Trigger: update skills, skill registry, actualizar skills, after skill changes. Index available skills by trigger and path.
68
81%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
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 regardless of SDD persistence mode.topic_key: skill-registry when available, with capture_prompt: false.sdd-*, _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 |
*/SKILL.md.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.docs/skill-style-guide.md — how skills should be authored before indexing.skills/_shared/skill-resolver.md — how delegators use the index.e01b114
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.