meta-audit-local-skills-and-hooks

Audit local Claude Code skills and hooks for rot, duplicates, and broken registrations.

1|Updated Jun 23, 2026
One-click install
npx skills add https://github.com/bitranox/bitranox-skills --skill meta-audit-local-skills-and-hooks-bitranox
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: meta-audit-local-skills-and-hooks
Source: https://github.com/bitranox/bitranox-skills/tree/main/plugins/bitranox/skills/meta-audit-local-skills-and-hooks
Command: npx skills add https://github.com/bitranox/bitranox-skills --skill meta-audit-local-skills-and-hooks-bitranox

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Local skills and hooks that no plugin ships - personal ~/.claude/skills entries, project .claude/skills, hooks wired in settings.json - run with no quality gate and rot quietly: hooks stop firing, test dirs exist but never run, retired shims get deleted, and local copies silently duplicate marketplace skills. ## Core Features & Use Cases - Ownership-based target selection: The targets verb identifies which skill directories you may edit versus which are plugin-owned and report-only, preventing edits to marketplace-owned content. - Deterministic checks: The check verb detects registrations naming missing files, orphan hook scripts, malformed tombstones, uncollectable test dirs, untested scripts, non-trigger-first descriptions, and local duplicates of shipped skills. - Duplicate handling guidance: Byte-identical duplicates are retired; differing duplicates are diffed first so a local improvement is contributed upstream rather than deleted. - Use Case: A hook silently stopped firing on your machine. Run the audit to discover the settings.json registration points at a file that no longer exists, then fix the registration. ## Quick Start Ask the AI to audit the local skills and hooks on this machine using the meta-audit-local-skills-and-hooks skill, starting with the targets command to see what may be edited.

Frequently Asked Questions about meta-audit-local-skills-and-hooks

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

FAQPage Schema
How do I audit local Claude Code skills and hooks?▼

Run the audit_local.py script with the targets verb first to see which directories you own and may edit, then run the check verb to detect broken registrations, orphan hooks, uncollectable tests, and duplicates of shipped skills.

Why did my Claude Code hook silently stop firing?▼

A common cause is a settings.json registration that names a hook file which no longer exists, so the hook never runs and fails silently. The check verb's registration check reports exactly this mismatch.

Can I edit a skill found under ~/.claude/plugins to fix it?▼

No. Anything under ~/.claude/plugins is an installed copy owned by the marketplace; edits there evaporate on the next update. The audit marks such paths report-only and the fix belongs in the owning repository.

What should I do when a local skill duplicates a marketplace skill?▼

If the copies are byte-identical, retire the local one and repoint its callers. If they differ, read the diff first: a local copy that is ahead should be contributed upstream and retired only after the improvement lands.

Why does the audit say a tests directory exists but does not run?▼

A tests directory that imports a retired shim dies at collection, so a simple existence check reports it green while nothing actually executes. The audit collects the tests to distinguish existing from running.

Should I delete retired shim scripts during cleanup?▼

No. A retired shim that exits non-zero is a deliberate tombstone that makes stale callers fail loudly instead of silently skipping a guard. The audit only checks that tombstones are well formed, never that they should exist.