Use when the user wants quality/health analysis of an existing resource list — flag stale repos, low-star entries, dead links, or surface what's worth pruning. Triggers — "audit the <topic> list", "find stale entries in...", "filter out repos under N stars that haven't been updated", "what should I cut from this list".
npx claudepluginhub danielrosehill/claude-code-plugins --plugin resource-list-builderThis skill uses the workspace's default tool permissions.
Run a health/quality pass over an existing resource list. Read-only by default — only mutates the list if the user approves a pruning plan.
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Share bugs, ideas, or general feedback.
Run a health/quality pass over an existing resource list. Read-only by default — only mutates the list if the user approves a pruning plan.
Read the README and extract every OWNER/REPO link.
Fetch metadata in parallel for each entry:
gh repo view OWNER/REPO --json stargazerCount,pushedAt,isArchived,description -q '{s:.stargazerCount,p:.pushedAt,a:.isArchived,d:.description}'
For 404s, mark dead.
Bucket the entries:
dead — 404, moved, or archived with no successor.stale — last push older than the staleness threshold.low-star — below the star threshold AND not flagged as a niche/early-stage exception by the user.description-drift — current GitHub description differs significantly from what the README says.healthy — passes all checks.Render a report as a markdown table sorted worst-first. Include section, project, stars, last push, flag(s).
Optionally write the report to outputs/<list-name>-audit-<YYYY-MM-DD>.md in the list repo if the user wants it kept.
Offer a pruning plan — list of removals + section renames the user could apply. Wait for explicit approval before mutating the README.
If approved, execute the prune — drop rows, update Contents TOC, commit:
git add -A && git commit -m "Audit prune: <N removed, N updated>"git pushupdate-resource-list decision.gh starts throttling, switch to sequential fetches with a small sleep, or batch via gh api graphql.