aria-skill-template
YAML-reconcile skill scaffolder. Generates a fully-formed skill directory in 5 seconds.
When to use
- Starting a new vendor integration (Linear, Notion, GitHub, etc.)
- Contributor wants to ship a PR — scaffold first, then fill in
- Pattern enforcement (the template embeds BUILDER_GUIDE conventions)
How it works
- Validates the skill name (lowercase + hyphens, 3-40 chars)
- Computes derived names (snake_case for Python, title for headings)
- Renders 5 template files via Python string formatting
- Writes them to
<dest>/<name>/ - Chmods the Python script executable
- Prints next-steps + path to the new skill
CLI
python3 aria_skill_template.py <skill-name> [--vendor <vendor>] [--dest <dir>] [--force]
Examples:
python3 aria_skill_template.py linear-sync
python3 aria_skill_template.py github-org-sync --vendor github
python3 aria_skill_template.py my-skill --dest /tmp/scratch
What gets generated
5 files in <dest>/<name>/:
README.md— public docs with the standard structureSKILL.md— Claude Code manifest with frontmatter trigger description<snake_name>.py— script with reconcile-loop stubs + TODO markers for vendor specifics<snake_name>_config.yaml— YAML config templaterequirements.txt— common deps (PyYAML + httpx)
Conventions enforced
Per BUILDER_GUIDE.md:
- Two-flag prod gate pre-wired (--apply + --prod for live mode)
- Mode-mismatch safety (refuses test-key in live-mode and vice-versa)
- Match-by-metadata-key (
aria_keyfield), not by display name - Splat audit hook stub
- Dry-run default
See also
- BUILDER_GUIDE.md — the pattern reference
- aria-skill-test — regression harness for shipped skills
License
Apache 2.0