skill-stocktake

Audit Claude Code skills and slash commands for redundancy and outdated entries.

Updated May 9, 2026
One-click install
npx skills add https://github.com/RambleRainbow/jd --skill skill-stocktake-ramblerainbow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-stocktake
Source: https://github.com/RambleRainbow/jd/tree/main/.claude/skills/skill-stocktake
Command: npx skills add https://github.com/RambleRainbow/jd --skill skill-stocktake-ramblerainbow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes scripts (resource) components.

What problem does it solve?

As you build out a library of custom Claude skills and slash commands, it becomes difficult to track which entries are still useful, up-to-date, non-redundant, and actively used. Manually reviewing each skill is time-consuming, inconsistent, and easy to overlook outdated references or overlapping functionality.

Core Features & Use Cases

  • Dual Audit Modes: Run a fast Quick Scan to only evaluate skills changed since your last audit, or a full Full Stocktake to review every skill in your global and project-level directories.
  • Holistic Quality Evaluation: Uses a standardized checklist to assess skill overlap, technical freshness, actionability, and usage frequency, with AI-powered judgment to assign clear Keep, Improve, Update, Retire, or Merge verdicts.
  • Usage Tracking: Integrates with Claude's observation logs to count how often each skill is used over 7 and 30 day windows, helping you prioritize updates for high-impact skills.
  • Use Case: If you have 30+ custom Claude skills accumulated over months, use this skill to quickly identify 5+ outdated or redundant skills to retire or merge, reducing clutter and improving your workflow efficiency.

Quick Start

Invoke the skill-stocktake command from your project root to run a full audit of all global and project-level Claude skills, or run it after a previous scan to only review recently changed skills.

Frequently Asked Questions about skill-stocktake

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit Claude Code skills and slash commands for quality?

You can audit Claude skills by running incremental quick scans or full stocktakes across global and project-level directories, evaluating technical freshness, overlap, and usage frequency to generate actionable Keep, Improve, or Retire verdicts.

What is the best way to clean up redundant or outdated custom Claude skills?

The best way to clean up redundant Claude skills is to perform a full stocktake that evaluates actionability and tracks usage from observation logs, identifying low-value entries to retire or merge.

How does usage frequency tracking work when evaluating Claude command quality?

Usage frequency tracking evaluates Claude command quality by integrating with observation logs to count how often each skill is invoked over 7 and 30 day windows, helping prioritize updates for high-impact skills.

Can I run a quick scan to only audit recently modified Claude skills?

Yes, you can run a quick scan to evaluate only Claude skills changed since your last audit by leveraging a timestamped JSON cache, enabling efficient incremental re-audits without reviewing the entire library.

Do I need jq installed to perform a Claude skill inventory scan?

Yes, you need jq installed as a dependency to execute the skill-stocktake script, which parses JSON data from skill directories and observation logs to generate structured evaluation verdicts.

What verdicts are assigned when reviewing a Claude skill library?

When reviewing a Claude skill library, the audit assigns standardized verdicts such as Keep, Improve, Update, Retire, or Merge based on a holistic checklist assessing overlap, technical freshness, and active usage.