Install any skill in seconds. Free to start, no credit card required.
Get Started Free →gentleman-programming/skill-registry
Trigger: update skills, skill registry, actualizar skills, after skill changes. Index available skills by trigger and path.
Passed 18 of 20 test cases with the skill, and 12 of 20 without it.
and 8 more in the full report
8 fixed10 passed either way0 still failing2 broke3 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
During manual skill scanning, a skill named `lint-code` was found in two global directories: `/etc/skills/lint-code/SKILL.md` (scanned first) and `~/.skills/lint-code/SKILL.md` (scanned second). Which one should be retained?
| Checked | Without skill | With skill |
|---|---|---|
| Selects the first global skill source from scan order | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill after installing, removing, creating, moving, or renaming skills, or when a delegator needs a fresh skill index.
SKILL.md remains the source of truth..atl/skill-registry.md, whether or not Engram is available.topic_key: skill-registry when available, with capture_prompt: false.gentle-ai skill-registry refresh --cwd <project>: it owns the scan order, deduplication, and the skills it never indexes. Scan by hand only when that command is unavailable._shared and skill-registry; deduplicate by skill name, preferring project-level skills over user-level skills..atl/ to .gitignore when possible unless explicitly disabled.| Situation | Action |
|---|---|
| Same skill exists globally and in project | Keep the project-level skill |
| Same skill exists in multiple global locations | Keep the first source in scan order |
| No skills found | Write an empty registry so agents stop searching blindly |
| Agent will delegate work | Select matching registry rows and pass their SKILL.md paths |
gentle-ai skill-registry refresh --cwd <project> (add --force after skill changes); it writes .atl/skill-registry.md. If it reports the refresh was skipped (not a project), stop: there is no registry to persist. If it succeeds, go to step 4. If it fails, report the error instead of scanning by hand.*/SKILL.md, reading frontmatter only as needed to extract name and description trigger text..atl/skill-registry.md with scanned sources, registry contract, skill name, trigger/description, scope, and exact path.title: skill-registry, topic_key: skill-registry, type: config, and capture_prompt: false.Return:
.atl/skill-registry.md path.test cases passed, vs 12 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.