本文へ移動
cccskills
無料GitHub で公開

organization

Use before any Leader action that depends on current team topology, worker list, worker phase, runtime, room ID, Matrix ID, Team Admin, human identity, or lifecycle state. Always use this skill when assigning tasks, sending cross-room messages, recovering projects, handling heartbeat, waking/sleeping workers, or when any worker/room/identity value might be stale.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md2.0 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Organization

Use this skill for current AgentTeams topology and runtime state.

Source Of Truth

Use agt CLI. Do not infer organization state from memory, old chat history, SOUL.md, or AGENTS.md.

Resolve the Team CR name before any team-scoped CLI query. The team name in SOUL.md may be the runtime/storage teamName, not the Kubernetes Team CR name accepted by agentteams --team.

TEAM_CR="$(agt get workers "${AGENTTEAMS_WORKER_CR_NAME:-$AGENTTEAMS_WORKER_NAME}" -o json | jq -r '.team')"
agt get teams "$TEAM_CR" -o json
agt get workers --team "$TEAM_CR" -o json
agt worker status --team "$TEAM_CR"

Use the Team CR name for CLI filters and lifecycle commands. Use the returned teamName only as runtime/storage/display context. If agt get workers --team <name> returns no workers, re-check that you used the Team CR name from your own Worker metadata, not the runtime teamName.

What To Read From CLI

  • Team Room and Leader Room IDs
  • Team Admin / human identity
  • Worker names
  • Worker full Matrix IDs
  • Worker room IDs
  • Worker phase and runtime state

Use the Team Room ID for normal task assignment notifications. Worker room IDs are for exceptional direct follow-up, not routine assignment.

Lifecycle

Use lifecycle commands only after checking active project and task files.

agt worker ensure-ready --name <worker-name> --team "$TEAM_CR"
agt worker wake --name <worker-name> --team "$TEAM_CR"
agt worker sleep --name <worker-name> --team "$TEAM_CR"

If CLI output is missing a required room ID or Matrix ID, stop and report a metadata problem. Do not guess.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

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.

日本語の概要は準備中です。原文の説明を表示しています。

agentscope-ai/AgentTeams5,7402026年10月12日 更新

Analyze current OpenClaw setup and generate a migration package (ZIP) for importing into AgentTeams as a managed Worker

日本語の概要は準備中です。原文の説明を表示しています。

agentscope-ai/AgentTeams5,7402026年10月12日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

agentscope-ai/AgentTeams5,7402026年10月12日 更新

将编码工作委托给 Manager 持有的 AI CLI 工具(Claude Code / Gemini CLI / qodercli)执行

日本語の概要は準備中です。原文の説明を表示しています。

agentscope-ai/AgentTeams5,7402026年10月12日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

agentscope-ai/AgentTeams5,7402026年10月12日 更新

Use before sending or suppressing any Leader message to Workers, Manager, or Team Admin. Always use this skill for cross-room Matrix messages, @mention decisions, task assignment notifications, structured status reports, completion reports, blocker/revision messages, questions, requester updates, or when deciding whether a same-room reply is enough.

日本語の概要は準備中です。原文の説明を表示しています。

agentscope-ai/AgentTeams5,7402026年10月12日 更新

agentscope-ai のスキルをすべて見る

このスキルの問題を報告する