skill-manager
Skill64 starsChanged 2 months agoMITView on GitHub
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".
52 other projects use a version of this.
Adopted by
Most recently taken up by
- Adelie-Squad/solosquadtheir own version, first seen Nov 8, 2026
- jerry-guo-mys/skillstheir own version, first seen Nov 8, 2026
- Melvynx/ai-sprint-skillstheir own version, first seen Nov 8, 2026
- Melvynx/ai-maxxing-skillstheir own version, first seen Nov 1, 2026
- ZhangShixing0/skill-centertheir own version, first seen Nov 1, 2026
- thefrederiksen/devthrottletheir own version, first seen Nov 1, 2026
Used with
Projects with it also use Skill Evolution Manager, github-to-skills and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Arthur-devroleSkillSkill Evolution Manager
专门用于在对话结束时，根据用户反馈和对话内容总结优化并迭代现有 Skills 的核心工具。它通过吸取对话中的“精华”（如成功的解决方案、失败的教训、特定的代码规范）来持续演进 Skills 库。
Also in 5 projects that use this
- Arthur-devroleSkill
github-to-skills
Automated factory for converting GitHub repositories into specialized AI skills. Use this skill when the user provides a GitHub URL and wants to "package", "wrap", or "create a skill" from it. It automatically fetches repository details, latest commit hashes, and generates a standardized skill structure with enhanced metadata suitable for lifecycle management.
Also in 5 projects that use this
NVIDIASkillreview-code
Review a code repository for concrete issues in correctness, robustness, security, maintainability, tests, and integration. Use for repository-wide or focused code review where practical engineering judgment and strict scope control matter.
Also in 3 projects that use this
SentrySkillskill-creator
Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.
Also in 12 projects that use this
OpenAISkillbrainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Also in 4 projects that use this
Microsoft AzureSkillhumanizer
Tone enforcement patterns for external-facing community responses
Also in 3 projects that use this
Other versions52 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 52
- anthropics/claude-for-legal★ 9.5ksame name
- buzhangsan/skill-manager★ 321same name
- thefrederiksen/cc-director★ 110same name
- thefrederiksen/devthrottle★ 110same name
- egebese/skill-manager★ 38same name
- GeekFamilyCorp/TricorderKit★ 32same name
- Melvynx/ai-maxxing-skills★ 32same name
- Starchild-ai-agent/official-skills★ 32same name
- Adelie-Squad/solosquad★ 25same name
- Interstellar-code/claud-skills★ 17same name
42 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository23 other files it gives its agents.
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 0 are common, 5 are distinctive, and 9 are very specific to this project.
0
Common
Most of the 32 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Add community skills to this agent, list what's installed, or remove what you no longer want.
- Very specific: line 27
Default scope is plugin (./skills/).
- Very specific: line 32
Call skill_install({ source }) — the tool clones, detects format, checks requirements
- Very specific: line 34
If format: openclaw was detected (rejected), DO NOT retry with force.
- Distinctive: line 35
If the skill installed with warnings, remind the user what needs to be set up (missing env var, binary, etc.)
- Very specific: line 44
Call skill_remove({ name }) first — this is a dry run.
- Distinctive: line 45
Ask the user: "Remove <name> from <dir>?
- Very specific: line 46
If they confirm, call skill_remove({ name, confirm: true })
- Distinctive: line 47
If they say no, just acknowledge and stop
- Very specific: line 49
If the user passed --force, skip step 2 and call directly with confirm: true.
- Distinctive: line 56
Remove: confirmation prompt → result line.
- Very specific: line 60
Do NOT run install scripts from cloned repos (no postinstall, no install.sh).
- Very specific: line 61
Do NOT try to auto-convert OpenClaw-flavored skills.
- Distinctive: line 62
Do NOT install without showing the install card — the user needs to see what they're getting.
“Common” is measured: kept by at least 6 in 10 of the 32 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
- Validate the source (GitHub shorthand, full URL, or local path — the tool parses all three)
- Call
skill_install({ source })— the tool clones, detects format, checks requirements - Print the returned card verbatim
- If
format: openclawwas detected (rejected), DO NOT retry withforce. Suggest/agent:import-skilland stop. - If the skill installed with warnings, remind the user what needs to be set up (missing env var, binary, etc.)
List flow
- Call
skill_list() - Print the card. On messaging channels, compress to one line per skill.
Remove flow
- Call
skill_remove({ name })first — this is a dry run; it reports what WOULD be removed - Ask the user: "Remove
<name>from<dir>? [y/N]" — short and clear - If they confirm, call
skill_remove({ name, confirm: true }) - If they say no, just acknowledge and stop
If the user passed --force, skip step 2 and call directly with confirm: true.
Response style
- Terse. No preamble.
- Install: show the install card (already formatted) then one line of what to do next if warnings.
- List: the card as-is on CLI/WebChat; one line per skill on WhatsApp/Telegram.
- Remove: confirmation prompt → result line.
Never
- Do NOT run install scripts from cloned repos (no
postinstall, noinstall.sh). The tool does not run them and neither do you. - Do NOT try to auto-convert OpenClaw-flavored skills. If the tool rejects one as OpenClaw, direct the user to
/agent:import-skill. - Do NOT install without showing the install card — the user needs to see what they're getting.
References
docs/skill-manager.md— full docslib/skill-manager.ts— implementationdocs/INDEX.md— master feature list
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.