jiepi-skill
New洁癖 Skill: Audit installed AI agent skills across Codex, Claude Code, Cursor, and optional project-local skill folders. Use when the user asks which skills are installed, how often Claude Code/Codex/Cursor used skills, whether a skill was used recently, which skills are stale or unused, or wants cleanup/removal/disable recommendations for skills.
Summary
洁癖 Skill audits installed AI agent skills across Codex, Claude Code, Cursor, and optional project-local folders.
- It inventories skills, counts confirmed usage, shows recent activity, and provides cleanup recommendations to help developers manage their skill ecosystem efficiently.
Overview
洁癖 Skill
Overview
Use this skill to inventory installed skills, count confirmed historical usage, show recent activity, and produce cleanup recommendations. Prefer the bundled script for deterministic scanning instead of hand-writing ad hoc searches.
Workflow
- Run
scripts/audit_skill_usage.pyfrom this skill folder. - Use the default scan for installed/synced skills:
``bash python3 scripts/audit_skill_usage.py --format markdown ``
- Add
--include-project-localonly when the user explicitly wants repository-local skills under Desktop/Documents included. This can find many source/test/example skills that are not globally installed. - Use
--days Nto define the recent-use window. Default is 30 days. - Save a report when useful:
``bash python3 scripts/audit_skill_usage.py --format markdown --output /tmp/skill-usage.md ``
Counting Rules
- •Treat the default call count as confirmed usage: a historical transcript or rollout explicitly referenced/read the skill's
SKILL.md. - •Do not count system/developer skill lists as usage.
- •Count each skill at most once per log line or tool call.
- •Prefer cleanup suggestions phrased as
keep,review, orcleanup-candidate; do not delete files automatically unless the user separately asks for removal. - •For plugin-provided skills, suggest disabling the plugin or reviewing plugin value before deleting cache files.
Interpreting Results
- •
keep: used recently or used often enough historically. - •
review: used before, but not inside the recent-use window. - •
cleanup-candidate: no confirmed usage found in available histories. - •
scope: distinguishescodex,claude,cursor, andproject-localsources so installed tools are not mixed with repository examples.
When presenting results, lead with totals, the top used skills, and the cleanup candidates. Mention the counting rule so the user understands that unconfirmed use may be undercounted.
Install & Usage
mkdir -p .claude/skillsmkdir -p .claude/skills && curl -o .claude/skills/jiepi-skill.md https://raw.githubusercontent.com/Pluviobyte/jiepi-skill/main/SKILL.md/jiepi-skillUse Cases
Usage Examples
/jiepi-skill audit my installed skills and show me which ones I haven't used in the last 30 days.
Run the skill audit script and output a markdown report to /tmp/skill-usage.md.
Check if any skills in my project-local folders are stale and suggest cleanup candidates.
Security Audits
Frequently Asked Questions
What is jiepi-skill?
洁癖 Skill audits installed AI agent skills across Codex, Claude Code, Cursor, and optional project-local folders. It inventories skills, counts confirmed usage, shows recent activity, and provides cleanup recommendations to help developers manage their skill ecosystem efficiently.
How to install jiepi-skill?
To install jiepi-skill: create the skills directory (mkdir -p .claude/skills), then run: mkdir -p .claude/skills && curl -o .claude/skills/jiepi-skill.md https://raw.githubusercontent.com/Pluviobyte/jiepi-skill/main/SKILL.md. Finally, /jiepi-skill in Claude Code.
What is jiepi-skill best for?
jiepi-skill is a skill categorized under General. It is designed for: agent. Created by Pluviobyte.
What can I use jiepi-skill for?
jiepi-skill is useful for: List all installed skills and see how often each has been used historically.; Identify skills that haven't been used recently and may be candidates for cleanup.; Get a report of skill usage for a specific time window, like the last 30 days.; Review project-local skills in Desktop or Documents folders for potential removal.; Generate a markdown report of skill audit results to share with a team or save for later.; Decide which skills to keep, review, or remove based on usage data and recommendations..