skill-registry

1## Activation Contract
2 
3Use this skill after installing, removing, creating, moving, or renaming skills, or when a delegator needs a fresh skill index.
4 
5## Hard Rules
6 
7- The registry is an index, not a compiler or summary. `SKILL.md` remains the source of truth.
8- Do not generate or inject compact rules by default; preserve author intent by passing exact skill paths to subagents.
9- Always write `.atl/skill-registry.md`, whether or not Engram is available.
10- Save the registry to Engram as `topic_key: skill-registry` when available, with `capture_prompt: false`.
11- 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.
12- When scanning by hand, skip `_shared` and `skill-registry`; deduplicate by skill name, preferring project-level skills over user-level skills.
13- Add `.atl/` to `.gitignore` when possible unless explicitly disabled.
14 
15## Decision Gates
16 
17| Situation | Action |
18| --- | --- |
19| Same skill exists globally and in project | Keep the project-level skill |
20| Same skill exists in multiple global locations | Keep the first source in scan order |
21| No skills found | Write an empty registry so agents stop searching blindly |
22| Agent will delegate work | Select matching registry rows and pass their `SKILL.md` paths |
23 
24## Execution Steps
25…