Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From skills-cleaner
Lists all installed skills grouped by source (project, personal, plugin), showing which plugin each belongs to with keyword-style descriptions.
npx claudepluginhub amebahead/skills-cleaner --plugin skills-cleanerHow this skill is triggered — by the user, by Claude, or both
Slash command
/skills-cleaner:list-skillsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Show all installed skills with their source (project / personal / plugin) and a short purpose hint, names emphasised for scannability.
Reports loaded skill inventory layered by bkit core vs project-local, detects naming conflicts and trigger overlaps, and displays coverage gaps. Useful for debugging skill activation, onboarding, or auditing a workspace.
Searches Claude Code skills across local ~/.claude/skills, skills.sh CLI directory, and GitHub fallback. Outputs markdown table and JSON with install info, sorted by source.
Manages Claude Code skills: lists existing ones via script, improves for optimal auto-activation, creates new from prompts or spec files.
Share bugs, ideas, or general feedback.
Show all installed skills with their source (project / personal / plugin) and a short purpose hint, names emphasised for scannability.
The bundled script scans three locations — project (<cwd>/.claude/skills/**, walking up to find the nearest one), personal (~/.claude/skills/**), and plugin cache (~/.claude/plugins/cache/**) — extracts each skill's frontmatter, deduplicates across versions, shortens each description to a keyword-style summary, and groups the result. Project skills come first when present, then personal, then plugin groups alphabetically.
Run the script in a single Bash call with no flags — nothing else. The script auto-detects the user's Claude Code verbose setting (~/.claude/settings.json, with ~/.claude/settings.local.json taking precedence) and routes its own output:
python3 "${CLAUDE_PLUGIN_ROOT}/skills/list-skills/scripts/collect_skills.py"
verbose: true → prints the ANSI-colored text table to stdout. The Bash result panel shows the full table directly.verbose !== true → writes the markdown version to ~/.claude/.cache/skills-cleaner-list.md and prints only wrote: <path> to stdout (so the Bash panel stays compact).After the script returns:
Installed Skills appears in the Bash output), stay silent — do not re-paste, summarize, or reformat.wrote:), Read that file and paste its contents verbatim as plain markdown — NOT inside a fenced code block. Pasting in a code block would show literal `name` instead of rendered skill names. The pasted markdown becomes the user's only visible output. Don't rephrase or reformat.Never read ~/.claude/settings.json yourself, never run grep/cat beforehand, and never add commentary before or after unless the user follows up. The script handles verbose detection internally so the user only sees the result.
Explicit flags (--format, --out, --color) skip the auto-routing and behave as documented below.
--no-project — skip the project-local scan (useful when the cwd is irrelevant).--project-dir <path> — point the project scan somewhere other than $PWD.--format json — raw array, for piping into other tooling.