skill-registry

Indexes available skills by trigger and path into a registry file.

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/Alountk/Bloodbowl_Project --skill skill-registry-alountk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-registry
Source: https://github.com/Alountk/Bloodbowl_Project/tree/main/.opencode/skills/skill-registry
Command: npx skills add https://github.com/Alountk/Bloodbowl_Project --skill skill-registry-alountk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After installing, removing, or renaming skills, agents and delegators lose track of what skills exist and where they live. This Skill rebuilds a fresh index so delegators can find the right skill by trigger without scanning directories blindly. ## Core Features & Use Cases - Skill Indexing: Scans user and project skill directories for SKILL.md files and extracts name and trigger descriptions from frontmatter. - Deduplication Rules: Prefers project-level skills over global ones and skips internal entries like sdd-*, _shared, and skill-registry itself. - Registry Output: Writes .atl/skill-registry.md with skill names, triggers, scope, and exact paths, and optionally persists it to Engram. - Use Case: After adding three new skills to a project, run this Skill so a delegating agent receives exact SKILL.md paths instead of searching the filesystem. ## Quick Start Update the skill registry after my recent skill changes and tell me how many skills were indexed.

Frequently Asked Questions about skill-registry

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update the skill registry after adding new skills?▼

Run the skill-registry skill after installing, removing, creating, moving, or renaming skills. It scans all known user and project skill directories for SKILL.md files and regenerates .atl/skill-registry.md with names, triggers, and exact paths.

What happens when the same skill exists globally and in a project?▼

The project-level skill is kept and the global duplicate is skipped. If the same skill exists in multiple global locations, the first source in scan order wins.

Does the skill registry modify or summarize SKILL.md files?▼

No. The registry is an index, not a compiler or summary. SKILL.md remains the source of truth, and delegators receive exact skill paths rather than generated compact rules.

What happens if no skills are found during the scan?▼

An empty registry is still written to .atl/skill-registry.md so agents stop searching blindly. The output reports the indexed skill count and cache status.

Which skills are excluded from the registry index?▼

Skills matching sdd-*, the _shared directory, and skill-registry itself are skipped during scanning. Duplicates are deduplicated by skill name with project-level entries preferred.