aria-skill-test
Skill0 starsChanged 2 months agoApache-2.0View on GitHub
Regression harness for the aria-skills repo. Runs every shipped skill in dry-run mode + asserts clean output (no traceback, no credential leaks, valid SKILL.md frontmatter, README.md present). Text report by default; --junit-xml flag for CI integration. Use when the user says "test the skills", "regression check", "before push", "run the test harness", or any time before opening a PR or pushing to main.
In this repository17 other files it gives its agents.
- aria-skill-candidatesSkill
- aria-skill-templateSkill
- 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
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Before pushing changes to the public repo
- Very specific: line 14
After running aria-skill-template to confirm the generated stub passes
- Distinctive: line 15
After editing any skill script — quick sanity check
- Distinctive: line 26
No Python traceback in stderr
- Distinctive: line 27
No credential leak patterns in output (Anthropic / Stripe / Resend / Twilio / Cloudflare / EL / AWS / GitHub PAT)
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
aria-skill-test
Regression harness. Pythonic + zero-dependency. Tests structural correctness across every skill in the repo without making any real API calls.
When to use
- Before pushing changes to the public repo
- In CI on every PR (use
--junit-xmlflag) - After running
aria-skill-templateto confirm the generated stub passes - After editing any skill script — quick sanity check
What gets checked
Per skill directory:
- SKILL.md frontmatter parses (YAML between
---markers) namefield in frontmatter matches directory namedescriptionfield is 40-600 chars- README.md exists
- Executable script found (snake_case or kebab-case .py / .sh)
- Dry-run exits 0 (clean) or 2 (needs creds with clear FATAL message)
- No Python traceback in stderr
- No credential leak patterns in output (Anthropic / Stripe / Resend / Twilio / Cloudflare / EL / AWS / GitHub PAT)
CLI
python3 aria_skill_test.py # all skills
python3 aria_skill_test.py --skill <name> # one skill
python3 aria_skill_test.py --skip <name> --skip <name> # exclude
python3 aria_skill_test.py --junit-xml results.xml # CI mode
python3 aria_skill_test.py --repo-root /path/to/repo # alternateSee also
- BUILDER_GUIDE.md — the patterns enforced
- aria-skill-template — generator paired with this harness
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.

