skills-manager
Skills Manager
Unified skill lifecycle management across agents.
Usage
/skills-manager # Quick status overview
/skills-manager list # All skills with origin, description, agent
/skills-manager search <query> # Search skills.sh ecosystem
/skills-manager install <source> # Install from ecosystem or GitHub
/skills-manager remove <name> # Remove a skill
/skills-manager inspect <name> # Deep-read: frontmatter, scripts, structure
/skills-manager validate [path] # Validate structure and frontmatter
/skills-manager audit # System-wide health check
/skills-manager update # Check and apply ecosystem updates
/skills-manager create # Guided creation (delegates to skill-creator)
Status (/skills-manager)
Quick overview of all installed skills.
bun ~/.claude/skills/skills-manager/scripts/manage.ts status
Shows: total count, breakdown by origin (local/ecosystem/symlink) and agent, lock file stats, validation issue count.
List (/skills-manager list)
All installed skills across agents with metadata.
Local skills:
bun ~/.claude/skills/skills-manager/scripts/manage.ts list
Ecosystem skills (via npx):
npx skills list -g
Present both outputs together — local list shows origin/agent/description, ecosystem list shows remote registry state.
Search (/skills-manager search )
Search the skills.sh ecosystem for installable skills.
npx skills find <query>
Present results with name, source, and install command. If no results, suggest npx skills find (interactive mode) or creating a custom skill.
Install (/skills-manager install )
Install a skill from the ecosystem or GitHub.
npx skills add <source> -g -y
Source formats:
owner/repo@skill-name— from skills.sh registryhttps://github.com/owner/repo— from GitHub directly- Local path — for development
The -g flag installs globally (user-level), -y skips confirmation.
After install, run validate to confirm the skill is well-formed:
bun ~/.claude/skills/skills-manager/scripts/manage.ts validate ~/.agents/skills/<name>
Remove (/skills-manager remove )
Remove an installed skill.
npx skills remove <name> -g -y
Inspect (/skills-manager inspect )
Deep-read a specific skill by name.
bun ~/.claude/skills/skills-manager/scripts/manage.ts inspect <name>
Shows: path, origin, agent, symlink target, frontmatter fields, scripts with size and executable status, references directory listing, SKILL.md heading structure.
Validate (/skills-manager validate [path])
Validate skill structure and frontmatter against the spec.
bun ~/.claude/skills/skills-manager/scripts/manage.ts validate <path>
Path can be:
- A single skill directory (containing SKILL.md)
- A directory of skills (e.g.,
~/.claude/skills)
Checks performed
Errors (blocking):
- SKILL.md exists with valid frontmatter
- Required fields: name, description
- Name: hyphen-case, max 64 chars, no leading/trailing/consecutive hyphens
- Description: 50+ chars, max 1024 chars, no angle brackets
- No forbidden files (README.md, CHANGELOG.md, etc.)
Warnings:
- Non-spec frontmatter keys (origin, inspired-by, hooks, status) — suggest metadata: migration
- Unexpected keys beyond spec-allowed set
- SKILL.md over 500 lines
- Scripts not executable
- Broken internal file references
Audit (/skills-manager audit)
System-wide health check across all agents.
bun ~/.claude/skills/skills-manager/scripts/manage.ts audit
Runs:
- Validation — every skill checked against spec
- Symlink health — dead symlinks flagged
- Lock file consistency — lock entries with missing directories
- Name overlap — same skill name across agents
Returns exit code 1 if any errors found.
Update (/skills-manager update)
Check for and apply ecosystem skill updates.
Check for updates:
npx skills check
Apply updates:
npx skills update
Create (/skills-manager create)
Delegates to the skill-creator skill for guided 6-step creation.
When user runs /skills-manager create:
- Invoke
/skill-creatorwhich provides the full guided workflow - After creation, run validate on the new skill:
bun ~/.claude/skills/skills-manager/scripts/manage.ts validate <new-skill-path>
Cross-Agent Reference
| Agent | Skills Dir | Lock File |
|---|---|---|
| Claude Code | ~/.claude/skills/ |
~/.agents/.skill-lock.json |
| Codex | ~/.codex/skills/ |
~/.agents/.skill-lock.json |
| Agents CLI | ~/.agents/skills/ |
~/.agents/.skill-lock.json |
All agents share the same lock file. The npx skills CLI auto-detects which agents are installed and manages skills for all of them.
Skill Conventions
- Frontmatter: name (hyphen-case), description (50-1024 chars), license (Apache-2.0)
- Structure: SKILL.md + optional scripts/, references/, assets/
- Forbidden: README.md, CHANGELOG.md, INSTALLATION.md, QUICK_REFERENCE.md
- Non-spec keys: origin, inspired-by, status, hooks — should migrate to metadata:
- Experimental skills:
status: experimentalin frontmatter (no directory prefix)
More from fairchild/dotclaude
backlog
Capture explored work as a backlog item for future implementation. Use when you've explored an enhancement, alternative approach, or feature but decided to defer it. Creates comprehensive plan files in backlog/ directory with enough context for a future session to execute efficiently.
20image-gen
Generate images using AI APIs (OpenAI gpt-image-1, Google Imagen 4, Nano Banana Pro, fal.ai Flux). Use when user asks to generate, create, or make an image.
16fork
Fork the current session with context carried over. Use `/fork <branch>` for a new worktree or `/fork --local` for a new session in the current directory.
10analyze-usage
Analyze AI coding assistant usage patterns across Claude Code and Cursor. Use when user asks about their coding usage, tool statistics, productivity patterns, skill popularity, session history, or wants to query their AI coding logs. Triggers include "usage", "how much have I used", "most used tools", "skill popularity", "coding stats", "productivity patterns".
2session-titles
Session title generation, evaluation, and optimization. Auto-generates context-aware titles via Stop hook. Includes quality evaluation (pattern checks, LLM judge), GEPA-inspired prompt evolution, golden dataset tooling, and interactive title rating for training data collection.
1status-line-live
Customize or troubleshoot the live status line. Use when modifying statusline.sh, debugging token display, or understanding the rendering pipeline. The status line runs passively -- this skill is for working on it, not using it.
1