scan-registry

Scan skill directories and write a unified registry to .sdd/skill-registry.md.

1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/lleontor705/cortex-ia --skill scan-registry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scan-registry
Source: https://github.com/lleontor705/cortex-ia/tree/main/internal/assets/skills/scan-registry
Command: npx skills add https://github.com/lleontor705/cortex-ia --skill scan-registry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scans all known skill locations to identify every skill and builds a unified catalog for sub-agent discovery, persisting it for cross-session use.

Core Features & Use Cases

  • Scans user-level and project-level skill directories, applies deduplication rules to keep the most specific version.
  • Writes a registry file to .sdd/skill-registry.md and optionally persists to Cortex when available.
  • Provides a ready-to-consume catalog for sub-agents to discover skills without repeated directory scans.

Quick Start

Scan all known skill locations and persist a unified registry to .sdd/skill-registry.md.

Frequently Asked Questions about scan-registry

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

FAQPage Schema
How do I build a unified skill registry for sub-agent discovery?

You build a unified skill registry by scanning all known user-level and project-level skill directories, applying deduplication rules, and persisting the consolidated catalog to .sdd/skill-registry.md.

What is the best way to persist a skill catalog for cross-session reuse?

Persisting a skill catalog for cross-session reuse involves writing the consolidated registry file to .sdd/skill-registry.md, and optionally persisting the data to Cortex when available.

How does scanning skill directories handle duplicate or deprecated entries?

Scanning skill directories handles duplicates by reading only the frontmatter of SKILL.md files and applying deduplication rules to keep the most specific version, while ignoring deprecated directories entirely.

Does the skill registry scan work with both project-level and user-level directories?

Yes, the skill registry scan operates across both project-level and user-level skill directories simultaneously to identify every available skill and consolidate them into a single unified catalog.

Why do I need to scan SKILL.md files to catalog available skills?

You need to scan SKILL.md files to catalog available skills because the scan reads only the frontmatter metadata to avoid redundant directory scans, providing a ready-to-consume registry for sub-agents.