gentle-ai-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`.
10- Save the registry to Engram as `topic_key: skill-registry` when available, with `capture_prompt: false`.
11- Skip `sdd-*`, `_shared`, and `skill-registry`; deduplicate by skill name, preferring project-level skills over user-level skills.
12- The registry mirrors Pi's runtime-resolved skill set (`before_agent_start.systemPromptOptions.skills`) as the authority for skill name, scope, and disablement. The loose scan still walks the known agent roots, which include the Pi-managed `~/.pi/agent/skills` and `.pi/skills`; every path Pi resolved is suppressed from the loose results, so a skill Pi hides (`disableModelInvocation` or an excluded name) is never re-indexed as active. Never rescan `node_modules` or reparse `pi.skills` yourself.
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…