メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Execute AI coding CLI tools (Claude Code / Gemini CLI / qodercli) on behalf of Workers. Use when a Worker sends a coding-request: message, asking Manager to run coding operations in their workspace.
Use when determining sender identity in any room, managing trusted contacts, configuring the admin's primary notification channel, handling first-contact from a new channel, or escalating to admin across channels.
Use when admin requests adding a human user to the system, changing human permissions, removing human access, or managing human accounts.
Use when admin asks to configure an MCP tool server (e.g., GitHub, weather API), rotate credentials, grant/revoke worker access to MCP tools, or add a custom API integration via YAML.
Expose worker HTTP services via Higress gateway. Use when admin asks to publish a worker's web app or API to make it externally accessible.
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 | agentteams-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/agentteams/agent/skills/agentteams-find-worker/scripts/agentteams-find-worker.sh \
--query "<admin requirement>" --limit 3 --json
# Install after the admin confirms
bash /opt/agentteams/agent/skills/agentteams-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/agentteams/agent/skills/agentteams-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 agt 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 agt 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/agentteams-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 |