skill-issue
Audit and review all installed agent skills. Run on-demand or via cron to get a health report: skill inventory, usage tracking, version checks, dependency health, and actionable recommendations (keep, update, review, remove). Use when asked to review skills, check for skill updates, find unused skills, or audit the skill ecosystem.
Best use case
skill-issue is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Audit and review all installed agent skills. Run on-demand or via cron to get a health report: skill inventory, usage tracking, version checks, dependency health, and actionable recommendations (keep, update, review, remove). Use when asked to review skills, check for skill updates, find unused skills, or audit the skill ecosystem.
Teams using skill-issue should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/skill-issue/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How skill-issue Compares
| Feature / Agent | skill-issue | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Audit and review all installed agent skills. Run on-demand or via cron to get a health report: skill inventory, usage tracking, version checks, dependency health, and actionable recommendations (keep, update, review, remove). Use when asked to review skills, check for skill updates, find unused skills, or audit the skill ecosystem.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Skill Issue — Skill Auditor Audit all installed skills and produce a markdown report with recommendations. ## Quick Start ```bash # Basic — scans ./skills and ./memory node scripts/audit.mjs # Custom directories SKILL_DIRS="./skills,/path/to/more/skills" MEMORY_DIR="./memory" node scripts/audit.mjs # Save report node scripts/audit.mjs > /tmp/skill-audit-report.md ``` ## Environment Variables | Variable | Default | Description | |----------|---------|-------------| | `SKILL_DIRS` | `./skills` | Comma-separated skill directories to scan | | `MEMORY_DIR` | `./memory` | Dated markdown logs for usage tracking | | `AUDIT_DAYS` | `7` | Days back to scan for usage | ## What It Checks 1. **Inventory** — Finds every subdirectory containing a `SKILL.md` with YAML frontmatter 2. **Usage** — Scans recent memory/log files for skill name mentions 3. **Health** — Verifies required binaries (`requires.bins`) and env vars (`requires.env`) 4. **Versions** — Checks ClawdHub registry if `clawdhub` CLI is available 5. **Recommendations** — keep (active+healthy), update (outdated), review (unused), remove (broken deps) ## Safety - **Read-only** — Never modifies, installs, or removes anything - **Advisory only** — Recommendations require manual action
Related Skills
plan-issue
Plan-only workflow for issue/repo changes. Use when user asks to plan, scope, estimate, or design.
verify-issue
Verify a completed issue by comparing implementation against acceptance criteria, running tests, and critiquing the work. Adds review notes as a comment on the ticket. Supports both Linear and Jira backends via progressive disclosure. Use as the final step in the issue workflow after execute-issue, when the user mentions "verify", "review", or "check" an issue.
gh-issues
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5] [--notify-channel -1002381931352]
agentic-issue-assistant
Install common docs/backlog skeleton plus an AGENTS template, and wrap issue/finalization operations for an agentic workflow.
accessibility-issues
Use when animation excludes users with vestibular disorders, cognitive disabilities, or assistive technology needs
work-issue
issues/ディレクトリのタスクを1つ実装し、ブランチ作成・コミット・PR作成を行なうワークフロー
sentry-alerts-issues
Use when configuring Sentry alerts, managing issues, or setting up notifications. Covers alert rules, issue triage, and integrations.
issue-driven-delivery
Use when work is tied to a ticketing system work item and requires comment approval, sub-task tracking, or CLI-based delivery workflows.
github-issues
Create, manage, triage, and close GitHub issues. Search existing issues, add labels, assign people, and link to PRs. Works with gh CLI or falls back to git + GitHub REST API via curl.
github-issue
Work on a GitHub issue end-to-end: checkout main, create branch, research best practices, plan implementation, write tests first (TDD), implement, run code review, QA validation, then create PR. Use when given a GitHub issue URL or number to implement.
github-issue-creator
Convert raw notes, error logs, voice dictation, or screenshots into crisp GitHub-flavored markdown issue reports. Use when the user pastes bug info, error messages, or informal descriptions and wan...
fix-issue
Workflow for fixing GitHub issues from start to finish