Skip to content

Gentleman-Programming/gentle-shell / skills/skill-registry

gentle-ai-skill-registry

Unverified

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.md remains the source of truth.
  • Do not generate or inject compact rules by default; preserve author intent by passing exact skill paths to subagents.
  • Refresh .atl/skill-registry.md as a shared disk-only index; do not save session-only runtime rows to the file or Engram.
  • Skip sdd-*, _shared, and skill-registry; deduplicate by skill name, preferring project-level skills over user-level skills.
  • In Pi, the effective view is <available_skills> plus the on-disk rows of the Effective session skills block in the system prompt.
  • Preserve Git-tracked targets during automatic refresh. Deliberate /skill-registry:refresh overrides that guard; unchanged rendered bytes remain untouched even on force.

Decision Gates

SituationAction
Same skill exists globally and in projectKeep the project-level skill
Pi-resolved skill and loose scan share a pathIn the effective view use the active Pi record, or suppress the path when disabled; the shared disk index remains independent
Same skill exists in multiple global locationsKeep the first source in scan order
No skills foundWrite an empty registry so agents stop searching blindly
Agent will delegate workSelect matching effective-view rows and pass their exact SKILL.md paths

Execution Steps

  1. Use /skill-registry:refresh for a deliberate disk-index refresh. It scans known project and user roots, reads frontmatter, and publishes deterministic rows and a non-authoritative cache.
  2. For Pi selection, consult the effective view: <available_skills> plus the Effective session skills rows.
  3. Pass selected exact paths to subagents and require them to read each SKILL.md before work.
  4. Return the registry path, disk skill count, and whether bytes changed.

Output Contract

Return:

  • Project name and .atl/skill-registry.md path.
  • Number of indexed skills.
  • Whether the registry changed or was already byte-identical.
  • Any skipped or duplicate skills when relevant.

References

  • docs/skill-style-guide.md — how skills should be authored before indexing.
  • assets/orchestrator-skills.md — Pi delegator protocol (effective view, exact paths).
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 463kUpdated Claude CodeCodexVerifiedInstall
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 463kUpdated Claude CodeCodexVerifiedInstall
discernment-nudgeanthropics/skillsAfter you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.Stars: 195kUpdated Claude CodeCodexVerifiedInstall
internal-commsanthropics/skillsA set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).Stars: 195kUpdated Claude CodeCodexVerifiedInstall