aria-skill-template
Skill0 starsChanged 2 months agoApache-2.0View on GitHub
Scaffolds a new aria-skills-pattern skill from a template. Generates README.md + SKILL.md + script.py with reconcile-loop stubs + config.yaml + requirements.txt — a fully-formed skill directory ready to fill in with vendor-specific logic. Multiplies contributor velocity. Use when the user says "scaffold a new skill", "create a skill for X", "new skill template", "I want to build a skill for <vendor>", or starting any new vendor integration.
In this repository17 other files it gives its agents.
- aria-skill-candidatesSkill
- aria-skill-testSkill
- call-scrubSkill
- cloudflare-dns-deploySkill
- doc-to-pdfSkill
- ffmpeg-audioSkill
- github-repo-deploySkill
- goal-to-planSkill
- headless-claudeSkill
- live-code-watchSkill
- premortemSkill
- screen-describeSkill
- session-cabinetSkill
- skill-manifest-genSkill
- sprint-scaffoldSkill
- surgical-patchSkill
- video-ingestSkill
The file
Files
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/scratchWhat 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
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.