Agent skill

Openserv Multi Agent Workflows

by internet-court in internet-court/internet-court-skill

Multi-agent workflow examples to work together on the OpenServ Platform.

MITAuto-check passedAgent Workflows

Install Openserv Multi Agent Workflows

skills CLI
$ npx skills add internet-court/internet-court-skill --skill openserv-multi-agent-workflows -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install internet-court/internet-court-skill openserv-multi-agent-workflows --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/internet-court/internet-court-skill.git skills-src && mkdir -p .claude/skills && cp -r skills-src/vendored/openserv/openserv-multi-agent-workflows .claude/skills/openserv-multi-agent-workflows && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
openserv-multi-agent-workflows
GitHub stars
6.5k
Used in
1 other repo
Token cost
~1.6k tokens
SKILL.md length
588 words
Files
15
Skills in repo
80
Repo updated
First seen
Licence
MIT

At a glance

Multi-agent workflow examples to work together on the OpenServ Platform.

  • Works in 3 steps: Authenticate with client.authenticate() → Find agents with… → Create workflow with…
  • Tasks that involve Multi-agent orchestration
  • SKILL.md covers Quick Start, Workflow Name & Goal, Core Concepts and Edge Design Best Practices, plus 2 more sections
  • Calls npx

What it does

Openserv Multi Agent Workflows is an agent skill from internet-court/internet-court-skill. Multi-agent workflow examples to work together on the OpenServ Platform. Covers agent discovery, multi-agent workspaces, task dependencies, and workflow orchestration using the Platform Client. Read reference.md for the full API reference. Read openserv-agent-sdk and openserv-client for building and running agents.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 15 other files (for example `examples/blog-pipeline.md`, `examples/content-creation-pipeline.md` and `examples/crypto-alpha-pipeline.md`).

It sits in Agent Workflows, covering Multi-agent orchestration and Building AI agents. The repository describes itself as: The trust layer for agent-to-agent commerce — natural-language mandates, ERC-7710 delegated permissions, x402 payments, escrow, and dispute resolution as one open, catch-all… The licence is MIT.

When your agent uses it

  • Tasks that involve Multi-agent orchestration
  • Tasks that involve Building AI agents

Example prompts

  • “/openserv-multi-agent-workflows”

Requirements

  • Node.js

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Authenticate with client.authenticate()
  2. Find agents with client.agents.listMarketplace()
  3. Create workflow with client.workflows.create() including

What it can do on your machine

Read from SKILL.md and the folder at commit fa89195. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Openserv Multi Agent Workflows loads about 1.6k tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 588 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~87
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from internet-court/internet-court-skill at commit fa89195, republished under its MIT licence (© internet-court). 588 words, ~1,616 tokens.

