القائمة
Use as a helper when the admin is assigning work but has not specified an existing Worker, so you need to search Nacos for a suitable Worker and ask whether to import it; also use when the admin explicitly says to import a Worker from the market or gives a direct nacos package URI.
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 before filesync calls for project directories, global-shared inputs, non-task shared files, listing shared paths, or troubleshooting missing files. Do not use for task-level sync; taskflow delegate_task and check_task handle task directory sync internally.
Sync files with centralized storage. Use when your coordinator or another Worker notifies you of file updates (config changes, task files, shared data, collaboration artifacts).
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.
Discover and call MCP Server tools via the mcporter CLI. Use when your coordinator notifies you about new MCP tools, or when you need to call external APIs. Includes workflow for generating skill documentation for new MCP servers.
Use when you are invited to a Project Room or assigned a task within a multi-worker project. Covers project plan reading, task coordination with other Workers, and git author config.
| name | hiclaw-find-worker |
| description | Use as a helper when the admin is assigning work but has not specified an existing Worker, so you need to search Nacos for a suitable Worker and ask whether to import it; also use when the admin explicitly says to import a Worker from the market or gives a direct nacos package URI. |
Use this skill as a helper around Worker discovery and import from Nacos AgentSpecs.
Use it in two cases:
nacos://... package URI.Do not use this skill for generic hand-created Worker creation. This skill only handles Nacos-backed Worker search and install, not zip packages or other import formats.
# Search by requirement
bash /opt/hiclaw/agent/skills/hiclaw-find-worker/scripts/hiclaw-find-worker.sh \
--query "<admin requirement>" --limit 3 --json
# Install after the admin confirms
bash /opt/hiclaw/agent/skills/hiclaw-find-worker/scripts/install-worker-template.sh \
--template <TEMPLATE_NAME> --worker-name <NAME>
# Or import a direct package URI after the admin confirms
bash /opt/hiclaw/agent/skills/hiclaw-find-worker/scripts/install-worker-template.sh \
--package-uri <PACKAGE_URI> --worker-name <NAME>
Full workflow: read
references/import-worker-template.md
create-worker.sh for Nacos imports — imports use hiclaw apply worker --package ....nacos://... directly, stay in this skill — treat it as an explicit package import, confirm the Worker name, then install without searching.worker-management only when search proves there is no usable Nacos candidate. Once the admin confirms a specific Worker/package URI, stay in this skill until install succeeds or fails.install-worker-template.sh or hiclaw apply worker fails, stop there and tell the admin the import failed. Include the key error from the command output. Do not hand-create a Worker after a confirmed import fails unless the admin explicitly asks for that fallback.package_uri is the handoff contract — use the package_uri from the search output as the package to install.| Admin wants to... | Read | Key script |
|---|---|---|
| Search Nacos Workers by requirement or exact name | references/import-worker-template.md | scripts/hiclaw-find-worker.sh |
Import a direct nacos://... package URI | references/import-worker-template.md | scripts/install-worker-template.sh |
| Install a confirmed Worker from Nacos | references/import-worker-template.md | scripts/install-worker-template.sh |