skills-management
Centralized manager for searching, installing, and updating AI coding agent skills.
Install
mkdir -p .claude/skills/skills-management && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11268" && unzip -o skill.zip -d .claude/skills/skills-management && rm skill.zipInstalls to .claude/skills/skills-management
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Search, find, discover, install, remove, update, review, list, and move skills for AI coding agents. Use when user asks "find a skill for X", "search for a skill", "is there a skill for X", "install skill", "remove skill", "update skills", "list skills", "review skill quality", "move skill", "check for updates", or "how do I do X" where X might have an existing skill. This is THE tool for skill discovery and ecosystem search.Key capabilities
- →Search and discover skills
- →Install skills from GitHub
- →Update and remove skills
- →Manage multi-agent skill distribution
How it works
Provides a CLI interface to manage skill directories across different AI agent environments.
Inputs & outputs
When to use skills-management
- →Find skill for specific task
- →Install new coding assistant skill
- →Check for skill updates
- →Remove unused agent extensions
About this skill
Skills Manager
Quick Reference
| Task | Command |
|---|---|
| List all | python3 scripts/list_skills.py |
| List by scope | python3 scripts/list_skills.py -s user or -s project |
| Show details | python3 scripts/show_skill.py <name> |
| Review skill | python3 scripts/review_skill.py <name> |
| Delete | python3 scripts/delete_skill.py <name> |
| Delete from agents | python3 scripts/delete_skill.py <name> --all-agents --force |
| Move to user | python3 scripts/move_skill.py <name> user |
| Move to project | python3 scripts/move_skill.py <name> project |
| Create new | Use /skill-creator |
| Discovery & Install | |
| Find skills | npx skills find [query] |
| Review remote skills | Fetch skills.sh pages, assess using assessment framework |
| List ecosystem skills | npx skills list or npx skills ls |
| Install from GitHub | npx skills add <owner/repo@skill> -g -y |
| Remove ecosystem skill | npx skills remove <name> -g -y or npx skills rm |
| Check for updates | npx skills check |
| Update all | npx skills update |
| Browse online | skills.sh |
| Multi-Agent | |
| Detect agents | python3 scripts/detect_agents.py |
| List agent skills | python3 scripts/list_agent_skills.py --agent cursor |
| Install to agent | python3 scripts/install_skill.py /path --agent cursor |
| Copy between agents | python3 scripts/copy_skill.py <name> --from claude-code --to cursor |
| Move between agents | python3 scripts/move_skill_agent.py <name> --from claude-code --to cursor |
Scopes
| Scope | Path | Visibility |
|---|---|---|
| User | ~/.claude/skills/ | All projects for this user |
| Project | .claude/skills/ | This repository only |
User scope takes precedence over project scope for skills with the same name.
Operations
List Skills
python3 scripts/list_skills.py # All skills
python3 scripts/list_skills.py -s user # User scope only
python3 scripts/list_skills.py -f json # JSON output
Show Skill Details
python3 scripts/show_skill.py <name> # Basic info
python3 scripts/show_skill.py <name> --files # Include file listing
python3 scripts/show_skill.py <name> -f json # JSON output
Review Skill
Audits a skill against best practices and suggests improvements:
python3 scripts/review_skill.py <name> # Review with text output
python3 scripts/review_skill.py <name> -f json # JSON output for programmatic use
Checks performed:
- Name format (lowercase, hyphens, max 64 chars, gerund form)
- Description quality (triggers, third person, specificity)
- Body length (warns if >500 lines)
- Time-sensitive content
- Path format (no Windows backslashes)
- Reference depth (should be one level)
- Table of contents for long files
After reviewing: Read the skill's SKILL.md and apply the suggested fixes directly.
Delete Skill
CRITICAL: Always use AskUserQuestion to confirm before deleting: "Are you sure you want to delete the skill '[name]'? This cannot be undone."
python3 scripts/delete_skill.py <name> # Claude Code only, with confirmation
python3 scripts/delete_skill.py <name> --force # Skip confirmation prompt
python3 scripts/delete_skill.py <name> -s project # Target specific scope
python3 scripts/delete_skill.py <name> -a cursor # Delete from specific agent
python3 scripts/delete_skill.py <name> --all-agents --force # Delete from all agents
Multi-agent deletion: Skills installed via npx skills add may exist in multiple agent directories. The default mode (no flags) deletes from Claude Code only and warns if copies remain in other agents. Use --all-agents to delete from every detected agent at once.
For ecosystem-installed skills, prefer npx skills remove <name> -g -y first. Use delete_skill.py --all-agents as fallback for manual cleanup.
Move Skill
python3 scripts/move_skill.py <name> user # Project → User (personal)
python3 scripts/move_skill.py <name> project # User → Project (share with team)
python3 scripts/move_skill.py <name> user -f # Overwrite if exists
Modify Skill
- Run
python3 scripts/show_skill.py <name>to locate it - Edit SKILL.md directly at the returned path
Create New Skill
Use the /skill-creator skill for guided creation with proper structure.
Discover & Install Skills
Search and install skills from the open agent skills ecosystem via the Skills CLI (npx skills). Browse at skills.sh.
Find Skills
npx skills find [query] # Interactive search
npx skills find react performance # Keyword search
npx skills find pr review # Search by task
Install from Ecosystem
npx skills add <owner/repo@skill> -g -y # Install globally, skip prompts
npx skills add vercel-labs/agent-skills@vercel-react-best-practices -g -y
List Ecosystem Skills
npx skills list # List all installed ecosystem skills
npx skills ls # Alias
npx skills list -g # Global skills only
npx skills list -a cursor # Skills for a specific agent
Remove Ecosystem Skills
Uninstalls skills installed via npx skills add. For locally-created skills, use python3 scripts/delete_skill.py instead.
CRITICAL: Always confirm with the user before removing.
npx skills remove <name> -g -y # Remove a global skill, skip prompt
npx skills rm <name> # Alias, with confirmation prompt
npx skills remove <name> -a cursor # Remove from specific agent
npx skills remove --all -g -y # Remove all global ecosystem skills
Check & Update
npx skills check # Check for available updates
npx skills update # Update all installed skills
When the user asks to "update skills", "update all skills", "are my skills up to date?", or "check for updates":
- Run
npx skills checkfirst to show what has updates available - If updates exist, confirm with user before running
npx skills update - After updating, remind user to restart the agent for changes to take effect
When to Search
Use npx skills find when the user:
- Asks "how do I do X" where X is a common task
- Says "find a skill for X" or "is there a skill for X"
- Wants specialized capabilities (design, testing, deployment, etc.)
Common Search Categories
| Category | Example queries |
|---|---|
| Web Dev | react, nextjs, typescript, tailwind |
| Testing | testing, jest, playwright, e2e |
| DevOps | deploy, docker, kubernetes, ci-cd |
| Docs | docs, readme, changelog, api-docs |
| Quality | review, lint, refactor, best-practices |
| Design | ui, ux, design-system, accessibility |
| Productivity | workflow, automation, git |
Review & Compare Results
Always suggest reviewing found skills after a search. After presenting search results, ask the user if they'd like you to review and compare the top candidates before installing.
When there are 2+ results, proactively offer to fetch and assess the top candidates. This is agent-driven — use WebFetch on https://skills.sh/<owner>/<repo>/<skill> pages and apply judgment.
Always offer review when:
- Any search returns results (ask: "Want me to review these skills before you install?")
- 3+ results returned — review is especially valuable
- Multiple results with similar names or overlapping descriptions
- User asks to compare, review, evaluate, or pick the best
- A result has suspicious metrics (niche topic with very high installs)
Process:
- Present the search results summary first
- Ask the user if they want you to review/compare the top candidates
- If yes: fetch skills.sh pages for top 3-6 candidates
- Evaluate quality signals: install count, agent distribution, age, description, relevance, overlap with installed skills
- Assign verdict: Recommended / Consider / Skip
- Present ranked summary with 1-2 sentence assessments
See references/remote-skill-assessment.md for the full assessment framework including red flags and scoring signals.
No Results
If no skills found: offer to help directly, then suggest npx skills init <name> to create a custom skill.
Multi-Agent Operations
Manage skills across 42 supported AI coding agents. Full registry at skills.sh.
Supported Agents
| Agent ID | Display Name | Project Skills Dir | Global Skills Dir |
|---|---|---|---|
adal | AdaL | .adal/skills | ~/.adal/skills |
amp | Amp | .agents/skills | ~/.config/agents/skills |
antigravity | Antigravity | .agent/skills | ~/.gemini/antigravity/skills |
augment | Augment | .augment/skills | ~/.augment/skills |
claude-code | Claude Code | .claude/skills | ~/.claude/skills |
cline | Cline | .cline/skills | ~/.cline/skills |
codebuddy | CodeBuddy | .codebuddy/skills | ~/.codebuddy/skills |
codex | Codex | .agents/skills | ~/.codex/skills |
command-code | Command Code | .commandcode/skills | ~/.commandcode/skills |
continue | Continue | .continue/skills | ~/.continue/skills |
crush | Crush | .crush/skills | ~/.config/crush/skills |
cursor | Cursor | .cursor/skills | ~/.cursor/skills |
droid | Droid | .factory/skills | ~/.factory/skills |
gemini-cli | Gemini CLI | .agents/skills | ~/.gemini/skills |
github-copilot | GitHub Copilot | .agents/skills | ~/.copilot/skills |
goose | Goose | .goose/skills | ~/.config/goose/skills |
iflow-cli | iFlow CLI | .iflow/skills | ~/.iflow/skills |
junie | Junie | .junie/skills | `~/.junie/skill |
Content truncated.
When not to use it
- →When manual file system manipulation is preferred
- →When agent environment is restricted
Prerequisites
Limitations
- →Requires restart of AI agent for changes to take effect
How it compares
Centralizes skill management across multiple agents rather than manual directory editing.
Compared to similar skills
skills-management side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| skills-management (this skill) | 0 | 5mo | Review | Beginner |
| using-superpowers | 95 | 3mo | No flags | Beginner |
| ultrawork | 11 | 2mo | No flags | Advanced |
| clawhub | 25 | 2mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by diegosouzapw
View all by diegosouzapw →You might also like
using-superpowers
obra
Use when starting any conversation - establishes mandatory workflows for finding and using skills, including using Skill tool before announcing usage, following brainstorming before coding, and creating TodoWrite todos for checklists
ultrawork
Yeachan-Heo
Parallel execution engine for high-throughput task completion
clawhub
openclaw
Use the ClawHub CLI to search, install, update, and publish agent skills from clawhub.com. Use when you need to fetch new skills on the fly, sync installed skills to latest or a specific version, or publish new/updated skill folders with the npm-installed clawhub CLI.
skill-installer
openai
Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).
continuous-learning
affaan-m
Automatically extract reusable patterns from Claude Code sessions and save them as learned skills for future use.
memory-keeper-proactive-context-maintenance
b4CU-R4U
Automatically detect and maintain memory freshness by monitoring context staleness, significant code changes, task completions, and phase transitions. Proactively suggests and executes memory sync operations with user confirmation. Use when the user says "sync memory", "update context", or when the Skill detects that context is stale (>2 hours), significant changes have occurred (new commits), tasks completed, or major milestones reached. Replaces passive "context is stale" warnings with active maintenance.