skill-registry

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After installing, removing, or renaming skills, AI agents and delegators lose track of what skills exist and where they live, causing blind searches and stale references. This Skill rebuilds a fresh index of all available skills so delegation decisions always use current information. ## Core Features & Use Cases - Skill Scanning: Scans all known user-level and project-level skill directories for SKILL.md files and extracts name and trigger descriptions from frontmatter. - Registry Generation: Writes a deduplicated registry to .atl/skill-registry.md, preferring project-level skills over global ones and skipping internal skills like sdd-* and _shared. - Persistence & Caching: Saves the registry to Engram with topic_key skill-registry when available, and reports cache hit or regeneration status. - Use Case: After adding a new code-review skill to your project, run this Skill so delegating agents immediately see the new skill's trigger and exact SKILL.md path. ## Quick Start Update the skill registry to index all current skills after my recent skill changes.

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

Invoke the skill-registry skill after installing, creating, moving, or renaming skills. It scans all known user and project skill directories for SKILL.md files and rewrites .atl/skill-registry.md with the current index.

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

The registry deduplicates by skill name and keeps the project-level skill over the user-level one. If duplicates exist across multiple global locations, the first source in scan order is kept.

Does the skill registry modify or summarize my 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 injected compact rules.

Which skills are excluded from the registry index?▼

Skills matching sdd-*, the _shared directory, and skill-registry itself are skipped during scanning. This keeps the index focused on delegatable skills rather than internal infrastructure.

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.