skill-review
Audit and maintain the joelclaw skill inventory. Use when checking skill health, fixing broken symlinks, finding stale skills, or running the skill garden. Triggers: 'skill audit', 'check skills', 'stale skills', 'skill health', 'skill garden', 'broken skill', 'skill review', 'fix skills', 'garden skills', or any task involving skill inventory maintenance.
- Installs
- 55
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/joelhooks/joelclaw --skill skill-review- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads skill-review automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Skill review
Audit the installed inventory against canonical sources and live evidence. Resolve symlinks before editing; installed roots may expose several repositories and namespaced packs. Inspect repository status and preserve existing edits.
Inventory
List skill roots and canonical targets. Record duplicate names, broken links, missing frontmatter, trigger overlap, and large entry files. Distinguish managed sources from vendor or plugin caches. Do not treat a directory as an orphan merely because one consumer root lacks a direct link.
Read the candidate before changing it. Check commands against live help or source, runtime facts against current configuration, and behavioral rules against the user request and harness hierarchy. An old AGENTS.md is evidence to review, not proof of live topology.
Prune and repair
Keep name, provenance, invocation metadata, operational constraints, and domain-specific gotchas. Remove repeated trigger lists, stale model pins, copied command manuals, duplicated global policy, and approval gates that disregard authorization already given.
Disclose branch-specific reference material behind an explicit trigger. Preserve its links. Do not replace useful runbooks with empty pointers or update vendor caches as if they were canonical.
Use joelclaw skills ensure --help for supported install repairs. Inspect real-directory conflicts before replacing anything. Add or change install manifests in their owning repository.
Verify
Check metadata, link targets, affected commands, and prompt installation where relevant. Use realistic before/after model cases for substantial behavior changes. Include an already-authorized action, missing input, a near-miss trigger, and a boundary that must hold. Separate static findings from observed execution.
Report every scanned source's disposition: changed, reviewed without change, or needs deeper review. Save unresolved findings with paths and reasons. A broad pattern scan is not a full semantic review.
The optional garden implementation is packages/system-bus/src/inngest/functions/skill-garden.ts. Inspect its current events, patterns, and schedule before invoking it; a manual audit does not require starting a background workflow.
FAQ
What does the skill-review skill do?
Audit and maintain the joelclaw skill inventory. Use when checking skill health, fixing broken symlinks, finding stale skills, or running the skill garden. Triggers: 'skill audit', 'check skills', 'stale skills', 'skill health', 'skill garden', 'broken skill', 'skill review', 'fix skills', 'garden skills', or any task involving skill inventory maintenance.
How do I install skill-review?
Run npx skills add https://github.com/joelhooks/joelclaw --skill skill-review in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/skill-review/ (personal) or .claude/skills/skill-review/ (project).
Which AI agents can use skill-review?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is skill-review safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains skill-review?
It is published by joelhooks in joelhooks/joelclaw. It has 55 recorded installs.
More from joelhooks/joelclaw
contacts
joelhooks/joelclaw
Add, enrich, and manage contacts in Joel's Vault. Fire the Inngest enrichment pipeline for full multi-source dossiers, or create quick contacts manually. Use when: 'add a contact', 'enrich this person', 'who is X', 'VIP contact', 'update contact', or any task involving the Vault/Contacts directory.
cli-design
joelhooks/joelclaw
Design and build agent-first CLIs with HATEOAS JSON responses, context-protecting output, and self-documenting command trees. Use when creating new CLI tools, adding commands to existing CLIs such as joelclaw, or reviewing CLI design for agent-friendliness. Triggers on 'build a CLI', 'add a command', 'CLI design', 'agent-friendly output', or any task involving command-line tool creation.
docker-sandbox
joelhooks/joelclaw
Create, manage, and execute agent tools (claude, codex) inside Docker sandboxes for isolated code execution. Use when running agent loops, spawning tool subprocesses, or any task requiring process isolation. Triggers on "sandbox", "isolated execution", "docker sandbox", "safe agent execution", or when working on agent loop infrastructure.
granola
joelhooks/joelclaw
Access and process Granola meeting notes and transcripts via the granola CLI (MCP-backed). Use when pulling meeting data, analyzing transcripts, backfilling meetings, or any task involving Granola meeting content.
k8s
joelhooks/joelclaw
Operate the joelclaw Kubernetes cluster — Talos Linux on Colima (Mac Mini). Deploy services, check health, debug pods, recover from restarts, add ports, manage Helm releases, inspect logs, fix networking. Triggers on: 'kubectl', 'pods', 'deploy to k8s', 'cluster health', 'restart pod', 'helm install', 'talosctl', 'colima', 'nodeport', 'flannel', 'port mapping', 'k8s down', 'cluster not working', 'add a port', 'PVC', 'storage', any k8s/Talos/Colima infrastructure task. Also triggers on service-specific deploy: 'deploy redis', 'redeploy inngest', 'livekit helm', 'pds not responding'.
joel-writing-style
joelhooks/joelclaw
Joel's writing voice and style guide for joelclaw.com content. Use when writing, editing, or reviewing any blog post, essay, book chapter, or prose content for joelclaw.com. Also use when asked to 'write like Joel,' 'match Joel's voice,' 'draft a post,' 'write content for the blog,' or 'review this for voice.' This skill captures Joel's specific writing patterns derived from 90,000 words of published content spanning 2012–2026. Cross-reference with copy-editing and copywriting skills for marketing-specific copy.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.