prpm.json

{
  "name": "agent-workforce-skills",
  "version": "1.8.0",
  "description": "Skills for multi-agent coordination - swarm patterns, workflow building, relay usage, and orchestrating agent-relay",
  "author": "khaliqgant",
  "organization": "agent-relay",
  "license": "MIT",
  "repository": "https://github.com/AgentWorkforce/skills",
  "homepage": "https://agentrelay.com",
  "packages": [
    {
      "name": "migrating-persona-to-relayflow",
      "version": "1.1.0",
      "description": "Use when migrating an existing defineAgent persona (in AgentWorkforce/agents or AgentWorkforce/internal-agents) to run its LLM-heavy work through a Relayflow v1 workflow via ctx.workflow.run(). Covers scope decisions, the 4-step durable-workflow shape, colocation with the persona, ctx.workflow.run() invocation, red-first + resume tests, useSubscription semantics for realtime triggers, and the agentworkforce >= 4.1.44 CI-deploy bump. Reference migration: hn-monitor PR #126.",
      "format": "claude",
      "subtype": "skill",
      "tags": [
        "relayflow",
        "migration",
        "persona",
        "defineAgent",
        "workflow",
        "durable-execution",
        "agents-repo"
      ],
      "files": [
        "skills/migrating-persona-to-relayflow/SKILL.md"
      ]
    },
    {
      "name": "choosing-swarm-patterns",
      "version": "1.1.5",
      "description": "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.",
      "format": "claude",
      "subtype": "skill",
      "tags": [
        "multi-agent",
        "orchestration",
        "swarm-patterns",
        "workflow",
        "coordination",
        "agent-management"
      ],
      "files": [
        "skills/choosing-swarm-patterns/SKILL.md"
      ]
    },
    {
      "name": "writing-agent-relay-workflows",
      "version": "2.0.0",
      "description": "DEPRECATED - the superseded v1 @relayflows/core WorkflowBuilder engine (failOnError, captureOutput, {{steps.X.output}}, .onError()). All new work uses writing-relayflows (v2: @relayflows/surface / @relayflows/sdk, CLI `flows`). Keep this only to read or maintain an existing v1 workflow: conversation vs pipeline coordination, DAG steps, idle detection, human assistance, waitFor gates, review-depth review/fix loops, channels, and parallel waves.",
      "format": "claude",
      "subtype": "skill",
      "languages": [
        "typescript",
        "python",
        "yaml"
      ],
      "tags": [
        "workflow",
        "multi-agent",
        "dag",
        "orchestration",
        "swarm-patterns",
        "typescript",
        "python",
        "yaml"
      ],
      "files": [
        "skills/writing-agent-relay-workflows/SKILL.md",
        "skills/writing-agent-relay-workflows/examples/README.md",
        "skills/writing-agent-relay-workflows/examples/assert-repo.ts",
        "skills/writing-agent-relay-workflows/examples/ship-issue.local.ts",
        "skills/writing-agent-relay-workflows/examples/github-steps.local.ts",
        "skills/writing-agent-relay-workflows/examples/integration-steps-need-an-executor.ts"
      ]
    },
    {
      "name": "setting-up-relayfile",
      "version": "1.1.1",
      "description": "Use when an agent or human needs to set up relayfile end-to-end so agents can read and write provider files through a local mount. Covers `relayfile setup`, dynamic integration discovery with `relayfile integration available/search`, Nango and Composio backend selection, Atlassian site selection and metadata, cloud login, OAuth/connect flows, mount verification, `RELAYFILE_LOCAL_DIR` handoff, writeback status and retry commands, and key May 2026 cloud-mount gotchas.",
      "format": "claude",
      "subtype": "skill",
      "tags": [
        "relayfile",
        "mount",
        "integrations",
        "notion",
        "agent-setup",
        "writeback"
      ],
      "files": [
        "skills/setting-up-relayfile/SKILL.md"
      ]
    },
    {
      "name": "writing-relayflows",
      "version": "1.4.0",
      "description": "Use when authoring a Relayflows flow (@relayflows/surface / @relayflows/sdk, the v2 journal-based engine, CLI `flows`) in TypeScript or YAML/JSON. Covers the run/llm/agent ladder, human/dispatch/done, verification gates, cli/model resolution, flows.json, and flows check/run/resume refusal shapes. Not for the older @relayflows/core WorkflowBuilder (chained .pattern('dag')/.agent()/.step() calls) — see writing-agent-relay-workflows / migrating-persona-to-relayflow instead.",
      "format": "claude",
      "subtype": "skill",
      "languages": [
        "typescript",
        "yaml"
      ],
      "tags": [
        "relayflows",
        "flows",
        "journal",
        "workflow",
        "agent",
        "typescript",
        "yaml"
      ],
      "files": [
        "skills/writing-relayflows/SKILL.md"
      ]
    },
    {
      "name": "using-agent-relay",
      "version": "1.4.0",
      "description": "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.",
      "format": "claude",
      "subtype": "skill",
      "tags": [
        "multi-agent",
        "agent-communication",
        "inter-agent",
        "coordination",
        "real-time",
        "messaging"
      ],
      "files": [
        "skills/using-agent-relay/SKILL.md"
      ]
    },
    {
      "name": "orchestrating-agent-relay",
      "version": "2.4.0",
      "description": "The canonical way to run agent-relay - self-bootstrap the local broker and autonomously spawn, monitor, and coordinate a team of worker agents without human intervention. Covers infrastructure startup, agent spawning, lifecycle monitoring, message-based reading via the relay MCP, GitHub PR-owner integration subscriptions, and team coordination.",
      "format": "claude",
      "subtype": "skill",
      "tags": [
        "multi-agent",
        "orchestration",
        "headless",
        "autonomous",
        "self-bootstrap",
        "agent-management"
      ],
      "files": [
        "skills/orchestrating-agent-relay/SKILL.md"
      ]
    },
    {
      "name": "relay-80-100-workflow",
      "version": "2.1.0",
      "description": "Use when writing a Relayflows v2 flow (@relayflows/surface / @relayflows/sdk, CLI `flows`) that must fully validate a feature end-to-end before it is sealed or merged - the 80-to-100 gap. Covers the evidence-recorder pattern that replaces v1's failOnError/captureOutput, repairable gates on the critical path, edit and hazard gates, gate cross-checking, fresh-eyes review rounds, and what a wall of green gates still misses.",
      "format": "claude",
      "subtype": "skill",
      "tags": [
        "relayflows",
        "workflow",
        "testing",
        "e2e-validation",
        "pglite",
        "quality-assurance",
        "multi-agent",
        "best-practices"
      ],
      "files": [
        "skills/relay-80-100-workflow/SKILL.md"
      ]
    },
    {
      "name": "activity-summary",
      "version": "1.0.0",
      "description": "Use when an agent is asked \"what did I (or my team) work on yesterday / this week / today\" across provider data in a relayfile mount (Linear, GitHub, Notion, Slack, Confluence, Jira, etc.). Tells the agent to consult the pre-computed `digests/yesterday.md` (and sibling digest files) at the workspace root BEFORE doing manual exploration with `ls`/`grep`/`find`. The digest is deterministic, exhaustive over the window, and costs one file read instead of dozens of provider queries.",
      "format": "claude",
      "subtype": "skill",
      "tags": [
        "relayfile",
        "activity-summary",
        "digest",
        "agent-context",
        "cost-optimization"
      ],
      "files": [
        "skills/activity-summary/SKILL.md"
      ]
    },
    {
      "name": "daily-digest",
      "version": "1.0.0",
      "description": "Use when authoring or extending the digest set in a relayfile workspace - covers the contract for files under `<mount>/digests/` (`yesterday.md`, `today.md`, `this-week.md`, date-stamped daily files), per-provider section format, link conventions back into the canonical mount tree, when digests are regenerated, and how adapter authors expose new provider data to the digest pipeline.",
      "format": "claude",
      "subtype": "skill",
      "tags": [
        "relayfile",
        "digest",
        "adapter",
        "authoring",
        "provider-integration"
      ],
      "files": [
        "skills/daily-digest/SKILL.md"
      ]
    },
    {
      "name": "writeback-as-files",
      "version": "1.0.0",
      "description": "Use when an agent needs to write back to a provider through a relayfile mount (Linear comments, GitHub issues, Slack messages, Notion pages, etc.). Covers the file-creation writeback contract (drop JSON at the canonical path → provider mutation), discovering paths and schemas via .schema.json siblings, idempotency keys, writeback status with relayfile writeback list and relayfile status, and recovering from dead-lettered writes under .relay/dead-letter/.",
      "format": "claude",
      "subtype": "skill",
      "tags": [
        "relayfile",
        "writeback",
        "provider-mutation",
        "agent-action",
        "dead-letter"
      ],
      "files": [
        "skills/writeback-as-files/SKILL.md"
      ]
    },
    {
      "name": "workspace-layout",
      "version": "1.0.1",
      "description": "Use when an agent is exploring a relayfile mount for the first time or trying to locate a specific resource (Notion page, Linear issue, Slack channel, GitHub PR). Tells the agent to start with `<mount>/LAYOUT.md` and `<provider>/LAYOUT.md` rather than guessing paths from memory, and to use the `by-title/`, `by-id/`, `by-name/`, `by-edited/<date>/`, `by-state/` alias subtrees instead of recursively grepping. Filename convention is `<identifier>__<uuid>`.",
      "format": "claude",
      "subtype": "skill",
      "tags": [
        "relayfile",
        "workspace",
        "navigation",
        "indexes",
        "agent-context"
      ],
      "files": [
        "skills/workspace-layout/SKILL.md"
      ]
    },
    {
      "name": "connecting-agents-across-machines",
      "version": "1.0.0",
      "description": "Use when agents running on two or more machines (laptops, desktops, Mac minis, servers) need to talk to each other or when you want to spawn an agent onto another machine with Agent Relay. Covers putting every machine on one shared workspace, starting a node per machine, messaging across machines, targeted spawns, and verifying the link agent-to-agent. No Relay Cloud sandbox required. Verified on agent-relay 12.4.1.",
      "format": "claude",
      "subtype": "skill",
      "tags": [
        "multi-machine",
        "fleet",
        "cross-machine",
        "workspace",
        "agent-relay",
        "getting-started"
      ],
      "files": [
        "skills/connecting-agents-across-machines/SKILL.md"
      ]
    },
    {
      "name": "multi-host-live-mount",
      "version": "1.0.0",
      "description": "Use when one Relayfile workspace must be mounted on several machines and an agent placed on a remote host inside the live tree without cloning. Covers joining an existing workspace with write opt-in, per-node mount scopes and credentials, fleet enrollment and placement, and byte-level proof that remote mirrors are current. Treats daemon liveness, lag/status lines, and fleet-node presence as non-proof.",
      "format": "claude",
      "subtype": "skill",
      "tags": [
        "relayfile",
        "multi-host",
        "fleet",
        "mount",
        "staleness",
        "placement",
        "agent-context"
      ],
      "files": [
        "skills/multi-host-live-mount/SKILL.md",
        "skills/multi-host-live-mount/scripts/assert-mirror-current.sh",
        "skills/multi-host-live-mount/scripts/assert-known-true-now.sh",
        "skills/multi-host-live-mount/scripts/assert-cross-host-write-visible.sh"
      ]
    },
    {
      "name": "adding-swarm-patterns",
      "version": "1.0.0",
      "description": "Use when adding new multi-agent coordination patterns to agent-relay - provides checklist for types, schema, templates, and docs updates",
      "format": "claude",
      "subtype": "skill",
      "tags": [
        "agent-relay",
        "swarm",
        "patterns",
        "workflows",
        "multi-agent",
        "orchestration"
      ],
      "files": [
        "skills/adding-swarm-patterns/SKILL.md"
      ]
    },
    {
      "name": "review-fix-signoff-loop",
      "version": "1.0.2",
      "description": "Use when writing Agent Relay or Ricky workflows that must loop review, fix, and validation with fresh agent context until independent signoff agents both agree the work is comprehensively complete",
      "format": "claude",
      "subtype": "skill",
      "tags": [
        "workflow",
        "review-loop",
        "signoff",
        "fresh-context",
        "quality-assurance",
        "multi-agent",
        "pr-comments"
      ],
      "files": [
        "skills/review-fix-signoff-loop/SKILL.md"
      ]
    },
    {
      "name": "trigger-autocomplete-catalog",
      "version": "1.0.0",
      "description": "Use when adding webhook events to make sure integrations properly register the webhook events they carry through KNOWN_TRIGGER_CATALOG in @relayfile/adapter-core - covers checking coverage, adding supportedEvents() or mapping.yaml webhooks, validation commands, and publishing the updated catalog.",
      "format": "claude",
      "subtype": "skill",
      "tags": [
        "nango",
        "webhooks",
        "trigger-catalog",
        "relayfile",
        "integration",
        "autocomplete"
      ],
      "files": [
        "skills/trigger-autocomplete-catalog/SKILL.md"
      ]
    },
    {
      "name": "create-workflow",
      "version": "1.0.5",
      "description": "Slash command to scaffold a new agent-relay multi-agent workflow using the writing-agent-relay-workflows skill - harness-agnostic, model-agnostic prompts, picks the right swarm pattern, and emits a runnable WorkflowBuilder file with verify gates, selected review-depth review/fix loops with test hardening, and integration notes",
      "format": "claude",
      "subtype": "slash-command",
      "tags": [
        "slash-command",
        "workflow",
        "multi-agent",
        "agent-relay",
        "orchestration",
        "scaffolding"
      ],
      "files": [
        "commands/create-workflow.md"
      ]
    },
    {
      "name": "spawn",
      "version": "1.1.0",
      "description": "Slash command for relay-orchestrator that bootstraps the agent-relay broker and spawns a worker on the chosen harness (claude, codex, opencode, droid, gemini, pi) with optional --model and --task - loads the orchestrator skill so infrastructure, channels, and lifecycle just work",
      "format": "claude",
      "subtype": "slash-command",
      "tags": [
        "slash-command",
        "orchestrator",
        "agent-relay",
        "spawn",
        "headless",
        "multi-agent"
      ],
      "files": [
        "commands/spawn.md"
      ]
    },
    {
      "name": "review-loop",
      "version": "1.0.1",
      "description": "Slash command that runs a robust dual-reviewer code-review loop - Claude and Codex each review the working-tree diff independently while fanning out into their own subagents, a Codex fixer repairs every valid finding from both reviews and hardens it with tests, and the loop repeats with fresh agent context until both reviewers independently sign off on the same post-fix state",
      "format": "claude",
      "subtype": "slash-command",
      "tags": [
        "slash-command",
        "code-review",
        "review-loop",
        "agent-relay",
        "multi-agent",
        "claude-codex",
        "subagents"
      ],
      "files": [
        "commands/review-loop.md"
      ]
    },
    {
      "name": "creating-cloud-persona",
      "version": "1.0.11",
      "description": "Use when creating or updating a Workforce cloud persona (persona.json/persona.ts + agent.ts) for the current deploy/runtime shape: defineAgent(...) triggers/schedules/watch or team-dispatcher launch, flat runtime fields, integrations with scope and adapter config passthrough, memory, onEvent, provider IO via @relayfile/relay-helpers, vendored production examples, production-correctness checks, and the agent-driven login then deploy flow.",
      "format": "claude",
      "subtype": "skill",
      "languages": [
        "typescript",
        "json"
      ],
      "tags": [
        "persona",
        "cloud",
        "workforce",
        "defineAgent",
        "relay-helpers",
        "deploy"
      ],
      "files": [
        "skills/creating-cloud-persona/SKILL.md",
        "skills/creating-cloud-persona/references/agents/cloud-team-implementer/agent.ts",
        "skills/creating-cloud-persona/references/agents/cloud-team-implementer/persona.json",
        "skills/creating-cloud-persona/references/agents/cloud-team-implementer/persona.ts",
        "skills/creating-cloud-persona/references/agents/cloud-team-reviewer/agent.ts",
        "skills/creating-cloud-persona/references/agents/cloud-team-reviewer/persona.json",
        "skills/creating-cloud-persona/references/agents/cloud-team-reviewer/persona.ts",
        "skills/creating-cloud-persona/references/agents/granola/agent.ts",
        "skills/creating-cloud-persona/references/agents/granola/persona.json",
        "skills/creating-cloud-persona/references/agents/granola/persona.ts",
        "skills/creating-cloud-persona/references/agents/hn-monitor/agent.ts",
        "skills/creating-cloud-persona/references/agents/hn-monitor/persona.json",
        "skills/creating-cloud-persona/references/agents/hn-monitor/persona.ts",
        "skills/creating-cloud-persona/references/agents/linear-slack/agent.ts",
        "skills/creating-cloud-persona/references/agents/linear/agent.ts",
        "skills/creating-cloud-persona/references/agents/linear/persona.json",
        "skills/creating-cloud-persona/references/agents/linear/persona.ts",
        "skills/creating-cloud-persona/references/agents/package.json",
        "skills/creating-cloud-persona/references/agents/repo-hygiene/agent.ts",
        "skills/creating-cloud-persona/references/agents/repo-hygiene/persona.json",
        "skills/creating-cloud-persona/references/agents/repo-hygiene/persona.ts",
        "skills/creating-cloud-persona/references/agents/review/agent.ts",
        "skills/creating-cloud-persona/references/agents/review/persona.json",
        "skills/creating-cloud-persona/references/agents/review/persona.ts",
        "skills/creating-cloud-persona/references/agents/spotify-releases/agent.ts",
        "skills/creating-cloud-persona/references/agents/spotify-releases/persona.json",
        "skills/creating-cloud-persona/references/agents/spotify-releases/persona.ts",
        "skills/creating-cloud-persona/references/agents/tsconfig.json",
        "skills/creating-cloud-persona/references/agents/vendor-monitor/agent.ts",
        "skills/creating-cloud-persona/references/agents/vendor-monitor/persona.json",
        "skills/creating-cloud-persona/references/agents/vendor-monitor/persona.ts",
        "skills/creating-cloud-persona/references/relayfile-adapters/packages/relay-helpers/README.md",
        "skills/creating-cloud-persona/references/workforce-cloud-persona-notes.md",
        "skills/creating-cloud-persona/references/workforce/examples/linear-shipper/agent.ts",
        "skills/creating-cloud-persona/references/workforce/examples/linear-shipper/persona.json",
        "skills/creating-cloud-persona/references/workforce/examples/notion-essay-pr/agent.ts",
        "skills/creating-cloud-persona/references/workforce/examples/notion-essay-pr/persona.json",
        "skills/creating-cloud-persona/references/workforce/examples/proactive-issue-resolver/agent.ts",
        "skills/creating-cloud-persona/references/workforce/examples/proactive-issue-resolver/persona.json",
        "skills/creating-cloud-persona/references/workforce/examples/review-agent/agent.ts",
        "skills/creating-cloud-persona/references/workforce/examples/review-agent/persona.json",
        "skills/creating-cloud-persona/references/workforce/examples/review-agent/persona.ts",
        "skills/creating-cloud-persona/references/workforce/examples/weekly-digest/agent.ts",
        "skills/creating-cloud-persona/references/workforce/examples/weekly-digest/persona.json",
        "skills/creating-cloud-persona/references/workforce/packages/cli/src/deploy-command.ts",
        "skills/creating-cloud-persona/references/workforce/packages/deploy/src/extract-agent.ts",
        "skills/creating-cloud-persona/references/workforce/packages/deploy/src/preflight.ts",
        "skills/creating-cloud-persona/references/workforce/packages/persona-kit/schemas/persona.schema.json",
        "skills/creating-cloud-persona/references/workforce/packages/persona-kit/src/types.ts",
        "skills/creating-cloud-persona/references/workforce/packages/runtime/src/clients/index.ts",
        "skills/creating-cloud-persona/references/workforce/packages/runtime/src/types.ts"
      ]
    },
    {
      "name": "factory-config",
      "version": "1.0.2",
      "description": "Use when creating, editing, or validating an Agent Relay Factory factory.config.json file, including repo routing, Linear state/team settings, GitHub issue ingestion, live mode, babysitter options, and Relayflows dispatch wiring boundaries",
      "format": "claude",
      "subtype": "skill",
      "tags": [
        "factory",
        "configuration",
        "relayfile",
        "linear",
        "github",
        "slack",
        "automation"
      ],
      "files": [
        "skills/factory-config/SKILL.md"
      ]
    },
    {
      "name": "openclaw-orchestrator",
      "version": "2.0.0",
      "description": "Run headless multi-agent Agent Relay sessions from OpenClaw. Use when spawning teams of agents, coordinating them over channels, and managing agent lifecycle from an OpenClaw session. Covers only the OpenClaw-specific setup and event reporting; the broker, spawn, and coordination mechanics come from the orchestrating-agent-relay skill.",
      "format": "claude",
      "subtype": "skill",
      "files": [
        "skills/openclaw-orchestrator/SKILL.md"
      ]
    }
  ],
  "collections": [
    {
      "id": "agent-relay-starter",
      "name": "Agent Relay Starter",
      "description": "Essential skills for building multi-agent systems with Agent Relay - swarm pattern selection, workflow authoring, and trail debugging",
      "version": "1.2.0",
      "category": "development",
      "tags": [
        "multi-agent",
        "orchestration",
        "swarm-patterns",
        "workflow",
        "agent-relay"
      ],
      "packages": [
        {
          "packageId": "@agent-relay/choosing-swarm-patterns",
          "version": "latest",
          "required": true,
          "reason": "Decision framework for picking the right multi-agent orchestration pattern"
        },
        {
          "packageId": "@agent-relay/writing-relayflows",
          "version": "latest",
          "required": true,
          "reason": "Authoring guide for the current Relayflows v2 engine (@relayflows/surface / @relayflows/sdk, CLI `flows`)"
        },
        {
          "packageId": "@agent-relay/writing-agent-relay-workflows",
          "version": "latest",
          "required": false,
          "reason": "DEPRECATED v1 WorkflowBuilder reference - install only to maintain an existing v1 workflow"
        },
        {
          "packageId": "@agent-workforce/trail-snippet",
          "version": "latest",
          "required": true,
          "reason": "Trail snippet utility for debugging and inspecting agent execution traces"
        },
        {
          "packageId": "@agent-relay/relay-80-100-workflow",
          "version": "latest",
          "required": false,
          "reason": "E2E validation patterns for workflows that must be production-ready before merging, including review-depth review/fix loops with test hardening"
        },
        {
          "packageId": "@agent-relay/review-fix-signoff-loop",
          "version": "latest",
          "required": false,
          "reason": "Fresh-context review/fix loop pattern for workflows that require independent dual-agent signoff"
        }
      ]
    },
    {
      "id": "relayfile-workspace",
      "name": "Relayfile Workspace",
      "description": "Relayfile workspace primitives for agents - activity digests, workspace layout, and file-native provider writeback",
      "version": "1.0.2",
      "category": "development",
      "tags": [
        "relayfile",
        "workspace",
        "digest",
        "writeback",
        "agent-context"
      ],
      "packages": [
        {
          "packageId": "@agent-relay/activity-summary",
          "version": "latest",
          "required": true,
          "reason": "Read precomputed activity digests before crawling provider trees for time-windowed questions"
        },
        {
          "packageId": "@agent-relay/daily-digest",
          "version": "latest",
          "required": true,
          "reason": "Understand the digest file contract, supported windows, and provider section shape"
        },
        {
          "packageId": "@agent-relay/workspace-layout",
          "version": "latest",
          "required": true,
          "reason": "Navigate relayfile mounts through LAYOUT.md and by-* alias indexes"
        },
        {
          "packageId": "@agent-relay/writeback-as-files",
          "version": "latest",
          "required": true,
          "reason": "Create provider mutations through file-native writeback with schemas and dead-letter recovery"
        },
        {
          "packageId": "@agent-relay/multi-host-live-mount",
          "version": "latest",
          "required": true,
          "reason": "Mount one existing Relayfile workspace on several hosts and prove each agent-visible mirror is current before placement"
        }
      ]
    }
  ]
}