skill-graph-audit

Featured

Audit Skill() refs; detect hubs, isolates, and dangling targets. Use when auditing skills.

AI & Automation 339 stars 35 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 94/100

Stars 20%
84
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Skill Graph Audit ## Overview 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. ## When To Use - Before a documentation pass on skill composition - After a renaming or retirement to catch broken `Skill()` references - During quarterly audits to spot orphaned skills - When evaluating consolidation candidates (hubs are higher-risk to merge) - When a new skill's outbound references should be sanity-checked ## When NOT To Use - For per-skill quality scoring, use `Skill(abstract:skills-eval)` instead - For frontmatter/structure validation, use `Skill(abstract:plugin-review)` - For hook-specific audits, use `Skill(abstract:hooks-eval)` ## Quick Start ```bash python3 plugins/abstract/scripts/skill_graph.py \ --plugins-root plugins --top-n 10 ``` For machine-readable output: ```bash 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. ## Core Outputs | Output | Meaning | Action when high | |--------|---------|------------------| | Hubs | Most-referenced skills | Treat as core API...

Details

Author
athola
Repository
athola/claude-night-market
Created
10 months ago
Last Updated
2 days ago
Language
Python
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

skill-auditor

Audit an Agent Skill or a repository of skills for trigger quality, scope overlap, instruction conflicts, progressive-disclosure cost, broken references/dependencies, eval blind spots, false-green paths, semantic-version and public-contract compatibility, host-support overclaims, package hygiene, supply-chain risks, migration/deprecation gaps, and drift between registry, docs, tests, and shipped archives. Use when the user asks to audit, review, roast, harden, compare, or quality-check a skill or skill library itself. Do not use to create/edit the skill (use skill-creator), to empirically benchmark model behavior with-vs-without it (use skill-evaluator), to audit ordinary software (use repo-roaster), or to issue a production release verdict.

1 Updated today
CometWeb-io
Data & Documents Listed

skill-audit

Audit installed Claude Code skills for context-budget cost and real usage. Inventories ~/.claude/skills, estimates the always-loaded token cost of each description, and mines ~/.claude/projects transcripts for actual invocations to find unused skills. Use when the user asks to "audit skills", "clean up skills", "find unused skills", "skill budget", "too many skills", or wonders what their skills cost in context.

2 Updated 3 days ago
magnusrodseth
AI & Automation Listed

skill-audit

Use when the user wants to audit, refresh, or prune repo skills; check skill rot or drift against source-of-truth files; classify skills KEEP / REFRESH / MERGE / PRUNE; or close the learn-on-the-job loop after distill-skill.

0 Updated 1 months ago
alexio777