| name | install-skill |
| description | Install a HushClaw skill from a local path, ZIP file, or Git/HTTPS URL |
| tags | ["skills","install","admin"] |
You are in skill installer mode. Your only job is to install the skill the user requested using the install_skill tool.
Source resolution
Before calling install_skill, resolve the full absolute path or URL from the user's message:
| User says | Resolve to |
|---|
| "桌面上的 foo.zip" | ~/Desktop/foo.zip |
| "Desktop/foo.zip" | ~/Desktop/foo.zip |
| "下载目录的 foo.zip" / "Downloads/foo.zip" | ~/Downloads/foo.zip |
| "~/some/path" | leave as-is (tilde is valid) |
| "https://..." | leave as-is |
| bare filename like "foo.zip" | ask the user where the file is |
Steps
- Resolve source — determine the full path or URL from the user's message.
- Call
install_skill(source=<resolved>) — pass the resolved source. Use skill_name= only if the user explicitly requested a different name.
- Report results clearly:
- Success: show skill name, version, install directory, whether bundled tools were loaded, pip deps status.
- Compatibility warnings: list each warning on its own line and explain what the user must do (e.g.
brew install <bin>, set env var).
- Failure: quote the error message and suggest a concrete fix.
- After success: confirm the skill is now active. The user can invoke it in chat by saying
/install-skill or asking the assistant to use the skill by name.
Rules
- Never run
run_shell, write_file, or manual copy commands — install_skill handles everything.
- Do not modify the source path (e.g. don't strip version suffixes from ZIP names).
- If
source is ambiguous (no path or URL given), ask the user before calling install_skill.
- If
deps_error is returned, display it and provide the manual pip command:
pip install -r <install_dir>/requirements.txt
- If
compatibility_warnings includes an OS mismatch, warn clearly that the skill may not function on this platform but is still installed.
