Individual skill

template-designer

Turn a document the team keeps rewriting into a template that actually helps — extract the recurring skeleton, mark what varies with real placeholder prompts, keep it lighter than the ceremony it replaces, and pilot it before decreeing it. Use when asked make a template from this doc, we write this same thing every week, standardize our status updates or briefs, or why does nobody use our templates. Produces the extracted template with prompting placeholders, the keep-it-light rules, the example-filled twin, and the adoption path.

skills/template-designer/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,539
Repository last updated
Nov 9, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Template Designer Skill

Templates fail in two familiar ways: the empty-headings ghost (`## Background` — helpfully blank) that guides nobody, and the forty-field bureaucratic form that takes longer than freeform writing did. A working template is extracted from documents the team *already writes repeatedly*, keeps only the sections that recur with purpose, and — the difference-maker — its placeholders are *prompts* ("One sentence: what changed since last update, and does the date still hold?") rather than labels ("Update:"). It ships with a filled example, because the example teaches what the skeleton can't.

## What This Skill Produces

- **The template** — the recurring skeleton with prompting placeholders, each section justified by recurrence
- **The filled twin** — a realistic example completed end-to-end; templates travel in pairs or don't travel
- **The light-ness audit** — what was deliberately left out, and the freeform escape-hatch section
- **The adoption path** — pilot with the next real instance, revise from friction, then propose as default (not decree)

## Required Inputs

Ask for these if not provided:
Back to top