generate-from-template

Substitute {{VARIABLE}} placeholders in templates using JSON mappings.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/fractary/claude-plugins --skill generate-from-template
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate-from-template
Source: https://github.com/fractary/claude-plugins/tree/main/plugins/faber-agent/skills/generate-from-template
Command: npx skills add https://github.com/fractary/claude-plugins --skill generate-from-template

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Generate artifacts by substituting template placeholders with actual values, ensuring deterministic outputs.

Core Features & Use Cases

  • Replaces {{VARIABLE}} placeholders with provided values.
  • Validates template existence and writes output to a target path.
  • Keeps unreplaced variables as warnings for auditability.

Quick Start

Provide a template file, output path, and a variables map to generate the final artifact.

Frequently Asked Questions about generate-from-template

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate files by substituting variables into templates?

Template substitution replaces {{VARIABLE}} placeholders with values from a JSON map to produce output files. Provide your template file, a variables JSON object, and target output path; the Skill replaces all matching placeholders and writes the result to disk.

Can I automate artifact generation from template files in workflows?

Yes. Template-based generation automates deterministic artifact creation by applying variable substitution to templates in automated workflows. Define your template, pass a variables map, and the Skill handles substitution and file writing without manual intervention.

What happens to placeholders that don't match my variables?

Unreplaced {{VARIABLE}} placeholders remain in the output and are reported as warnings for auditability. This flags incomplete substitutions so you can verify all required variables were provided and catch configuration errors early.

How do I validate that template generation succeeded?

The Skill validates that the output file exists and is non-empty after substitution completes. If validation fails, the operation reports an error, preventing downstream use of incomplete or corrupted generated artifacts.

Do I need specific file formats or structure for my templates?

Templates use {{VARIABLE}} placeholder syntax for substitution; no special format is required beyond standard text or configuration files. The Skill enforces exact template usage and works with any file type containing placeholders you need replaced.