lexielin99-code

Skill Curator — Development skill for Claude Code

Development community

A Claude Code meta-skill that lists, diagnoses, and tunes your installed skills — conflict detection, context-overload warnings, and trigger analysis in plain language.

How to install Skill Curator

This entry records only its repository, not the path inside it, so there is no exact command to give. Open lexielin99-code/skill-curator and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Skill Curator does

A Claude Code meta-skill that lists, diagnoses, and tunes your installed skills — conflict detection, context-overload warnings, and trigger analysis in plain language.

Alternatives in Development

Clean Worktree (Interactive) — Interactive cleanup of worktrees: lists merged/stale branches and asks confirmation before deleting 25.5k ★
Careful — Activate destructive command warnings for the session 2.8k ★
Magnitude — Open source inference server your agent sets up for you 1.5k ★

README

skill-curator

Manage the Claude Code skills installed on your machine — list, inspect, disable, enable, or remove across user, project, and plugin sources.

Skills in Claude Code are triggered by natural-language match against each skill's `description`. As your library grows past a dozen or so, it becomes hard to remember what you have, what will fire when, and what overlaps. **skill-curator** is a single skill that manages the others.

Scope

skill-curator only manages **filesystem SKILL.md files**. It deliberately does **not** track:

Claude Code built-in slash commands (/init, /review, /compact, etc.)
MCP server tools / prompts
Runtime-injected capabilities or harness-level agents
Files under ~/.claude/commands/ (those are slash commands, not skills)

The rule is simple: if there's a `SKILL.md` file under `~/.claude/skills/`, `/.claude/skills/`, or `~/.claude/plugins/cache////skills/`, curator manages it. Anything else is out of scope.

What it does

List every installed skill across all three sources (user / project / plugin), grouped by what they do (Write · Find · Build · Manage · Other). Each row shows the skill's one-line purpose, its concrete trigger context ("say 'draft a cold email'" / "when planning a multi-step project" / "type /name" / "auto on file edit"), and its source.
Diagnose proactively at the bottom of every list: name conflicts, bundled duplicates (e.g. you manually copied 14 skills from the same plugin — collapsed into one summary), and functionally overlapping skills. Each overlap ships with a side-by-side read: what's in common, what's different, which one to keep and why.
Tune triggers (tune-trigger ): append your own trigger keywords, switch a skill to manual-only, or change its scenario description. For plugin skills, curator forks them to your user directory first so updates don't overwrite your changes.
Disable / enable skills