Agent Skills
› Gentleman-Programming/gentle-ai
› skill-registry
skill-registry
GitHub管理技能注册表,在技能增删改后重建索引。通过gentle-ai命令或手动扫描SKILL.md,去重并生成.registry文件,支持持久化至Engram,确保代理能准确定位和调用技能。
Trigger Scenarios
安装、移除、创建、移动或重命名技能后
需要刷新技能索引时
Install
npx skills add Gentleman-Programming/gentle-ai --skill skill-registry -g -y
SKILL.md
Frontmatter
{
"name": "skill-registry",
"license": "MIT",
"metadata": {
"author": "gentleman-programming",
"version": "1.0"
},
"description": "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.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.md, whether or not Engram is available. - Save the registry to Engram as
topic_key: skill-registrywhen available, withcapture_prompt: false. - Generate the registry with
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. - When scanning by hand, skip
_sharedandskill-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
- Run
gentle-ai skill-registry refresh --cwd <project>(add--forceafter 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. - Only if the command is unavailable: scan all known user and project skill directories for
*/SKILL.md, reading frontmatter only as needed to extractnameanddescriptiontrigger 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.
Version History
-
4acaf42
Current 2026-10-19 08:19
移除对SDD和OpenSpec的引用,将注册表生成方式改为使用gentle-ai skill-registry refresh命令,排除逻辑移至Go生成器。
- e01b114 2026-07-25 07:00


