skill-registry

Other Community

Repo stars 3,249
License MIT
Author repo gentle-ai

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Trigger: update skills, skill registry, actualizar skills, after skill changes. Index available skills by trigger and path. Use…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Activation Contract”, “Hard Rules”, “Decision Gates”, “Execution Steps”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name skill-registry directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Activation Contract / Hard Rules / Decision Gates” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write / shell-exec; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

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.

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: Other
Author-declared agents: No explicit declaration found; this is not inferred or tested compatibility
Static check: 94 / 100 · heuristic scan, not runtime safety proof
Author / version / license: @Gentleman-Programming · MIT
Fluxly token estimate: Lean
Fluxly setup estimate: Guided setup
External API key: No requirement detected
Detected OS requirements: Unspecified
Runtime requirements: Unspecified
Detected file/system behavior: Read-only
Write / modify
Shell exec
Detected network behavior: Local-only
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview skill-registry.preview

The current SKILL.md does not define a fixed output example.

SKILL.md SKILL.md

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

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> Activation Contract → Hard Rules → Decision Gates → Execution Steps → Output Contract → References
terms    -> Use this skill after installing, removing, creating, moving, or renaming skills, or when a delegator needs a fresh skill index. · - The registry is an index, not a compiler or summary. · 1. Scan all known user and project skill directories for /SKILL.md. · Return: - Project name and .atl/skill-registry.md path. · - docs/skill-style-guide.md — how skills should be authored before indexing.
files/cmd -> .atl/skill-registry.md · topickey: skill-registry · captureprompt: false · sdd- · shared · skill-registry · .atl/ · .gitignore
body sha256 -> eb60fef3f354