container/skills/install-skill/SKILL.md
When a user requests to install a new skill, this skill guides you to identify the package name from various input formats and use the install_skill MCP tool. Supports skills.sh URLs, GitHub URLs, owner/repo, and owner/repo@skill formats.
npx skillsauth add riba2534/happyclaw install-skillInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
When a user asks to install a skill (e.g., sends a link, mentions a skill name, or says "install xxx skill"), follow this process:
Parse the user's input to extract the owner/repo or owner/repo@skill format:
| Input Format | Example | Extract As |
|---|---|---|
| skills.sh URL | https://skills.sh/s/owner/repo | owner/repo |
| skills.sh skill URL | https://skills.sh/s/owner/repo/skill-name | owner/repo@skill-name |
| GitHub URL | https://github.com/owner/repo | owner/repo |
| GitHub tree URL | https://github.com/owner/repo/tree/main/skills/name | owner/repo@name |
| Direct package | owner/repo | owner/repo |
| Package with skill | owner/repo@skill | owner/repo@skill |
Call the install_skill MCP tool with the extracted package name:
install_skill({ "package": "owner/repo" })
Or with a specific skill from the repo:
install_skill({ "package": "owner/repo@skill-name" })
On success:
installed array from the response)On failure:
owner/repo or owner/repo@skillIf the user wants to uninstall a skill, use the uninstall_skill MCP tool:
uninstall_skill({ "skill_id": "skill-name" })
The skill_id is the directory name of the installed skill.
testing
测试完成后的扫尾清理流程。在向某个工作区发送测试指令(如长篇文章生成、耗时任务)后,用此流程彻底清除测试痕迹,防止测试消息残留在会话上下文中持续消耗 token 额度。
development
Browse the web for any task — research topics, read articles, interact with web apps, fill forms, take screenshots, extract data, and test web pages. Use whenever a browser would be useful, not just when the user explicitly asks.
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------