Aria skill template
Open-source Claude Code Skills that replace clicking through vendor dashboards — Stripe, Cloudflare DNS, ElevenLabs, GitHub, and more. Powered by Aria Code.
npx -y skills add iansteitz1-eng/aria-skills --skill aria-skill-templateAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
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.
SKILL.md
2.3 KB, as published. Nobody here has run it
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