// Use when the assistant has a workspace VFS (via @agent-assistant/harness workspace_* tools) backed by RelayFile. Covers path conventions per provider and the cite-your-source discipline. Provider-specific rows are populated at runtime from /_conventions/*.json written by cataloging agents; hand-written rows below are the fallback.
| name | using-relayfile-vfs |
| description | Use when the assistant has a workspace VFS (via @agent-assistant/harness workspace_* tools) backed by RelayFile. Covers path conventions per provider and the cite-your-source discipline. Provider-specific rows are populated at runtime from /_conventions/*.json written by cataloging agents; hand-written rows below are the fallback. |
The assistant has workspace_list, workspace_read, workspace_read_json, and
workspace_search tools available, backed by a RelayFile VFS that's been synced
by cataloging agents. Prefer these generic tools to any provider-specific
API when the answer is a lookup from synced state.
sourcePath returned by a tool. No path, no claim.workspace_list or
workspace_read_json returns nothing for path X, don't substitute
prior knowledge — say X returned no data and stop./github/...)| Shape | Example | Contents |
|---|---|---|
/github/repos/{owner}/{repo}/metadata.json | repo | repo metadata |
/github/repos/{owner}/{repo}/pulls/{n}/metadata.json | PR | PR metadata incl. state: open|closed |
/github/repos/{owner}/{repo}/issues/{n}/metadata.json | issue | issue metadata |
/github/repos/{owner}/{repo}/commits/{sha}/metadata.json | commit | commit metadata |
Worked example — list open PRs in {owner}/{repo}:
workspace_list('/github/repos/{owner}/{repo}/pulls', depth=2)metadata.json path, workspace_read_json(path)json.state === 'open'json.updated_at descendingCite each metadata.json path in the reply.
Provider conventions published to /_conventions/<provider>.json by their
cataloging agents. Assistant runtimes should list /_conventions at turn
start and fold those rows into this skill. Stubs:
slack: TBD (populated by cataloging-agent-slack)linear: TBD (populated by cataloging-agent-linear)notion: TBD (populated by cataloging-agent-notion)teams: TBD (populated by cataloging-agent-teams)gitlab: TBD (populated by cataloging-agent-gitlab)Use when coordinating multiple AI agents with Agent Relay's workflow engine and need to pick the right orchestration pattern - covers the 10 core patterns (fan-out, pipeline, hub-spoke, consensus, mesh, handoff, cascade, dag, debate, hierarchical) plus 14 specialized ones, with decision framework and accurate SDK/YAML examples.
Use when building multi-agent workflows with the relay broker-sdk - covers conversation-shape vs pipeline-shape coordination, the WorkflowBuilder API, DAG step dependencies, agent definitions, step output chaining via {{steps.X.output}}, verification gates, evidence-based completion, owner decisions, dedicated channels, dynamic channel management (subscribe/unsubscribe/mute/unmute), swarm patterns, chat-native coordination recipes (Q/A, broadcast-ack, peer review, standup, hand-off), error handling, event listeners, step sizing rules, authoring best practices, and the lead+workers team pattern for complex steps
Use when coordinating multiple AI agents with Agent Relay's workflow engine and need to pick the right orchestration pattern - covers the 10 core patterns (fan-out, pipeline, hub-spoke, consensus, mesh, handoff, cascade, dag, debate, hierarchical) plus 14 specialized ones, with decision framework and accurate SDK/YAML examples.
Use when building multi-agent workflows with the relay broker-sdk - covers conversation-shape vs pipeline-shape coordination, the WorkflowBuilder API, DAG step dependencies, agent definitions, step output chaining via {{steps.X.output}}, verification gates, evidence-based completion, owner decisions, dedicated channels, dynamic channel management (subscribe/unsubscribe/mute/unmute), swarm patterns, chat-native coordination recipes (Q/A, broadcast-ack, peer review, standup, hand-off), error handling, event listeners, step sizing rules, authoring best practices, and the lead+workers team pattern for complex steps
Use when an agent needs to self-bootstrap agent-relay and autonomously manage a team of workers - covers infrastructure startup, agent spawning, lifecycle monitoring, and team coordination without human intervention
Use when an agent needs to self-bootstrap agent-relay and autonomously manage a team of workers - covers infrastructure startup, agent spawning, lifecycle monitoring, and team coordination without human intervention