skill-registry

Scans skill directories and project conventions to generate a centralized Markdown skill index.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/juanjo-zurich/juarvis-v4 --skill skill-registry-juanjo-zurich
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-registry
Source: https://github.com/juanjo-zurich/juarvis-v4/tree/main/plugins/core/skills/skill-registry
Command: npx skills add https://github.com/juanjo-zurich/juarvis-v4 --skill skill-registry-juanjo-zurich

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents working on a project often lack awareness of which skills and project conventions are available, leading to missed context and inconsistent behavior. This Skill scans user and project skill directories plus convention files to build a single centralized registry that orchestrators and sub-agents can load on demand. ## Core Features & Use Cases - Skill Discovery: Scans user-level directories (Claude, Gemini, Cursor, OpenCode, Antigravity) and project-level directories for SKILL.md files, extracting their triggers. - Convention Indexing: Detects project convention files such as AGENTS.md, GEMINI.md, .cursorrules, and .agent/rules, following referenced files recursively. - Flexible Persistence: Writes the registry to .juar/skill-registry.md and optionally persists it to Engram memory depending on the artifact storage mode (engram, openspec, hybrid, none). - Use Case: After installing new skills in a project, run this Skill so the orchestrator and all sub-agents immediately know which skills exist, their triggers, and where to load them from. ## Quick Start Ask the agent to scan all skill directories and project conventions and generate the centralized skill registry index in .juar/skill-registry.md.

Frequently Asked Questions about skill-registry

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

FAQPage Schema
How do I create a central index of AI agent skills in a project?▼

Run the skill-registry Skill, which scans user and project skill directories for SKILL.md files, extracts their triggers, and writes a Markdown table to .juar/skill-registry.md. Project-level skills take priority over user-level duplicates.

Which directories does the skill registry scan for SKILL.md files?▼

It scans user directories for Claude, Gemini, Antigravity, Cursor, and OpenCode, plus project directories like .juarvis/skills, .gemini/skills, .agent/skills, and a recursive skills/ folder. It ignores SDD skills and files starting with _shared.

Does the skill registry include project convention files?▼

Yes, it indexes convention files such as AGENTS.md, GEMINI.md, .cursorrules, and .agent/rules. If a convention file references other files, those references are read and included in the registry as well.

Where is the generated skill registry stored?▼

The registry is always written to .juar/skill-registry.md when possible. Depending on the artifact storage mode, it can also be persisted to Engram memory via mem_save, or returned without changes in none mode.

What happens when the same skill exists in both user and project directories?▼

The project-level skill always wins. The registry deduplicates entries and prioritizes project sources over user sources so local conventions override global ones.