# Send OpenServ Multi Agent Workflows to your agent Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually. ## Fast path - Download the package from Yavira. - Extract it into a folder your agent can access. - Paste one of the prompts below and point your agent at the extracted folder. ## Suggested prompts ### New install ```text I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete. ``` ### Upgrade existing ```text I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run. ``` ## Machine-readable fields ```json { "schemaVersion": "1.0", "item": { "slug": "openserv-multi-agent-workflows", "name": "OpenServ Multi Agent Workflows", "source": "tencent", "type": "skill", "category": "效率提升", "sourceUrl": "https://clawhub.ai/issa-me-sush/openserv-multi-agent-workflows", "canonicalUrl": "https://clawhub.ai/issa-me-sush/openserv-multi-agent-workflows", "targetPlatform": "OpenClaw" }, "install": { "downloadUrl": "/downloads/openserv-multi-agent-workflows", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=openserv-multi-agent-workflows", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "packageFormat": "ZIP package", "primaryDoc": "SKILL.md", "includedAssets": [ "reference.md", "troubleshooting.md", "SKILL.md", "examples/youtube-to-blog-pipeline.md", "examples/paid-image-pipeline.md", "examples/polymarket-intelligence.md" ], "downloadMode": "redirect", "sourceHealth": { "source": "tencent", "slug": "openserv-multi-agent-workflows", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-30T17:12:20.001Z", "expiresAt": "2026-05-07T17:12:20.001Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=openserv-multi-agent-workflows", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=openserv-multi-agent-workflows", "contentDisposition": "attachment; filename=\"openserv-multi-agent-workflows-1.0.2.zip\"", "redirectLocation": null, "bodySnippet": null, "slug": "openserv-multi-agent-workflows" }, "scope": "item", "summary": "Item download looks usable.", "detail": "Yavira can redirect you to the upstream package for this item.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/openserv-multi-agent-workflows" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] } }, "links": { "detailUrl": "https://openagent3.xyz/skills/openserv-multi-agent-workflows", "downloadUrl": "https://openagent3.xyz/downloads/openserv-multi-agent-workflows", "agentUrl": "https://openagent3.xyz/skills/openserv-multi-agent-workflows/agent", "manifestUrl": "https://openagent3.xyz/skills/openserv-multi-agent-workflows/agent.json", "briefUrl": "https://openagent3.xyz/skills/openserv-multi-agent-workflows/agent.md" } } ``` ## Documentation ### 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(): Authenticate with client.authenticate() Find agents with client.agents.listMarketplace() 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. ### 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 // 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 ### 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 Linear is usually best: Start with a simple chain, only add complexity when truly needed Each task should have a clear purpose: If you can't explain why Task A connects to Task B, remove the edge Minimize cross-connections: Avoid connecting every agent to every other agent Use fan-out only for parallel work: Multiple tasks from one source is fine; connecting everything to everything is not 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. # Check if updates are available npx skills check # Update all installed skills to latest versions npx skills update Or reinstall the OpenServ skills directly: npx skills add openserv-labs/skills ### Related 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 ## Trust - Source: tencent - Verification: Indexed source record - Publisher: issa-me-sush - Version: 1.0.2 ## Source health - Status: healthy - Item download looks usable. - Yavira can redirect you to the upstream package for this item. - Health scope: item - Reason: direct_download_ok - Checked at: 2026-04-30T17:12:20.001Z - Expires at: 2026-05-07T17:12:20.001Z - Recommended action: Download for OpenClaw ## Links - [Detail page](https://openagent3.xyz/skills/openserv-multi-agent-workflows) - [Send to Agent page](https://openagent3.xyz/skills/openserv-multi-agent-workflows/agent) - [JSON manifest](https://openagent3.xyz/skills/openserv-multi-agent-workflows/agent.json) - [Markdown brief](https://openagent3.xyz/skills/openserv-multi-agent-workflows/agent.md) - [Download page](https://openagent3.xyz/downloads/openserv-multi-agent-workflows)