Skill Registry
Trigger: update skills, skill registry, actualizar skills, after skill changes.
Install
npx skills add Gentleman-Programming/gentle-ai --skill skill-registry -g -a claude-code -y- Repository
- Gentleman-Programming/gentle-ai8.2k
- Category
- Engineering
- Updated
- 3d ago
- License
- MIT
- Context cost
- Lightabout 659 tokens
- Runs scripts
- No, instructions only
What it does
Trigger: update skills, skill registry, actualizar skills, after skill changes. Index available skills by trigger and path.
Activation Contract
Use this skill after installing, removing, creating, moving, or renaming skills, or when a delegator needs a fresh skill index.
Hard Rules
- The registry is an index, not a compiler or summary.
SKILL.mdremains the source of truth. - Do not generate or inject compact rules by default; preserve author intent by passing exact skill paths to subagents.
- Always write
.atl/skill-registry.md, whether or not Engram is available. - Save the registry to Engram as
topic_key: skill-registrywhen available, withcapture_prompt: false. - Generate the registry with
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. - When scanning by hand, skip
_sharedandskill-registry; deduplicate by skill name, preferring project-level skills over user-level skills. - Add
.atl/to.gitignorewhen possible unless explicitly disabled.
Decision Gates
| 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 |
