Skills openserv-multi-agent-workflows

📦

openserv-multi-agent-workflows

Name: openserv-multi-agent-workflows
Author: internet-court

Content revision r2 High Risk ⚙️ External commands🌐 Network access🔑 Env variables

Orchestrate OpenServ Multi-Agent Workflows

Complex agent projects need clear data flow, dependencies, and reliable triggers. This skill provides practical OpenServ patterns for building and operating coordinated workflows.

Supports: Claude Codex Code(CC)

⚠️ 38 Poor

Stop for confirmation before installing.

Review the plan and obtain explicit user consent before changing files.

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "openserv-multi-agent-workflows" from https://skillstore.io/skills/internet-court-openserv-multi-agent-workflows.md and its manifest at https://skillstore.io/api/skills/internet-court-openserv-multi-agent-workflows/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/internet-court-openserv-multi-agent-workflows.md Signed manifest GET /api/skills/internet-court-openserv-multi-agent-workflows/manifest Signed lockfile GET /api/skills/internet-court-openserv-multi-agent-workflows/lockfile

Test it

Using "openserv-multi-agent-workflows". Create a two-agent workflow that researches a topic and drafts a blog post.

Expected outcome:

A sequential design with a webhook trigger, research task, writing task, explicit trigger-to-research and research-to-writing edges, and required inputs.

Using "openserv-multi-agent-workflows". Why does a task not start after its dependency completes?

Expected outcome:

Confirm that the dependency status is done.
Check that the workflow graph contains an edge from the prior task to the waiting task.
Verify that both tasks reference agents present in the workspace.

Using "openserv-multi-agent-workflows". How should I expose a paid OpenServ workflow?

Expected outcome:

Use an x402 trigger, configure a payout wallet, authenticate the client securely, activate the trigger, and test payment and task execution separately.

Security Audit

High Risk

v3 • 8/7/2026 Open versioned report

The 400 static matches are predominantly documentation noise for template literals, diagrams, documented endpoints, and conventional environment-variable configuration. Two direct wallet-private-key references are confirmed security-sensitive, and the workflow examples also lack verification before assigning work to marketplace agents. Static review was capped at 400/444 representative findings; omitted static matches are unconfirmed, so automatic publishing stays disabled until manual review.

Files scanned

2,904

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (3)

High

examples/paid-image-pipeline.md:152

Crypto seed/private key mention

privateKey: process.env.WALLET_PRIVATE_KEY!,

The cited text directly handles a wallet private key for authentication or on-chain registration. Compromise could authorize transactions, so this is a real credential-security risk even though no exfiltration is shown.

High

troubleshooting.md:131

Crypto seed/private key mention

**If using `workflows.create()` or `workflow.sync()` directly:** Ensure the client was authenticated

High

SKILL.md:70-75 examples/blog-pipeline.md:74-94

Unverified Marketplace Agent Selection

The workflow examples select the first marketplace search result and assign it user-provided work without showing identity, publisher, capability, permission, or data-handling verification. A malicious or unsuitable agent could receive sensitive inputs or return unsafe content.

The cited workflow explicitly searches the marketplace, takes the first result, and passes its identifier into workflow creation. No trust or capability validation appears in the documented pattern.

Risk Factors

⚙️ External commands (50)

🌐 Network access (34)

examples/blog-pipeline.md:144 examples/blog-pipeline.md:146 examples/blog-pipeline.md:225 examples/blog-pipeline.md:257 examples/content-creation-pipeline.md:158 examples/content-creation-pipeline.md:160 examples/content-creation-pipeline.md:201 examples/crypto-alpha-pipeline.md:149 examples/crypto-alpha-pipeline.md:151 examples/crypto-alpha-pipeline.md:192 examples/life-coaching-pipeline.md:223 examples/life-coaching-pipeline.md:225 examples/life-coaching-pipeline.md:278 examples/podcast-production-line.md:147 examples/podcast-production-line.md:149 examples/podcast-production-line.md:190 examples/polymarket-intelligence.md:147 examples/polymarket-intelligence.md:149 examples/polymarket-intelligence.md:190 examples/social-media-pipeline.md:149 examples/social-media-pipeline.md:151 examples/social-media-pipeline.md:192 examples/tokenomics-design-pipeline.md:151 examples/tokenomics-design-pipeline.md:153 examples/tokenomics-design-pipeline.md:194 examples/video-content-factory.md:147 examples/video-content-factory.md:149 examples/video-content-factory.md:190 examples/youtube-to-blog-pipeline.md:149 examples/youtube-to-blog-pipeline.md:151 examples/youtube-to-blog-pipeline.md:153 examples/youtube-to-blog-pipeline.md:192 examples/youtube-to-blog-pipeline.md:194 reference.md:147

🔑 Env variables (50)

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/internet-court-openserv-multi-agent-workflows/audits/3?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/internet-court-openserv-multi-agent-workflows/security.svg)](https://skillstore.io/skills/internet-court-openserv-multi-agent-workflows?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/internet-court-openserv-multi-agent-workflows?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/internet-court-openserv-multi-agent-workflows/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/internet-court-openserv-multi-agent-workflows.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

internet-court. (2026). openserv-multi-agent-workflows security audit report (audit version 3) [Author version unspecified]. Skillstore. https://skillstore.io/skills/internet-court-openserv-multi-agent-workflows/audits/3

BibTeX citation

@techreport{internet-court-internet-court-openserv-multi-agent-workflows-2026,
  author = {internet-court},
  title = {openserv-multi-agent-workflows security audit report (audit version 3)},
  institution = {Skillstore},
  year = {2026},
  number = {3},
  url = {https://skillstore.io/skills/internet-court-openserv-multi-agent-workflows/audits/3},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "openserv-multi-agent-workflows security audit report (audit version 3)"
version: "unspecified"
type: report
authors:
  - name: "internet-court"
date-released: "2026-08-07"
url: "https://skillstore.io/skills/internet-court-openserv-multi-agent-workflows/audits/3"
identifiers:
  - type: other
    value: "skillstore:internet-court-openserv-multi-agent-workflows:audit:3"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Plan a Content Pipeline

Design a sequential workflow that researches a topic, writes content, and sends results through explicit task edges.

Launch a Paid Agent Service

Adapt provisioning and x402 examples to expose a paid workflow with wallet configuration and clear task sequencing.

Debug Workflow Execution

Use the reference and troubleshooting guidance to inspect triggers, dependencies, workspace agents, and synchronization behavior.

Try These Prompts

Explain the Basics

Explain how OpenServ workflows, agents, tasks, triggers, dependencies, and edges fit together for a beginner.

Design a Sequential Workflow

Design an OpenServ workflow for [goal]. Define the agents, task order, inputs, outputs, trigger, and edges.

Adapt an Example

Adapt the most relevant example for [use case]. Preserve explicit data flow, validate required agents, and list configuration changes.

Review Production Readiness

Review this OpenServ workflow design for security, reliability, cost control, agent trust, webhook exposure, and failure handling. Return prioritized fixes.

Best Practices

Use explicit edges to express intentional data flow between triggers and tasks.
Keep tasks focused and validate marketplace agents before assigning them work or sensitive inputs.
Protect wallet credentials, test paid triggers with limits, and monitor workflow state after synchronization.

Avoid

Connecting every task to every other task without a clear data dependency.
Selecting the first marketplace search result without checking identity, capability, trust, or cost.
Committing wallet keys to a repository or exposing webhook tokens without access controls.