skill-registry

To build a project skill registry automatically, use a tool that scans every SKILL.md frontmatter across user and project directories to consolidate workspace conventions into a single persisted file. This ensures consistent loading and provides a ready-to-load registry for sub-agents.

A centralized skill registry is a consolidated index of all available user and project-level skills. You need it to automate discovery and ensure consistent skill loading across tasks, preventing manual lookup errors and missing conventions during execution.

You can scan directories for SKILL.md files by running an automated discovery process that aggregates user-level and project-level frontmatter. This process extracts and consolidates the defined conventions into a centralized markdown file for task reference.

Yes, you can persist a skill registry to engram for cross-session reuse. The registry is saved locally to .atl/skill-registry.md and optionally to engram when available, ensuring that sub-agents can reference it before task execution across sessions.

No, the skill registry discovery process does not require external dependencies. It operates independently by scanning local user and project directories for SKILL.md frontmatter and aggregating the results into a centralized registry file.

You should not use an automated skill registry if your project lacks structured SKILL.md frontmatter files across directories. The tool relies on scanning these specific files to aggregate workspace conventions, so unstructured documentation will not be discovered or consolidated.