example-skill
Skill144 starsChanged 15 months agoMITView on GitHub
Use when you need the canonical shape of an Aegis Stack skill, or as the copy-from starting point for a new skill. Demonstrates every required section; not a real workflow.
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 38 edited versions we read keep these.
4
Distinctive
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 14
Use when starting a new skill and you want a known-good skeleton to fill in, or when you need to see how the required sections fit together.
- Distinctive: line 17
Do NOT use for real work. This skill performs no framework change.
- Very specific: line 34
Write the failing test first (TDD): add the case to the relevant tests/...
- Distinctive: line 39
Update docs and i18n keys touched by the change.
- Distinctive: line 40
Run the gates below and fix anything red.
“Common” is measured: kept by at least 6 in 10 of the 38 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Example skill
This skill exists to validate and demonstrate the house format defined in
.claude/skills/README.md. It is a template, not a real workflow. Copy this
directory, rename it, and replace the placeholder content.
When to use
Use when starting a new skill and you want a known-good skeleton to fill in, or when you need to see how the required sections fit together.
Do NOT use for real work. This skill performs no framework change; it only shows the format.
Files that change
Grouped by role. A real skill lists exact repo-relative paths here so an agent opens them without searching. Placeholder example:
- Registry:
aegis/services/registry.py - CLI:
aegis/cli/<command>.py - Template:
aegis/templates/copier-aegis-project/{{ project_slug }}/... - Tests:
tests/<area>/test_<thing>.py - Docs:
docs/<page>.md - i18n:
aegis/i18n/en.py
Procedure
- Write the failing test first (TDD): add the case to the relevant
tests/...file and confirm it fails for the right reason. - Make the change in the registry, CLI, and template files listed above.
- Backport any change made in a generated project into its template under
aegis/templates/, so it survives the nextaegis init. - Update docs and i18n keys touched by the change.
- Run the gates below and fix anything red.
Gates
make check(lint, typecheck, test) must pass.make test-templatemust pass when the change touches templates.
Pitfalls
- Template changes read from the committed git state, not the working tree, so an uncommitted template edit will not show up in a freshly generated project.
- A vague frontmatter
descriptionmeans the skill never loads, because the description is the only thing an agent reads when deciding to use it.
Other versions50 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 50
- anthropics/claude-plugins-official★ 46ksame name
- NVIDIA/SkillSpector★ 24ksame name
- microsoft/apm★ 4.2ksame name
- huggingface/upskill★ 764same name
- open-gitagent/gitclaw★ 712same name
- aws-samples/sample-well-architected-skills-and-steering★ 268same name
- PromptPartner/agentsmith★ 173same name
- OPBR/build-claude-code★ 136same name
- LeeYudok/agents-scaffold★ 37same name
- lukasz-fedor/claude-memory-template★ 31same name
40 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use handoff and code-review.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 3 projects that use this
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 3 projects that use this
In this repository14 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- tests/CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- llms.txtllms.txt
- add-cli-commandSkill
- add-componentSkill
- add-serviceSkill
- create-pluginSkill
- execute-issueSkill
- i18nSkill
- releaseSkill
- squash-branchSkill
- template-devSkill
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.