Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
nomadamas avatar

K Skill Cleaner

  • 2.1k installs
  • 6.5k repo stars
  • Updated July 27, 2026
  • nomadamas/k-skill

k-skill-cleaner is an agent skill for Interview the user and inspect coding-agent skill trigger counts to recommend unused K-skills for removal.

About

The k-skill-cleaner skill Interview the user and inspect coding-agent skill trigger counts to recommend unused K-skills for removal. It covers do not delete skills automatically. Produce a ranked recommendation first, then make deletions only after the user explicitly approves the shortlist.. Key workflows include treat trigger counts as best-effort signals , not absolute truth. Different agents store transcripts differently and may rotate or omit logs.. Developers invoke k-skill-cleaner when the task matches the triggers and reference files in SKILL.md for grounded, stepwise execution. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation.

  • Do not delete skills automatically. Produce a ranked recommendation first, then make deletions only after the user expli
  • Treat trigger counts as best-effort signals , not absolute truth. Different agents store transcripts differently and may
  • Protect any skill the user marks as "keep", even if its trigger count is zero.
  • Prefer removing whole root-level skill directories only after checking README/docs/install references in the same change
  • 어떤 에이전트를 주로 쓰나요? Claude Code, Codex, OpenCode, OpenClaw/ClawHub, Hermes Agent, 기타

K Skill Cleaner by the numbers

  • 2,095 all-time installs (skills.sh)
  • +125 installs in the week ending Jul 28, 2026 (Skillselion tracking)
  • Ranked #264 of 1,881 Marketing & SEO skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
At a glance

k-skill-cleaner capabilities & compatibility

Capabilities
do not delete skills automatically. produce a ra · treat trigger counts as best effort signals , no · protect any skill the user marks as "keep", even · prefer removing whole root level skill directori · 어떤 에이전트를 주로 쓰나요? claude code, codex, opencode, o
Use cases
seo · marketing · copywriting
From the docs

What k-skill-cleaner says it does

description: Interview the user and inspect coding-agent skill trigger counts to recommend unused K-skills for removal.
SKILL.md
Use this skill when the user wants to slim down a K-skill bundle, find skills they never use, or make an evidence-backed deletion shortlist instead of deleting directories by guesswork.
SKILL.md
npx skills add https://github.com/nomadamas/k-skill --skill k-skill-cleaner

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs2.1k
repo stars6.5k
Security audit3 / 3 scanners passed
Last updatedJuly 27, 2026
Repositorynomadamas/k-skill

What problem does k-skill-cleaner solve for developers using the documented workflows?

Interview the user and inspect coding-agent skill trigger counts to recommend unused K-skills for removal.

Who is it for?

Developers working with k-skill-cleaner patterns described in the skill documentation.

Skip if: Skip when docs are empty or the task is outside the skill documented scope.

When should I use this skill?

Use when Interview the user and inspect coding-agent skill trigger counts to recommend unused K-skills for removal.

What you get

Actionable k-skill-cleaner guidance grounded in SKILL.md workflows and reference files.

  • Conservative skill removal shortlist
  • Scan report from folders and logs

By the numbers

  • Excludes 10+ standard root directories including .git, .cursor, .claude, and docs from scans

Files

SKILL.mdMarkdownGitHub ↗

k-skill-cleaner

Use this skill when the user wants to slim down a K-skill bundle, find skills they never use, or make an evidence-backed deletion shortlist instead of deleting directories by guesswork.

Safety contract

  • Do not delete skills automatically. Produce a ranked recommendation first, then make deletions only after the user explicitly approves the shortlist.
  • Treat trigger counts as best-effort signals, not absolute truth. Different agents store transcripts differently and may rotate or omit logs.
  • Protect any skill the user marks as "keep", even if its trigger count is zero.
  • Prefer removing whole root-level skill directories only after checking README/docs/install references in the same change.

Interview first

Ask a compact interview before scanning or recommending deletion:

