Claude Skill

gentle-ai-skill-registry

Trigger: update skills, skill registry, actualizar skills, after skill changes. Index available skills by trigger and path.

LLM Mart · 0 points · 9 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download gentleman-programming-gentle-pi-skills_skill-registry-f48a957.zip · 1 KB

gentleman-programming/gentle-pi 939 141 forks MIT Updated 5d ago

Part of gentleman-programming/gentle-pi — 12 skills

Install

skills CLI npx skills add https://github.com/Gentleman-Programming/gentle-pi/tree/main/skills/skill-registry

Claude Code

claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install gentleman-programming-gentle-pi@llmmart

Git git clone https://github.com/Gentleman-Programming/gentle-pi.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole gentleman-programming/gentle-pi collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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.
Always write .atl/skill-registry.md regardless of SDD persistence mode.
Save the registry to Engram as topic_key: skill-registry when available, with capture_prompt: false.
Skip sdd-*, _shared, and skill-registry; deduplicate by skill name, preferring project-level skills over user-level skills.
Add .atl/ to .gitignore when possible unless explicitly disabled.

Decision Gates

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

Execution Steps

Scan all known user and project skill directories for */SKILL.md.
Read frontmatter only as needed to extract name and description trigger text.
Render .atl/skill-registry.md with scanned sources, registry contract, skill name, trigger/description, scope, and exact path.
Persist to Engram when available using title: skill-registry, topic_key: skill-registry, type: config, and capture_prompt: false.
Return the registry path, skill count, cache status, and whether Engram was updated.

Output Contract

Return:

Project name and .atl/skill-registry.md path.
Number of indexed skills.
Whether the cache was hit or regenerated.
Any skipped or duplicate skills when relevant.

References

docs/skill-style-guide.md — how skills should be authored before indexing.
skills/_shared/skill-resolver.md — how delegators use the index.

Files (gentle-pi)

SKILL.md 2.3 KB

---
name: gentle-ai-skill-registry
description: "Trigger: update skills, skill registry, actualizar skills, after skill changes. Index available skills by trigger and path."
license: MIT
metadata:
  author: gentleman-programming
  version: "1.0"
---

## 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.
- Always write `.atl/skill-registry.md` regardless of SDD persistence mode.
- Save the registry to Engram as `topic_key: skill-registry` when available, with `capture_prompt: false`.
- Skip `sdd-*`, `_shared`, and `skill-registry`; deduplicate by skill name, preferring project-level skills over user-level skills.
- Add `.atl/` to `.gitignore` when possible unless explicitly disabled.

## Decision Gates

| 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 |

## Execution Steps

1. Scan all known user and project skill directories for `*/SKILL.md`.
2. Read frontmatter only as needed to extract `name` and `description` trigger text.
3. Render `.atl/skill-registry.md` with scanned sources, registry contract, skill name, trigger/description, scope, and exact path.
4. Persist to Engram when available using `title: skill-registry`, `topic_key: skill-registry`, `type: config`, and `capture_prompt: false`.
5. Return the registry path, skill count, cache status, and whether Engram was updated.

## Output Contract

Return:
- Project name and `.atl/skill-registry.md` path.
- Number of indexed skills.
- Whether the cache was hit or regenerated.
- Any skipped or duplicate skills when relevant.

## References

- `docs/skill-style-guide.md` — how skills should be authored before indexing.
- `skills/_shared/skill-resolver.md` — how delegators use the index.