skill-registry

Scan SKILL.md files and publish a deduplicated .atl/skill-registry.md.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/valentinmathey/Skills-Back-Automation --skill skill-registry-valentinmathey
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-registry
Source: https://github.com/valentinmathey/Skills-Back-Automation/tree/main/skills/skill-registry
Command: npx skills add https://github.com/valentinmathey/Skills-Back-Automation --skill skill-registry-valentinmathey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create or update the skill registry for the current project by scanning user and project-level skill definitions, consolidating triggers, and publishing a centralized .atl/skill-registry.md. This entry also integrates with engram storage when available.

Core Features & Use Cases

  • Scans all skills across user and project folders to build a complete registry
  • Deduplicates skills by priority to keep project-level definitions when conflicts arise
  • Writes the .atl/skill-registry.md file and optionally persists to engram for cross-session recall
  • Supports downstream agents by providing pre-resolved, compact rules for prompts

Quick Start

Run the registry update to scan all skills and project conventions, generating or refreshing .atl/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 maintain a live registry of skills for my prompts?▼

To maintain a live skill registry, scan all SKILL.md files across user and project scopes, deduplicate entries by prioritizing project-level versions, and publish a centralized .atl/skill-registry.md file for reference.

What is the best way to consolidate prompt triggers across multiple project folders?▼

Consolidating prompt triggers requires scanning user and project-level skill definitions, resolving conflicts by keeping project-level definitions, and writing the compiled rules into a single .atl/skill-registry.md file.

Can I persist a skill registry for cross-session reuse with an engram system?▼

Yes, you can persist a skill registry for cross-session reuse by integrating with an engram system when available, allowing downstream agents to access pre-resolved and compact rules across sessions.

How does skill deduplication work when scanning user and project scopes?▼

Skill deduplication works by scanning every SKILL.md across user and project scopes and automatically prioritizing the project-level version when conflicts arise, ensuring localized definitions override global ones.

Do I need any external dependencies to generate a skill registry?▼

No external dependencies are required to generate a skill registry; the process solely scans SKILL.md files and writes the .atl/skill-registry.md file, though an engram system is optionally supported for persistence.