skill-registry
- Repo stars 3,249
- License MIT
- Author updated Live
- Author repo gentle-ai
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 94 / 100 · audit passed
- Author / version / license
- @Gentleman-Programming · MIT
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: skill-registry
description: Trigger: update skills, skill registry, actualizar skills, after skill changes. Index available…
category: other
runtime: no special runtime
---
# skill-registry output preview
## PART A: Task fit
- Use case: Trigger: update skills, skill registry, actualizar skills, after skill changes. Index available skills by trigger and path. Use this skill after installing, removing, creating, moving, or renaming skills, or when a delegator needs a fresh skill index. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Activation Contract / Hard Rules / Decision Gates” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Trigger: update skills, skill registry, actualizar skills, after skill changes. Index available skills by trigger and path. Use this skill after installing, removing, creating, moving, or renaming skills, or when a delegator needs a fresh skill index. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Activation Contract / Hard Rules / Decision Gates” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Start with a small task and check whether the result follows “Activation Contract / Hard Rules / Decision Gates”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: skill-registry
description: Trigger: update skills, skill registry, actualizar skills, after skill changes. Index available…
category: other
source: Gentleman-Programming/gentle-ai
---
# skill-registry
## When to use
- Trigger: update skills, skill registry, actualizar skills, after skill changes. Index available skills by trigger and…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Activation Contract / Hard Rules / Decision Gates” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "skill-registry" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Activation Contract / Hard Rules / Decision Gates
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files, run shell commands | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} 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.mdremains 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.mdregardless of SDD persistence mode. - Save the registry to Engram as
topic_key: skill-registrywhen available, withcapture_prompt: false. - Skip
sdd-*,_shared, andskill-registry; deduplicate by skill name, preferring project-level skills over user-level skills. - Add
.atl/to.gitignorewhen 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
nameanddescriptiontrigger text. - Render
.atl/skill-registry.mdwith 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, andcapture_prompt: false. - Return the registry path, skill count, cache status, and whether Engram was updated.
Output Contract
Return:
- Project name and
.atl/skill-registry.mdpath. - 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.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review