Imported from oimiragieo/agent-studio (
.claude/skills/template-updater/SKILL.md). Install upstream withnpx skills add oimiragieo/agent-studio --skill template-updater. Copyright stays with the author.
Template Updater
Overview
Use this skill to refresh an existing template safely: research current best practices, compare against current implementation, verify placeholder completeness, apply updates, and validate rendering.
When to Use
- Template produces outdated or incorrect output when rendered
- New framework conventions make template content stale
- Reflection flags template quality issues
- User asks to audit/refresh an existing template
The Iron Law
Never update a template blindly. Every refresh must be evidence-backed, TDD-gated, and integration-validated.
Workflow
Step 0: Evaluate Current State
- Read the template file and understand its purpose
- Identify all
{{PLACEHOLDER}}tokens and their expected values - Check which creators/skills use this template
- Identify issues: missing placeholders, outdated content, wrong structure
Step 1: Research Best Practices
- Read
.claude/templates/CLAUDE.mdfor template conventions - Review similar templates for patterns
- Check the
template-rendererskill for rendering expectations - Use
Skill({ skill: 'research-synthesis' })if external research needed
Step 2: Generate Patch Backlog
- List specific changes needed
- Prioritize: structural fixes > content updates > formatting improvements
- Ensure all placeholders are documented
Step 3: Apply Updates
- Write or update rendering tests first (RED phase)
- Apply template changes (GREEN phase)
- Refactor for clarity (REFACTOR phase)
- Use
Edittool — never rewrite the entire file
Step 4: Verify Integration
- Verify all
{{PLACEHOLDER}}tokens are documented in the template header - Test rendering with
Skill({ skill: 'template-renderer' }) - Verify output matches expected structure for the artifact type
- Run
pnpm lint:fix && pnpm format
Step 5: Record
- Log changes via
MemoryRecordif significant - Update CHANGELOG.md entry
Domain-Specific Validation
- All
{{PLACEHOLDER}}tokens MUST be documented with description and example - Template MUST render without errors when all placeholders are provided
- Template output MUST match the target artifact's expected structure
- Conditional sections MUST handle missing optional placeholders gracefully
Anti-Patterns
- Adding placeholders without documenting them
- Hardcoding values that should be placeholders
- Breaking the template's rendering by changing placeholder names
- Removing sections that creators depend on