dvy1987/agent-loom / .agents/skills/cross-link-skills
cross-link-skills
VerifiedRepair and verify cross-references between SKILL.md files after a skill is created, renamed, removed, or restructured. Ensures every skill that calls another skill references the correct name, and every skill that is called has accurate "Called by" context. Load after universal-skill-creator creates a skill, after improve-skills completes a cycle, after a skill is renamed or removed, or when the user asks to fix cross-references, sync skill links, repair broken skill references, update skill cross-links, check skill references, or "are cross-links correct".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.9 KB |
| references/examples.md | markdown | 2.6 KB |
references/examples.md
View on GitHub# Cross-Link Skills — Full Worked Examples
Skill: `cross-link-skills` | Enriched from SKILL.md (improve-skills pass, SKIP_RESEARCH).
## Example 1 — Documented workflow
**Input:** Skill `agent-architect` was renamed to `agent-builder`. Run cross-link repair.
**Output:**
```
Cross-link repair triggered by: rename (agent-architect → agent-builder)
Skills scanned: 35
Stale references found: 13
process-decomposer/SKILL.md: 2 references → fixed
setup-evaluation/SKILL.md: 4 references → fixed
project-orchestrator/SKILL.md: 2 references → fixed
create-agent-prompt/SKILL.md: 2 references → fixed
skill-finder/SKILL.md: 1 reference → fixed
tool-finder/SKILL.md: 1 reference → fixed
ROUTING.md: 1 reference → fixed (not a SKILL.md, flagged for library-skill)
Validation: all 6 edited skills still ≥10/14 ✓
```
## Example 2 — Documented workflow
**Input:** New skill `cross-link-skills` was just created. Run cross-link repair.
**Output:**
```
Cross-link repair triggered by: new skill (cross-link-skills)
Skills scanned: 36
New skill calls: validate-skills
New skill called by: universal-skill-creator, improve-skills
universal-skill-creator/SKILL.md: reference present ✓
improve-skills/SKILL.md: reference present ✓
Stale references: 0
Missing references: 0
No edits needed.
```
## Example 3 — Step-by-step execution
**Input:** "Run `cross-link-skills` on [concrete task]"
**Agent actions:**
1. Build Skill Registry
2. Detect Stale References
3. Apply Fixes
4. Validate Edits
5. Report
6. Reconcile knowledge graph
**Impact Report shape:**
```
Cross-link repair complete: YYYY-MM-DD
Trigger: [created | renamed | removed | rewired] — [skill name(s)]
Skills scanned: N
Stale references found: N
References fixed: N
References flagged for manual review: N
SKILL.md files edited: [list]
Validation: all edited skills ≥10/14 [✓ | list failures]
```
## Example 4 — Gotcha application
**Input:** Task hits a non-obvious edge case
**Apply:**
- **Description text contains skill names as triggers** — e.g., "when agent-builder checks skill availability". These ARE cross-references and must be updated on rename.
- **Examples may contain skill names** — these are illustrative, not functional. Update them to avoid confusion, but don't flag them as broken references.
- **Frontmatter `sources` field** — skill names in sources are metadata, not cross-references. Leave them alone.
- **Don't create circular references** — if skill A calls B and B calls A, flag it instead of silently wiring it.
---
See `SKILL.md` for hard rules and verification checklist.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |