메뉴
Use when a human or lead agent needs one plain handoff for starting an Agent Relay workspace, choosing the right Relay skill, and telling spawned agents how to communicate.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/AgentWorkforce/agentrelay.com --skill agent-relay-team-onboarding명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
| name | agent-relay-team-onboarding |
| description | Use when a human or lead agent needs one plain handoff for starting an Agent Relay workspace, choosing the right Relay skill, and telling spawned agents how to communicate. |
Use this skill when someone asks how to get agents onto Agent Relay, how a lead should start a workspace, or which Relay skill to give to a worker.
The default handoff URL is:
https://agentrelay.com/skill
Give that URL to a human driver, a lead agent, or a newly spawned agent when you want them to orient themselves without a long custom prompt.
On Agent Relay 11.3.0 and earlier, agent-relay node up and
agent-relay node status print the active workspace key. Agent Relay
11.3.1 masks it in these two commands; it is not a guarantee about
credential output from every command in the installed dependency tree. If
you are on 11.3.0 or earlier, upgrade to 11.3.1 or later, or ask a human
driver to run those commands from a trusted, non-transcribed terminal.
The commands remain the correct way to start and inspect a node. The gate is about the vulnerable release's output, not a replacement workflow. The human-only quick start below is retained so an operator has the exact commands; do not copy its first two command lines into an agent prompt while 11.3.0 or earlier is installed.
On 11.3.1 or later this gate does not apply. The orchestrator starts and
inspects the broker itself, exactly as the linked
orchestrating-agent-relay
skill describes — that skill assumes a patched install and is written for
autonomous self-bootstrap with no human in the loop. Check your installed
version before deciding which path applies:
agent-relay --version
Never build an observer URL from a workspace key, on any version — it is an administrative credential and a URL query string is not a place for one. From Agent Relay 11.8.1, run (or call the MCP tool) to mint a scoped, read-only, expiring token and print the link built from it. See .
agent-relay observerget_observer_urlUse orchestrating-agent-relay when the agent is responsible for starting Relay and managing other agents from the outside.
Source:
https://github.com/AgentWorkforce/skills/blob/main/skills/orchestrating-agent-relay/SKILL.md
Use this role when the agent should:
agent-relay node up on Agent Relay 11.3.1 or later; on 11.3.0 or earlier, coordinate startup with a human driver insteadImportant distinction: lifecycle control — starting the broker, spawning,
listing, tailing, attaching, releasing — goes through the agent-relay node ...
CLI. Messaging goes through the relay MCP (agent-relay mcp) after the session
registers itself once with the register_agent tool (messaging tools error
with "Not registered" until it does); a plain shell sends with a registered
agent token instead, while channel reads need no token.
Use using-agent-relay when the agent is already on the relay as a registered participant.
Source:
https://github.com/AgentWorkforce/skills/blob/main/skills/using-agent-relay/SKILL.md
Use this role when the agent should:
Registered participants should use the current flat Agent Relay MCP tools, such
as send_dm, post_message, reply_to_thread, check_inbox, list_agents,
and join_channel.
Start Relay from the project root:
agent-relay node up --background --verbose
agent-relay node status --wait-for 10
Spawn a lead or worker:
agent-relay node agent spawn claude --name Lead --task "Use https://agentrelay.com/skill. Start the workspace, coordinate workers, and report progress."
Watch output from the lead:
agent-relay node tail --agent Lead
Send follow-up instructions through an interactive attach:
agent-relay node agent attach Lead --mode drive
List and inspect workers:
agent-relay node agent list
agent-relay node tail --agent Lead
Use https://agentrelay.com/skill as your Agent Relay onboarding reference.
You are the orchestrator. Use the orchestrating-agent-relay role:
- start or verify the relay broker yourself on Agent Relay 11.3.1 or later; have a human driver do it when 11.3.0 or earlier is installed
- spawn the workers needed for the task
- tell each worker to use the using-agent-relay role
- read worker output with agent-relay node tail --agent <name>
- monitor liveness with agent-relay node agent list
- send follow-up instructions with agent-relay node agent attach <name> --mode drive
- keep workers alive through review/fix loops
- release workers only after final acceptance
Workers should ACK when they receive work, report DONE when complete, and stay alive for review findings until you release them.
Use https://agentrelay.com/skill as your Agent Relay onboarding reference.
You are a registered Agent Relay participant. Use the using-agent-relay role:
- ACK the task immediately over Relay
- use flat Agent Relay MCP tools for DMs, channel posts, replies, inbox checks, and agent lists
- post concise progress updates when useful
- report DONE with evidence when the task is complete
- do not remove or release yourself; stay available for review findings
If a tool says:
Not registered. Call agent.register first.
You are probably acting as the outside orchestrator. Use agent-relay CLI commands instead of participant MCP tools, or register yourself before using participant-only MCP tools.
https://agentrelay.com/skillhttps://agentrelay.com/skill.mdhttps://github.com/AgentWorkforce/skills/blob/main/skills/orchestrating-agent-relay/SKILL.mdhttps://github.com/AgentWorkforce/skills/blob/main/skills/using-agent-relay/SKILL.md