claude-code-plugin-ref…
Explain plugin, skill, command, agent, and hook mechanics used here. Use when authoring or debugging plugins. Do not use for ops; use night-market-operations.
Audit Skill() refs; detect hubs, isolates, and dangling targets. Use when auditing skills.
$ npx -y skills add athola/claude-night-market --skill skill-graph-audit --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/skill-graph-auditContext preview
The summary Claude sees to decide when to auto-load this skill.
Audit Skill() refs; detect hubs, isolates, and dangling targets. Use when auditing skills.
name: skill-graph-audit role: library description: 'Audit Skill() refs; detect hubs, isolates, and dangling targets. Use when auditing skills.' category: skill-management alwaysApply: false tools: [] modules: - modules/usage.md - modules/interpretation.md
Build a directed graph of `Skill(plugin:name)` invocations across the marketplace and surface composition patterns: which skills are heavily referenced (hubs), which orchestrate many others (orchestrators), which have no incoming or outgoing references (isolates), and which point at non-existent skills (dangling references).
The federation graph is now derivable from source rather than hand-curated.
python3 plugins/abstract/scripts/skill_graph.py \ --plugins-root plugins --top-n 10
For machine-readable output:
python3 plugins/abstract/scripts/skill_graph.py \ --plugins-root plugins --format json --output reports/skill-graph.json
See `modules/usage.md` for full CLI reference and example workflows.
| Output | Meaning | Action when high | |--------|---------|------------------| | Hubs | Most-referenced skills | Treat as core API; retire with extreme care | | Orchestrators | Skills that call many others | Verify each ref still resolves | | Isolates | Zero in / zero out | Check role: library? entrypoint? typo? | | Dangling: bugs | Missing internal target | Fix immediately (typo or retired skill) | | Dangling: external | Reference to external plugin | Document plugin dependency | | Dangling: placeholders | Template text like `-NAME` | Verify intentional |
See `modules/interpretation.md` for false-positive guidance and isolation taxonomy.
This skill itself was scaffolded TDD-first; on first run against `plugins/`, it caught two genuine dangling refs that the manual audit (2026-04-25) had missed:
(script name confused with skill name)
(command referenced as skill)
Both were converted to correct command-style references in the same session.
Two ways to validate the audit output is trustworthy:
1. **Test-suite correctness check**: Run `pytest -o addopts= plugins/abstract/tests/scripts/test_skill_graph.py` to confirm extraction, graph construction, ranking, isolate detection, and dangling-ref classification all pass on the current code. The `-o addopts=` flag bypasses the package-wide coverage gate, which would otherwise fail on a single-file run. 2. **Round-trip smoke check**: Note the dangling-ref count from a baseline run, fix one or more flagged references, then rerun and verify the count drops by at least the number fixed. If the count does not move, the report is stale or the regex missed a syntax variant.
without error and emits a node/edge count.
placeholders (the three `Core Outputs` rows resolve).
session or filed as a tracked issue.
passes.
by at least the number of references fixed.
`docs/quality-gates.md#skill-level-quality-gate-composition`
A plugin marketplace for Claude Code. Install only the plugins you need to run git workflows, code review, spec-driven development, and autonomous agents from inside your Claude Code session.
Explain plugin, skill, command, agent, and hook mechanics used here. Use when authoring or debugging plugins. Do not use for ops; use night-market-operations.
States load-bearing decisions, invariants, and weak points. Use when judging a design change. Do not use for gating; use night-market-change-control.
Rebuild the dev environment: uv, Python tiers, pins, traps. Use when onboarding or toolchain breaks. Do not use for daily commands; use night-market-operations.
Classify, gate, and review changes. Use when landing a PR, releasing, or amending rules. Do not use for failure triage; use night-market-debugging-playbook.
Search and record project memory (Discussions, journal, ADRs). Use before re-investigating anything. Do not use for settled battles; see failure-archaeology.
Bind loop 'done' to unfakeable gates. Use to harden egregore/herald loops or promote completion_integrity. Not for QA gates; use night-market-validation-and-qa.