k-skill-cleaner

Analyze local agent logs to rank K-skill directories into remove, review, or keep groups.

7.1k|836|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/NomaDamas/k-skill --skill k-skill-cleaner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: k-skill-cleaner
Source: https://github.com/NomaDamas/k-skill/tree/main/k-skill-cleaner
Command: npx skills add https://github.com/NomaDamas/k-skill --skill k-skill-cleaner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

K-skill bundle directories grow over time, and deleting the wrong one can break workflows; this Skill helps you identify never-used candidates using best-effort agent trigger evidence, while keeping deletions user-approved.

Core Features & Use Cases

  • Interview-driven cleanup planning: asks which agents you use, which skills to keep, which ones you never use, and what time window to analyze.
  • Best-effort trigger counting from agent logs: scans local JSONL/log files for skill mentions and SKILL.md load markers, with support for importing pre-aggregated usage counts.
  • Conservative ranked recommendations: produces deletion vs review vs keep groups and includes evidence and limitations so you can decide safely.

Quick Start

Ask the agent to run the k-skill-cleaner helper to scan your last 90 days of usage logs and output a ranked shortlist of K-skills to review or delete, without deleting anything automatically.

Frequently Asked Questions about k-skill-cleaner

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

FAQPage Schema
How do I find unused skills in my coding agent bundle?

To find unused skills in a coding agent bundle, you can analyze local agent trigger logs and usage counts over a configurable time window to identify never-loaded candidates for safe removal.

Can I automate cleanup of unused Claude Code or Codex skills without breaking workflows?

Yes, you can automate cleanup planning for agent skills across platforms like Claude Code and Codex by scanning usage logs for trigger evidence and generating user-approved removal shortlists without automatic filesystem deletions.

What is the best way to analyze coding agent usage logs for dependency hygiene?

The best way to analyze coding agent usage logs for dependency hygiene is to deterministically scan local JSONL files for skill mentions and SKILL.md load markers, then rank candidates into remove, review, and keep groups.

Does the skill removal process support pre-aggregated usage data imports?

Yes, the skill removal process supports pre-aggregated usage data imports by allowing you to supply a pre-aggregated usage JSON file as an alternative to scanning local agent logs directly within the time window.

What are the limitations of automated skill bundle slimming for coding agents?

Limitations of automated skill bundle slimming include best-effort trigger counting that may miss usage evidence, a mandatory interview to protect kept skills, and a strict prohibition against performing filesystem deletions automatically.