// Discover and install agent skills from the open ecosystem. Use when you encounter an unfamiliar domain, framework, or workflow that you lack specialized knowledge about, or when your coordinator suggests searching for skills before starting a task.
Use before sending @mentions, deciding whether to reply, TASK_COMPLETED, BLOCKED, QUESTION, direct answers, loop prevention, or suppressing low-information acknowledgements.
Use before direct filesync calls, reading non-task shared files, pushing mid-task progress, or troubleshooting missing shared files. Do not use for normal task acceptance or submission; taskflow ack_task and submit_task handle lifecycle sync internally.
Use only when you need to look up team topology, worker phase, runtime state, or identity that is NOT available from the current message context. Do not use for standard task flows — the coordinator is the message sender, and the task room is in meta.json.room_id.
Use before any Worker taskflow call or assigned-task workflow, including reading task state, acknowledging a task, executing a task, tracking progress, handling blockers/questions, submitting structured results, or reporting completion. Always use this skill when the message mentions assigned task, task ID, shared/tasks, spec.md, meta.json, result.md, deliverables, BLOCKED, REVISION_NEEDED, SUCCESS, submit_task, or ack_task.
Use when admin asks to start a multi-worker project, when a Worker @mentions you with task completion in a project room, when project plan changes are needed, or when a blocked task needs resolution.
Use when admin gives a task to delegate to a Worker, when a Worker reports task completion, when managing recurring scheduled tasks, or when you need to check worker availability.
| name | find-skills |
| description | Discover and install agent skills from the open ecosystem. Use when you encounter an unfamiliar domain, framework, or workflow that you lack specialized knowledge about, or when your coordinator suggests searching for skills before starting a task. |
This skill helps you discover and install skills from the open agent skills ecosystem.
Worker is completely isolated and cannot access any admin's personal sensitive data. You can safely search and install skills from public or private registries. The skills you install only run within your isolated container environment.
Use this skill when the user:
The Skills CLI (skills) is the package manager for the open agent skills ecosystem. Skills are modular packages that extend agent capabilities with specialized knowledge, workflows, and tools.
If skills command is not found, install it: npm install -g skills
Resolve the script from local skill paths. Do not hardcode container absolute paths in chat or task outputs:
FIND_SKILLS_SCRIPT=""
for candidate in \
"./skills/find-skills/scripts/hiclaw-find-skill.sh" \
"./active_skills/find-skills/scripts/hiclaw-find-skill.sh" \
"./find-skills/scripts/hiclaw-find-skill.sh"; do
if [ -x "$candidate" ]; then
FIND_SKILLS_SCRIPT="$candidate"
break
fi
done
test -n "$FIND_SKILLS_SCRIPT" || { echo "find-skills script not found" >&2; exit 1; }
Key commands:
"${FIND_SKILLS_SCRIPT}" find [query] - Search for relevant skills"${FIND_SKILLS_SCRIPT}" install <skill> - Install a skillskills check - Check for skill updatesskills update - Update all installed skillsBrowse skills at: https://skills.sh/
SKILLS_API_URL # Skills registry API endpoint (default: nacos://market.hiclaw.io:80/public)
Can be configured by admin to point to an enterprise-private registry.
When a user asks for help with something, identify:
Run the find command with a relevant query:
"${FIND_SKILLS_SCRIPT}" find [query]
For example:
"${FIND_SKILLS_SCRIPT}" find react performance"${FIND_SKILLS_SCRIPT}" find pr review"${FIND_SKILLS_SCRIPT}" find changelogThe command will return results like:
Install with ./skills/find-skills/scripts/hiclaw-find-skill.sh install <skill>
vercel-react-best-practices
└ React and Next.js performance guidance
Critical: Always use the exact install command shown in search results. Never guess or shorten the package name or command, because that may fail.
If the user already gave you a concrete skill name and asked to import it from the market, you can install it directly with this skill instead of doing a separate search first:
"${FIND_SKILLS_SCRIPT}" install <skill>
For example:
"${FIND_SKILLS_SCRIPT}" install remotion-best-practices"${FIND_SKILLS_SCRIPT}" install github-operationsIf the provided name looks ambiguous or you are not sure about the exact package name, search first and then copy the exact install command from the results.
When you find relevant skills, present them to the user with:
Example response:
I found a skill that might help! The "remotion-best-practices" skill provides
best practices for Remotion video creation in React.
To install it:
"${FIND_SKILLS_SCRIPT}" install remotion-best-practices
If the user wants to proceed, you can install the skill for them:
"${FIND_SKILLS_SCRIPT}" install <skill>
The default install location for skills add -g is runtime-managed. Prefer the install command printed by this skill and then use the file-sharing skill if your coordinator asks you to sync updates.
When searching, consider these common categories:
| Category | Example Queries |
|---|---|
| Web Development | react, nextjs, typescript, css, tailwind |
| Testing | testing, jest, playwright, e2e |
| DevOps | deploy, docker, kubernetes, ci-cd |
| Documentation | docs, readme, changelog, api-docs |
| Code Quality | review, lint, refactor, best-practices |
| Design | ui, ux, design-system, accessibility |
| Productivity | workflow, automation, git |
vercel-labs/agent-skills or ComposioHQ/awesome-claude-skillsIf no relevant skills exist:
skills initExample:
I searched for skills related to "xyz" but didn't find any matches.
I can still help you with this task directly! Would you like me to proceed?
If this is something you do often, you could create your own skill:
skills init my-xyz-skill
hiclaw-find-skill.sh is the resource that belongs to this skill. Resolve it into FIND_SKILLS_SCRIPT first so your command does not depend on hidden runtime paths.