Download SKILL.mdSave it as .claude/skills/openserv-multi-agent-workflows/SKILL.md (or your agent's skills folder). This skill also uses 14 other files; get the full folder from GitHub.
name
openserv-multi-agent-workflows
description
Multi-agent workflow examples to work together on the OpenServ Platform. Covers agent discovery, multi-agent workspaces, task dependencies, and workflow orchestration using the Platform Client. Read reference.md for the full API reference. Read openserv-agent-sdk and openserv-client for building and running agents.

Multi-Agent Workflows on OpenServ

Build workflows where multiple AI agents collaborate to complete complex tasks.

Reference files:

  • reference.md - Workflow patterns, declarative sync, triggers, monitoring
  • troubleshooting.md - Common issues and solutions
  • examples/ - Complete pipeline examples (blog, youtube-to-blog, etc.)

Quick Start

See examples/ for complete runnable examples:

  • blog-pipeline.md - Simple 2-agent workflow (research → write)
  • content-creation-pipeline.md - 3-agent workflow (research → write → image)
  • life-coaching-pipeline.md - Complex 6-agent workflow with comprehensive input schema

Recommended pattern using workflows.sync():

  1. Authenticate with client.authenticate()
  2. Find agents with client.agents.listMarketplace()
  3. Create workflow with client.workflows.create() including:
    • Triggers
    • Tasks
    • Edges (⚠️ CRITICAL - connects triggers and tasks together)

⚠️ CRITICAL: Always define edges when creating workflows. Setting task dependencies is NOT enough - you must create workflow edges to actually connect triggers to tasks and tasks to each other.


Workflow Name & Goal

When creating workflows (via workflows.create() or provision()), two properties are critical:

  • name (string) - This becomes the agent name in ERC-8004. Make it polished, punchy, and memorable — this is the public-facing brand name users see. Think product launch, not variable name. Examples: 'Instant Blog Machine', 'AI Video Studio', 'Polymarket Intelligence'.
  • goal (string, required) - A detailed description of what the workflow accomplishes. Must be descriptive and thorough — short or vague goals will cause API calls to fail. Write at least a full sentence explaining the end-to-end purpose of the workflow.

Core Concepts

Workflows

A workflow (workspace) is a container that holds multiple agents and their tasks.

Task Dependencies
  • Each task is assigned to a specific agent
  • Tasks can depend on other tasks: dependencies: [taskId1, taskId2]
  • A task only starts when all dependencies are done
  • Output from dependencies is passed to dependent tasks
Workflow Graph
  • Nodes: Triggers and tasks
  • Edges: Connections between nodes
  • When Task A completes, its output flows to dependent tasks via edges
Agent Discovery
typescript
// Search marketplace for agents by name/capability (semantic search)
const result = await client.agents.listMarketplace({ search: 'research' })
const agents = result.items // Array of marketplace agents

// Get agent details
const agent = await client.agents.get({ id: 123 })
console.log(agent.capabilities_description)

// Note: client.agents.searchOwned() only searches YOUR OWN agents
// Use listMarketplace() to find public agents for multi-agent workflows

Common agent types: Research (Grok, Perplexity), Content writers, Data analysis, Social media (Nano Banana Pro), Video/audio creators.


Edge Design Best Practices

CRITICAL: Carefully design your workflow edges to avoid creating tangled "spaghetti" graphs.

A well-designed workflow has clear, intentional data flow. Common mistakes lead to unmaintainable workflows.

Bad Pattern - Everything Connected to Everything
         ┌──────────────────────────────────┐
         │           ┌─────────┐            │
         │     ┌─────┤ Agent A ├─────┐      │
         │     │     └────┬────┘     │      │
         │     │          │          │      │
Trigger ─┼─────┼──────────┼──────────┼──────┤
         │     │          │          │      │
         │     │     ┌────┴────┐     │      │
         │     └─────┤ Agent B ├─────┘      │
         │           └─────────┘            │
         └──────────────────────────────────┘
              (Spaghetti - avoid this!)

This creates:

  • Unclear execution order
  • Difficult debugging
  • Agents receiving redundant/conflicting inputs
  • Hard to understand what depends on what
Show full SKILL.md (229 more words)Show less
Good Patterns

Sequential Pipeline:

Trigger → Research → Content → Enhancement → Output

Staged Fan-Out:

                    ┌─ Task A ─┐
Trigger → Research ─┼─ Task B ─┼─→ Combiner → Output
                    └─ Task C ─┘

Conditional Branching (v1.1.3+):

                    ┌─[approved]─→ Process
Trigger → Review ──┤
                    └─[rejected]─→ Reject Handler

Use outputOptions on tasks and sourcePort on edges for branching.

Guidelines for Clean Workflows
  1. Linear is usually best: Start with a simple chain, only add complexity when truly needed
  2. Each task should have a clear purpose: If you can't explain why Task A connects to Task B, remove the edge
  3. Minimize cross-connections: Avoid connecting every agent to every other agent
  4. Use fan-out only for parallel work: Multiple tasks from one source is fine; connecting everything to everything is not
  5. One combiner at the end: If you need to merge outputs, have ONE final task that depends on all parallel branches
Before Adding an Edge, Ask:
  • Does Task B actually need the output of Task A?
  • Would Task B work without this connection?
  • Am I adding this edge "just in case"? (Don't!)

Updating This Skill

This skill may be outdated. The OpenServ team ships updates regularly—new features, API changes, and bug fixes won't be reflected here until you update. If something isn't working as expected, or you want to make sure you have the latest information, update the skill before proceeding.

bash
# Check if updates are available
npx skills check

# Update all installed skills to latest versions
npx skills update

Or reinstall the OpenServ skills directly:

bash
npx skills add openserv-labs/skills

  • openserv-agent-sdk - Building individual agent capabilities
  • openserv-client - Full Platform Client API reference
  • openserv-launch - Launch tokens on Base blockchain
  • openserv-ideaboard-api - Find ideas and ship agent services on the Ideaboard

© internet-court, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 14 other files in vendored/openserv/openserv-multi-agent-workflows of internet-court/internet-court-skill.

  • SKILL.md
  • LICENSE
  • examples/blog-pipeline.md
  • examples/content-creation-pipeline.md
  • examples/crypto-alpha-pipeline.md
  • examples/life-coaching-pipeline.md
  • examples/paid-image-pipeline.md
  • examples/podcast-production-line.md
  • examples/polymarket-intelligence.md
  • examples/social-media-pipeline.md
  • examples/tokenomics-design-pipeline.md
  • examples/video-content-factory.md
  • examples/youtube-to-blog-pipeline.md
  • reference.md
  • troubleshooting.md

Open the folder on GitHubat commit fa89195

Used in 1 other repository

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in internet-court/internet-court-skill, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Openserv Multi Agent Workflows next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Openserv Multi Agent Workflows compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Openserv Multi Agent Workflows this skillinternet-court/internet-court-skill6.5k1 repos~1.6kAutomated safety check: PassMIT
Adk Agent Buildergoogle/adk-python22k—~879Automated safety check: PassApache-2.0
Agents Buildaws/agent-toolkit-for-aws2.8k—~2.3kAutomated safety check: NotesApache-2.0
Omnigent Agent Builderomnigent-ai/omnigent11k—~2.1kAutomated safety check: PassApache-2.0
Feishu Multi Agenthyperlist/feishu-multi-agent273—~419Automated safety check: PassNone
Swarmclawswarmclawai/swarmclaw688—~2kAutomated safety check: PassMIT

Similar skills

  • Adk Agent Builder

    google/adk-python

    Official

    Builds ADK (Agent Development Kit) Python agents: LLM agents with tools, graph workflows of function and agent nodes, conditional routing, fan-out and join, schema-validated delegation between…

    22k GitHub stars~879 tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Agents Build

    aws/agent-toolkit-for-aws

    Official

    A skill your agent uses to extend an existing agent project with memory, app integration, VPC, multi-agent, migration, model, browser, code interpreter, payments, or resource removal.

    2.8k GitHub stars~2.3k tokensUpdated yesterday
    Agent WorkflowsAuto-check: notes
  • Omnigent Agent Builder

    omnigent-ai/omnigent

    Gives patterns for generating a minimal, valid Omnigent agent directory: the config.yaml fields, the right executor type, and the files each agent needs.

    11k GitHub stars~2.1k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Feishu Multi Agent

    hyperlist/feishu-multi-agent

    飞书多 Agent 系统搭建指南。当用户要求创建新的功能 Agent、配置飞书群聊绑定、 搭建多 Agent 协作系统时激活此 skill。

    273 GitHub stars~419 tokensUpdated 7 mo ago
    Agent WorkflowsAuto-check passed
  • Swarmclaw

    swarmclawai/swarmclaw

    AI agent runtime and multi-agent orchestration platform. An agent skill from swarmclawai/swarmclaw.

    688 GitHub stars~2k tokensUpdated 3 mo ago
    Agent WorkflowsAuto-check passed
  • Swarmclaw

    swarmclawai/swarmclaw

    Manage your SwarmClaw agent fleet — agents, tasks, chats, chatrooms, goals, schedules, memory, wallets, connectors, autonomy, and 40+ more command groups.

    688 GitHub stars~4.2k tokensUpdated 3 mo ago
    Agent WorkflowsAuto-check passed

More from internet-court/internet-court-skill

All 80 skills in this repo
  • Kleros IPFS Upload

    internet-court/internet-court-skill

    Uploads one Kleros-related file per paid request to IPFS through the Kleros x402 gateway for 0.01 USDC on Base, returning a CID that Kleros contracts can reference.

    6.5k GitHub stars~4.9k tokensUpdated 1 mo ago
    Auto-check: notes
  • 0G Compute Network Guide

    internet-court/internet-court-skill

    Guides building on the 0G Compute Network, a decentralized GPU marketplace for AI inference and fine-tuning, with SDK patterns and CLI commands.

    6.5k GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed
  • PNP Prediction Markets on Solana

    internet-court/internet-court-skill

    Creates, trades and settles permissionless prediction markets on Solana with any SPL token as collateral, including social-media and custom-oracle markets.

    6.5k GitHub stars~7.5k tokensUpdated 1 mo ago
    Auto-check: notes
  • BNB Chain MCP Server

    internet-court/internet-court-skill

    Connects an agent to the BNB Chain MCP server to read blocks and contracts, move tokens and NFTs, register ERC-8004 agents and use Greenfield storage.

    6.5k GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed
  • GenLayer ERC-7710 Connector

    internet-court/internet-court-skill

    Specifies how a GenLayer Intelligent Contract decision about an agent's performance becomes an ERC-7710 revocation or policy change, through a relayer or bridge and an EVM controller.

    6.5k GitHub starsUsed in 1 repo~2.2k tokens
    Auto-check passed
  • GenLayer Agent Supervision Adapter

    internet-court/internet-court-skill

    Specifies how a GenLayer Intelligent Contract should supervise an AI agent, with review rubrics, evidence schemas and continue, warn, constrain or revoke decisions.

    6.5k GitHub starsUsed in 1 repo~1.8k tokens
    Auto-check passed

Categories

Questions about Openserv Multi Agent Workflows

What does Openserv Multi Agent Workflows do?

Multi-agent workflow examples to work together on the OpenServ Platform. Openserv Multi Agent Workflows is an agent skill from internet-court/internet-court-skill. Multi-agent workflow examples to work together on the OpenServ Platform.

When should I use Openserv Multi Agent Workflows?

Openserv Multi Agent Workflows fits situations like: tasks that involve Multi-agent orchestration; tasks that involve Building AI agents.

How do I install Openserv Multi Agent Workflows in Claude Code?

Run `npx skills add internet-court/internet-court-skill --skill openserv-multi-agent-workflows -a claude-code`. Or copy the skill folder (vendored/openserv/openserv-multi-agent-workflows in internet-court/internet-court-skill) into .claude/skills/openserv-multi-agent-workflows in your project. Claude Code loads it when a task matches its description.

How do I install Openserv Multi Agent Workflows in Codex?

Run `npx skills add internet-court/internet-court-skill --skill openserv-multi-agent-workflows -a codex`. Or copy the skill folder (vendored/openserv/openserv-multi-agent-workflows in internet-court/internet-court-skill) into .agents/skills/openserv-multi-agent-workflows in your project. Codex loads it when a task matches its description.

Can I use Openserv Multi Agent Workflows in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add internet-court/internet-court-skill --skill openserv-multi-agent-workflows -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/openserv-multi-agent-workflows, .gemini/skills/openserv-multi-agent-workflows, .github/skills/openserv-multi-agent-workflows and .opencode/skills/openserv-multi-agent-workflows in your project.

What does Openserv Multi Agent Workflows need to run?

Going by SKILL.md and its folder, Openserv Multi Agent Workflows needs the command-line tools its instructions call (npx). Our summary lists: Node.js.

Does Openserv Multi Agent Workflows access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Openserv Multi Agent Workflows safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Openserv Multi Agent Workflows use?

Openserv Multi Agent Workflows is published under the MIT licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Openserv Multi Agent Workflows use?

About 1.6k tokens (SKILL.md is roughly 6.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Openserv Multi Agent Workflows?

Skills that share tags, products or a category with Openserv Multi Agent Workflows: Adk Agent Builder (google/adk-python, 22k stars), Agents Build (aws/agent-toolkit-for-aws, 2.8k stars), Omnigent Agent Builder (omnigent-ai/omnigent, 11k stars) and Feishu Multi Agent (hyperlist/feishu-multi-agent, 273 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Openserv Multi Agent Workflows?

internet-court (a GitHub organization) maintains it in internet-court/internet-court-skill, which has 6,471 GitHub stars. The repository holds 80 skills in this directory. The repository was last updated on August 19, 2026.

Source: internet-court/internet-court-skill on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.