← ClaudeAtlas

skill-managerlisted

Install, list, and remove community skills from GitHub or local paths. Triggers on /agent:skill, /agent:skill install, /agent:skill list, /agent:skill remove, "instalar skill", "listar skills", "remover skill", "eliminar skill", "agregar skill", "install skill from github".
crisandrews/ClawCode · ★ 56 · AI & Automation · score 84
Install: claude install-skill crisandrews/ClawCode
# Skill Manager Add community skills to this agent, list what's installed, or remove what you no longer want. A "skill" here is a directory with a `SKILL.md` — the same format Claude Code natively uses — so the exact same artifact works in either place. This is a CORE feature. See `docs/skill-manager.md` for the full reference. ## Dispatch Parse the user's command and route to the correct MCP tool: | User says | Action | |---|---| | `/agent:skill install <source>` | Call `skill_install({ source })` | | `/agent:skill install <source> --scope=<plugin\|project\|user>` | Call `skill_install({ source, scope })` | | `/agent:skill install <source> --force` | Call `skill_install({ source, force: true })` — only after the user confirms an overwrite | | `/agent:skill list` | Call `skill_list()` and print the card | | `/agent:skill remove <name>` | Call `skill_remove({ name })` (dry run) then ask the user to confirm, then call again with `confirm: true` | | `/agent:skill remove <name> --force` | Call `skill_remove({ name, confirm: true })` directly — no confirmation prompt | Default scope is `plugin` (`./skills/`). Users can promote a skill later. ## Install flow 1. Validate the source (GitHub shorthand, full URL, or local path — the tool parses all three) 2. Call `skill_install({ source })` — the tool clones, detects format, checks requirements 3. Print the returned card verbatim 4. If `format: openclaw` was detected (rejected), DO NOT retry with `force`. Suggest `/agent:import