Leftover [X] or {{name}} in delivered files can easily reveal that the output is AI-generated. In addition to explicit placeholders, common template artifacts such as sample lines, “Acme Corp” in footers, or example data are also leftovers. template-instantiator provides a mechanical process to verify that a template has been correctly filled before delivery, with no unprocessed placeholders or sample content left behind.

What It Is

This is a DSH workflow plugin maintained by ChenneyZhuang. Its core value is to generate a zero-hit report before delivering files by mechanically inventorying, replacing, and scanning, proving that the template has no residues instead of merely “looking” filled.

Core Features

  1. Inventory all placeholders and variants: Identify {{var}}, [X], TODO/FIXME/TBD, Lorem ipsum, and sample lines in the template.
  2. Replace from provided data: Populate the template using provided data or agreed sources. Do not fabricate nonexistent values, remove optional parts that the user did not request, and do not leave half-finished content.
  3. Mechanical scanning and zero-hit proof: Perform a full scan across all inventoried patterns and output the results to prove that no leftovers remain.

Installation and Enablement

Run the following command to install the plugin:

npx skills add ChenneyZhuang/template-instantiator

For specific installation paths for each agent, refer to COMPATIBILITY.md.

Usage Workflow

The plugin’s workflow is fixed: “inventory, replace, scan, and present the zero-hit result”:

  1. Inventory: List all placeholders and variants in the template.
  2. Replace: Populate from provided data or agreed sources.
  3. Scan: Perform a mechanical scan of the final file to ensure all inventoried patterns have been processed.
  4. Present: Display the scan results in the delivery notes (patterns checked, items matched, items resolved).

Caveats and Limitations

  • Scan scope limitation: The scan can only find inventoried patterns. If the template contains placeholder styles that were not listed, those residues will not be detected.
  • Content correctness: The plugin can only prove “no leftovers,” not “content correctness.” When populating legal or compliance templates, domain review is still required.
  • License: MIT.

Summary

template-instantiator ensures the purity of deliverables through a mechanical process, making it suitable for scenarios that require strict control over template delivery quality. View the plugin details: catalog_url or the source code: github_url.