cross-link-skills

Repair and verify cross-references between SKILL.md files after structural changes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps a skill library consistent by finding and repairing stale or missing cross-references between SKILL.md files after skills are created, renamed, removed, or restructured, preventing broken invocations and inaccurate Called by contexts.

Core Features & Use Cases

  • Registry construction: Scans every .agents/skills/*/SKILL.md and builds an in-memory registry of names, Calls, and Called by relationships.
  • Detection and minimal fixes: Identifies stale references from renames/removals, missing references for new skills, and rewiring changes, then performs minimal edits limited to cross-reference strings.
  • Validation and safety: Runs validate-skills on every edited file and rolls back edits that drop below the validation threshold, reporting files that require manual review.
  • Reporting: Produces an impact report summarizing trigger, scanned skills, fixes made, and validation outcomes.
  • Use Case: After renaming agent-architect to agent-builder, run this Skill to update all SKILL.md mentions, fix Called by contexts, and validate the edits.

Quick Start

Run the cross-link-skills repair after renaming a skill to update all SKILL.md cross-references and validate edits.

Frequently Asked Questions about cross-link-skills

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

FAQPage Schema
How do I fix broken cross-references in SKILL.md files after renaming a skill?

Repair broken cross-references by scanning all SKILL.md files, building an in-memory registry, and applying minimal edits to stale Calls and Called by metadata strings.

Why do skill invocations fail after restructuring my skill library?

Skill invocations fail because restructuring leaves stale or missing cross-references between SKILL.md files, desynchronizing agent metadata and causing inaccurate Called by contexts.

What is the best way to synchronize skill registry metadata after removing a skill?

Synchronize skill registry metadata by rebuilding the registry to detect missing references, rewiring cross-reference strings, and validating edited files to ensure consistent invocation contexts.

Can I automatically validate SKILL.md edits and roll back changes that fail?

Automatically validate SKILL.md edits by running validate-skills on every edited file, rolling back edits that drop below the validation threshold, and flagging them for manual review.

Does cross-link repair modify anything beyond cross-reference strings in skill files?

Cross-link repair limits modifications strictly to cross-reference strings in SKILL.md files, performing minimal edits to ensure only Calls and Called by metadata is synchronized.