omcustom:fix-refs

Audit, fix, and validate broken agent references and symlinks.

13|6|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/baekenough/second-brain --skill omcustom-fix-refs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omcustom:fix-refs
Source: https://github.com/baekenough/second-brain/tree/main/.claude/skills/fix-refs
Command: npx skills add https://github.com/baekenough/second-brain --skill omcustom-fix-refs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Broken references and missing symlinks in agent configurations cause runtime failures and manual cleanup overhead.

Core Features & Use Cases

  • Audit: detect missing/misaligned references across agent manifests.
  • Automatic fixes: update references and restore valid symlinks.
  • Validation: re-run audits to ensure healthy dependencies after fixes.

Quick Start

Run mgr-supplier:audit to identify issues, then run mgr-supplier:fix to apply fixes and re-audit.

Frequently Asked Questions about omcustom:fix-refs

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

FAQPage Schema
How do I fix broken symlinks and references in my agent configurations?

To fix broken symlinks and references, you can run an audit to detect missing or misaligned agent manifests, apply automatic fixes to restore valid symlinks, and then re-run validation audits to ensure healthy dependencies without causing further runtime failures.

What causes missing symlinks and broken references across claude agents?

Missing symlinks and broken references are typically caused by misaligned agent manifests, which lead to runtime failures and require manual cleanup overhead to restore valid dependencies across the harness environment.

Can I preview changes before applying fixes to agent references?

Yes, you can preview changes before applying fixes by using dry-run options. This enforces safe changes by allowing you to validate the audit and repair workflow without immediately modifying the active agent configurations.

What is the best way to audit and validate agent dependencies after making updates?

The best way to audit and validate agent dependencies is to run an audit command to identify issues, apply fixes to update references and restore symlinks, and then re-run the audit to ensure healthy dependencies post-repair.

Does this agent reference fixer support batch processing for multiple agents?

Yes, the agent reference fixer supports batch processing by focusing on audit, fix, and validation workflows for multiple agents simultaneously within the harness environment to prevent broken dependencies.