1.9 KiB
1.9 KiB
Workflow: Add a Template to a Skill
<required_reading> Read these reference files NOW:
- references/using-templates.md </required_reading>
Ask (if not already provided):
- Which skill needs a template?
- What output does this template structure?
Step 2: Analyze Template Need
Confirm this is a good template candidate:
- Output has consistent structure across uses
- Structure matters more than creative generation
- Filling placeholders is more reliable than blank-page generation
If not a good fit, suggest alternatives (workflow guidance, reference examples).
Step 3: Create Templates Directory
mkdir -p ~/.claude/skills/{skill-name}/templates
Step 4: Design Template Structure
Gather requirements:
- What sections does the output need?
- What information varies between uses? (→ placeholders)
- What stays constant? (→ static structure)
Step 5: Write Template File
Create templates/{template-name}.md with:
- Clear section markers
{{PLACEHOLDER}}syntax for variable content- Brief inline guidance where helpful
- Minimal example content
Step 6: Update Workflow to Use Template
Find the workflow that produces this output. Add:
<process>
...
N. Read `templates/{template-name}.md`
N+1. Copy template structure
N+2. Fill each placeholder based on gathered context
...
</process>
Step 7: Test
Invoke the skill workflow and verify:
- Template is read at the right step
- All placeholders get filled appropriately
- Output structure matches template
- No placeholders left unfilled
<success_criteria> Template is complete when:
- templates/ directory exists
- Template file has clear structure with placeholders
- At least one workflow references the template
- Workflow instructions explain when/how to use template
- Tested with real invocation </success_criteria>