Scan skill directories and write a resolved registry to .atl/skill-registry.md.
npx skills add https://github.com/aroca89/roca_teams --skill skill-registry-aroca89
Please help me install this Agent Skill. Skill: skill-registry Source: https://github.com/aroca89/roca_teams/tree/main/skills/skill-registry Command: npx skills add https://github.com/aroca89/roca_teams --skill skill-registry-aroca89
This skill removes the need for manual discovery of skills and conventions by keeping a centralized registry that the orchestrator can read once per session to pass pre-resolved paths to sub-agents.
.atl/skill-registry.md, optionally saves to engram, and ensures .atl/ is ignored so future orchestration starts with reliable data.Tell the orchestrator to refresh the registry by saying 'update skills' after installing or removing a skill.
High-intent search queries and answers about installing and using this skill.
To keep a project skill registry synced, you can scan available skill directories and conventions to generate a centralized registry file. This process updates resolved skill paths for sub-agents after adding or removing skills.
The best way to resolve skill paths without manual discovery is using a centralized registry that the orchestrator reads once per session. This provides pre-resolved paths to sub-agents instantly without rescanning directories.
To update skills in Claude, Gemini, or Copilot workspace directories, you trigger a registry refresh by telling the orchestrator to update skills. This scans global and workspace directories, deduplicates entries, and captures triggers from frontmatter.
Yes, you can persist convention indexes and referenced files so sub-agents have instant access to project rules. The registry includes each convention index so agents can read rules without re-reading indexes during sessions.
Yes, the skill registry supports saving to engram so the orchestrator can load pre-resolved skill targets without rescanning. It also writes a registry file and ensures the output directory is ignored for reliable future data.
Your orchestrator fails to find newly configured skills because the registry needs refreshing after installation or removal. Scanning available directories and regenerating the registry ensures newly configured skills are discovered and paths resolved.
adacosdevScan SKILL.md frontmatter and consolidate skills into a registry file.
thiagoooo34252Manage project skill registries by scanning SKILL.md files and extracting metadata.
imbue-aiProcess managed agent lifecycle state events and trigger automated responses.
AarononthewebGenerate routing indexes mapping tasks to dotnet-skills in AGENTS.md and CLAUDE.md.