1. 어떤 에이전트를 주로 쓰나요? (Claude Code, Codex, OpenCode, OpenClaw/ClawHub, Hermes Agent, 기타) 2. 절대 지우면 안 되는 스킬은 무엇인가요? 3. 본인이 절대로 쓰지 않는다고 확신하는 스킬은 무엇인가요? 4. 최근 30/90/180일 중 어떤 기간의 사용 흔적을 우선 볼까요? helper 실행 시 --days 또는 --since로 반영합니다. 5. 추천만 원하나요, 아니면 승인 후 실제 삭제까지 원하나요?

Trigger count sources by agent

AgentWhere to checkReliabilityNotes
Claude Code~/.claude/projects/**/*.jsonl, ~/.claude/transcripts/**/*.jsonlbest-effortLook for skill-trigger events, $skill-name mentions, and SKILL.md loads.
Codex~/.codex/sessions/**/*.jsonl, ~/.codex/log/**/*.log, .omx/logs/**/*.logbest-effortLook for routed skill names, explicit $skill invocations, and skill file reads.
OpenCode~/.local/share/opencode/**/*.jsonl, ~/.config/opencode/**/*.jsonlbest-effortIf local schema differs, ask the user for an exported transcript or usage JSON.
OpenClaw/ClawHub~/.openclaw/**/*.jsonl, ~/.clawhub/**/*.jsonl if presentmanual-confirmNo stable public local trigger-count schema is assumed; prefer exported stats when available.
Hermes Agent~/.hermes/**/*.jsonl, ~/.config/hermes/**/*.jsonl if presentmanual-confirmNo stable public local trigger-count schema is assumed; prefer exported stats when available.

Local helper

From an installed standalone skill, run the deterministic helper from the k-skill-cleaner skill directory. In a full repository checkout, the compatibility wrapper at scripts/k_skill_cleaner.py accepts the same options.

python3 scripts/k_skill_cleaner.py \
  --skills-root . \
  --scan-default-logs \
  --days 90 \
  --never-use blue-ribbon-nearby,lotto-results \
  --keep k-skill-setup,k-skill-cleaner

For agent exports or hand-curated counts, pass a JSON object mapping skill name to trigger count:

python3 scripts/k_skill_cleaner.py --skills-root . --usage-json usage-counts.json --days 90

--days and --since filter scanned log records only. --usage-json values are already-aggregated counts, so prepare/export that JSON for the same time window before passing it to the helper.

The helper prints JSON with:

  • skill_count: number of root-level skills discovered.
  • candidates: ranked remove or review candidates with trigger_count and reasons.
  • agent_usage_sources: the agent-specific paths and caveats above.
  • time_window: the effective --since/--days cutoff and mtime fallback caveat.
  • usage_json: whether imported counts were merged and the pre-windowing caveat.
  • scanned_logs: how many readable log files were scanned and which paths contributed best-effort evidence.
  • safety: reminder that no files were deleted.

Recommendation policy

  • remove: user explicitly marked the skill as never used. Mention any zero/low trigger evidence as supporting context.
  • review: trigger count is zero or below the selected low-usage threshold, but the user did not explicitly ask to remove it.
  • keep: user-protected skills and actively triggered skills.

When reporting, group recommendations like this:

1. 삭제 후보 — interview says never used, with trigger evidence. 2. 검토 후보 — zero/low trigger count only. 3. 보존 후보 — protected or recently used. 4. 통계 한계 — which agents had no readable logs and require manual export.

If deletion is approved

1. Remove the skill directory. 2. Remove README table/list entries and docs/features/<skill>.md links. 3. Remove docs/install.md --skill <skill> entries. 4. Remove package/workspace/test references only if the skill owns those files. 5. Run npm run lint, npm run typecheck, and npm run test (or npm run ci for packaging/release changes).

Related skills

FAQ

Who is k-skill-cleaner for?

Developers and software engineers working with k-skill-cleaner patterns described in the skill documentation.

When should I use k-skill-cleaner?

When Interview the user and inspect coding-agent skill trigger counts to recommend unused K-skills for removal.

Is k-skill-cleaner safe to install?

Review the Security Audits panel on this page before installing in production.

Marketing & SEOseocontent

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.