Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub Β· Productivity
OpenServ Multi Agent Workflows
Multi-agent workflow examples to work together on the OpenServ Platform. Covers agent discovery, multi-agent workspaces, task dependencies, and workflow orch...
skill openclawclawhub Free
Multi-agent workflow examples to work together on the OpenServ Platform. Covers agent discovery, multi-agent workspaces, task dependencies, and workflow orch...
β¬ 0 downloads β
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- reference.md, troubleshooting.md, SKILL.md, examples/youtube-to-blog-pipeline.md, examples/paid-image-pipeline.md, examples/polymarket-intelligence.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- 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.
New install
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
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.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.2
Provenance
- Publisher
- issa-me-sush
- Source page
- View original listing
- Canonical URL
- Open canonical page
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
Category context
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
6 Docs
- SKILL.md
- examples/paid-image-pipeline.md
- examples/polymarket-intelligence.md
- examples/youtube-to-blog-pipeline.md
- reference.md
- troubleshooting.md