Build and refresh an index of available skills, including when to use each one and its exact file path. Resolve duplicate entries and give agents a current reference after skills are added, removed, moved, or renamed.
Trigger: update skills, skill registry, actualizar skills, after skill changes. Index available skills by trigger and path.
Review the instructions the agent will receive before you install.
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.docs/skill-style-guide.md — how skills should be authored before indexing.skills/_shared/skill-resolver.md — how delegators use the index.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Prepare pull requests by checking approved issue links, change-type labels, and required automated checks. Draft the repository’s PR template using observed test results, while leaving commits, pushes, PR creation, and merging under human control.
Split changes exceeding 400 lines into linked pull requests with clear boundaries and dependencies. Choose a chain structure, keep tests and documentation with each work unit, and document review order, verification plans, and justified size exceptions.
Structure guides, READMEs, design documents, and pull request descriptions so readers can find answers quickly. Put outcomes first, introduce details gradually, and use examples, tables, and checklists to support understanding and review.
Draft clear, considerate comments for code reviews, issue replies, and team updates. Put the actionable point first, explain technical reasons when needed, and give a concrete next step while matching the conversation’s language.
Create and verify gentle-ai journeys, which are scripted sequences of product actions. Check their declarations separately from actual execution, review outdated expectations after behavior changes, and record execution results for pull requests.
Prepare Gentle AI changes for review by linking approved issues, following branch and commit naming rules, and drafting pull requests with observed test results. Check change size and required automated checks before claiming readiness.