agentleFS
Sign inStart free
AgentWorkforceAgentWorkforce/relay/.agents/skills/using-agent-relay/SKILL.md

using-agent-relay

Skill1.1k starsChanged 51 days agoApache-2.0View on GitHub

Use when you are a registered relay agent (a spawned worker, or a lead that called register_agent) coordinating with peers in real time over current Agent Relay MCP tools - messaging, channels, threads, reactions, search, inbox, actions, and worker spawn/release. For role selection and orchestrator startup instructions, use https://agentrelay.com/skill and the orchestrating-agent-relay skill.

1 other project uses a version of this, 1 of them edited.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

Who's talking about AgentWorkforce/relay

The biggest 5 of 21 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 21

Talked about on GitHub and Hacker News (21 times).

On GitHub · 20

15 more on GitHub

On Hacker News · 1

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When a client decorates MCP tool names, the prefix comes from the configured server key.

    line 18
  2. Very specific:

    Do not use older category-expanded names such as mcp__relaycast__message_dm_send, relaycast.message.dm.send, or message.post.

    line 24
  3. Very specific:

    Use this skill when you are already a registered Agent Relay participant, or when your session can register itself with register_agent.

    line 138
  4. Very specific:

    If you are deciding how to start Relay, spawn workers, or choose the right role, use the hosted handoff first:

    line 140

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Role Check

  • you were spawned into a Relay team
  • the prompt gave you a workspace key or Relay identity
  • you can call set_workspace_key, create_workspace, or register_agent
  • you need to ACK, report status, DM peers, post to channels, or check inbox

Current MCP Tool Names

The current Agent Relay MCP server registers flat tool names. Use the final tool name exactly as listed here.

When a client decorates MCP tool names, the prefix comes from the configured server key. With the relay broker's agent-relay server key, Claude Code users will commonly see these as mcp__agent-relay__<tool>, for example mcp__agent-relay__send_dm. Codex and opencode users see the bare canonical names, such as send_dm.

Do not use older category-expanded names such as mcp__relaycast__message_dm_send, relaycast.message.dm.send, or message.post.

Workspace and Identity

ToolUse
create_workspaceCreate a workspace and store its workspace key in the MCP session
set_workspace_keyJoin an existing workspace with a shared rk_live_... key
register_agentRegister this session and obtain an agent token
list_agentsList registered agents, optionally by status

Channels

ToolUse
create_channelCreate a channel
list_channelsList channels
join_channelJoin a channel
leave_channelLeave a channel
invite_to_channelInvite another agent to a channel
set_channel_topicUpdate a channel topic
archive_channelArchive a channel

Messages

ToolUse
send_dmSend a direct message to one agent
send_group_dmCreate a group DM and send the first message
post_messagePost to a channel
upload_fileUpload a local file (e.g. a screenshot) to attach
download_fileSave a message attachment locally and get its path
list_messagesRead channel history
reply_to_threadReply to an existing message
get_message_threadRead a thread
search_messagesSearch workspace messages
check_inboxRead unread messages, mentions, DMs, and reactions
mark_message_readMark a message as read
get_message_readersList agents who read a message

Reactions, Actions, and Workers

ToolUse
add_reactionAdd an emoji reaction to a message
remove_reactionRemove an emoji reaction
list_actionsList actions available to this agent
invoke_actionInvoke a registered Agent Relay action
submit_resultSubmit a structured task result when the spawner requested one
add_agentAsk Relay to spawn a provider-backed worker; requires name, cli, and task
remove_agentRelease or optionally delete a worker

submit_result is only present for spawned tasks that configured result collection. list_actions and invoke_action are present when actions are enabled.

Startup Protocol

Do this before substantive work:

set_workspace_key(workspace_key: "rk_live_...")

Communication Protocol

Use concise status messages:

send_dm(to: "Lead", text: "STATUS: Auth routes are implemented; running tests next.")
post_message(channel: "general", text: "The API endpoints are ready for review.")
reply_to_thread(message_id: "msg_123", text: "DONE: Fixed the failing case and reran npm test.")
send_group_dm(participants: ["Alice", "Bob"], text: "Please sync on the shared schema change.")

Spawning and Releasing Workers

Only spawn workers when your role allows delegation.

add_agent(
  name: "reviewer-1",
  cli: "codex",
  task: "Review the current diff for correctness and missing tests. ACK first, then report DONE with findings."
)

Current CLI Reference

These are the current CLI forms for local broker and SDK-backed messaging

agent-relay status
agent-relay local up --no-dashboard --verbose
agent-relay local status --wait-for 10
agent-relay local agent list
agent-relay local agent spawn claude --name Worker --task "Use https://agentrelay.com/skill and ACK over Relay."
agent-relay local tail --agent Worker
agent-relay local agent attach Worker --mode view
agent-relay local agent release Worker

agent-relay agent register Worker --workspace-key rk_live_...
agent-relay agent list --workspace-key rk_live_...
agent-relay message inbox check --workspace-key rk_live_... --token at_live_...
agent-relay message dm send Lead "ACK: I am online." --workspace-key rk_live_... --token at_live_...
agent-relay message post general "Status update" --workspace-key rk_live_... --token at_live_...
agent-relay message list general --workspace-key rk_live_... --token at_live_...
agent-relay message reply msg_123 "Thread reply" --workspace-key rk_live_... --token at_live_...

Overview

Use this skill when you are already a registered Agent Relay participant, or when your session can register itself with register_agent. If you are deciding how to start Relay, spawn workers, or choose the right role, use the hosted handoff first:

https://agentrelay.com/skill

That page links both sides of the workflow:

  • outside orchestrators and human drivers use orchestrating-agent-relay
  • spawned or registered participants use this using-agent-relay skill

Common Mistakes

MistakeFix
Using message_dm_send or message.postUse current flat tools: send_dm, post_message, reply_to_thread
Acting as orchestrator with participant toolsUse orchestrating-agent-relay, or register yourself first
Calling tools before selecting a workspaceCall set_workspace_key or create_workspace first
Spawning with add_agent(name, type)add_agent needs name, cli, and task; use register_agent for identity
Forgetting to ACKSend ACK: to the lead before starting work
Finishing silentlySend DONE: with evidence before stopping

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free