skill-link-check

Audits .agents/skills and .claude/skills directories for symlink consistency issues.

197|85|Updated Jul 5, 2026
One-click install
npx skills add https://github.com/yan-labs/yan-skills --skill skill-link-check-yan-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-link-check
Source: https://github.com/yan-labs/yan-skills/tree/main/skill-link-check
Command: npx skills add https://github.com/yan-labs/yan-skills --skill skill-link-check-yan-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Skills installed in one directory but missing from another cause silent failures where slash commands or skills never load. This Skill audits the layout between .agents/skills (the real source) and .claude/skills (the runtime mirror) and reports exactly which links are broken, orphaned, or pointing at the wrong target. ## Core Features & Use Cases - Layout Detection: Automatically recognizes both valid layouts—parent symlink (.claude/skills linking to .agents/skills) and per-child symlinks—without forcing a migration. - Five Issue Classifications: Detects orphan-in-claude, missing-link, not-symlink, broken-symlink, and wrong-target problems, each with evidence paths and suggested fix commands. - Scoped Audits with JSON Output: Audit project scope, global home scope, or both, with --project-root, --project-only, --global-only, and --json flags for automation. - Use Case: A skill you installed appears in .claude/skills but never loads. Run the audit to discover it is an orphan real directory with no source in .agents/skills, then review the suggested move-and-link commands before applying them. ## Quick Start Ask the AI to run the skill link audit on the current project and report any inconsistent or broken skill symlinks with suggested fixes.

Frequently Asked Questions about skill-link-check

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

FAQPage Schema
How do I check why a skill is not loading in Claude Code?

Run the check.py audit script against your project or home directory. It compares .agents/skills with .claude/skills and reports whether the skill is an orphan, has a missing symlink, or has a broken link, along with suggested fix commands.

How do I audit skill symlinks from the command line?

Run python3 check.py from the skill directory. Use --project-root to target a specific project, --project-only or --global-only to limit scope, and --json to emit stable machine-readable output for automation.

What is the difference between parent symlink and per-child symlink layouts?

In a parent symlink layout, .claude/skills itself is a single symlink to .agents/skills. In a per-child layout, .claude/skills is a real directory where each entry links to its counterpart in .agents/skills. Both are valid and the audit accepts either.

Does the skill link audit automatically fix broken symlinks?

No. The audit only reports issues with suggested fix commands for manual review. It never moves, deletes, or overwrites files, because orphan directories may contain work that has not been migrated yet.

Why does the audit script exit with code 1?

Exit code 1 means the audit completed successfully and found consistency issues, not that the script failed. Exit code 0 means no issues were found. Only Python tracebacks or unreadable targets indicate actual execution failure.