library-skill

Synchronize skill repository metadata, indexes, and call graphs after structural changes.

3|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/dvy1987/agent-loom --skill library-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: library-skill
Source: https://github.com/dvy1987/agent-loom/tree/main/.agents/skills/library-skill
Command: npx skills add https://github.com/dvy1987/agent-loom --skill library-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps a distributed skill library consistent after structural changes by scanning every SKILL.md and synchronizing indexes, documentation, and call graphs so references do not become stale or broken.

Core Features & Use Cases

  • Scans all .agents/skills/*/SKILL.md files to build a canonical registry of skill names, descriptions, categories, triggers, and call relationships.
  • Updates central references: docs/SKILL-INDEX.md, AGENTS.md, README.md, docs/skill-graph.md, docs/prd/PRD.md, docs/architecture.md, and logs changes to docs/skill-outputs/SKILL-OUTPUTS.md.
  • Validates cross-references, flags broken or orphaned entries, conditionally invokes codebase-understanding or prd-writing to create missing docs, and always invokes generate-changelog as the final step.
  • Use case: run after adding, renaming, splitting, deprecating, or recategorizing skills to automatically rebuild call graphs and documentation and to produce an audit log and changelog entry.

Quick Start

Run library-skill after adding, renaming, or deprecating a skill to automatically synchronize indexes, documentation, call graphs, and changelogs.

Frequently Asked Questions about library-skill

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

FAQPage Schema
How do I automatically sync skill library documentation after renaming or adding skills?

Rebuilding a skill call graph after structural changes involves scanning all SKILL.md files to extract metadata, validating cross-references, and updating docs/skill-graph.md. This process automatically flags broken or orphaned entries to keep distributed skill libraries consistent.

What is the best way to maintain a call graph for AI agent skills?

Maintaining a call graph for AI agent skills requires scanning SKILL.md files to build a canonical registry of triggers and relationships. This registry is then used to update central reference documents and validate cross-references after skills are split or recategorized.

How do I generate a changelog entry after updating skill categories and indexes?

Generating a changelog entry after updating skill categories is done by invoking generate-changelog as the final synchronization step. The process logs changes to docs/skill-outputs/SKILL-OUTPUTS.md and produces an audit trail after rebuilding indexes and documentation.

Does this skill library synchronization approach validate broken cross-references?

Yes, skill library synchronization validates cross-references and flags broken or orphaned entries. It reads SKILL.md files to build a registry, rebuilds indexes, and conditionally invokes codebase-understanding or prd-writing to create missing docs while checking for stale references.

When should I run a skill repository sync to update README and AGENTS.md docs?

You should run a skill repository sync to update README and AGENTS.md docs whenever skills are added, renamed, split, deprecated, or when call relationships and categories change. This ensures central references and call graphs remain consistent across the library.