# Manage OpenServ Agents and Workflows

OpenServ agent deployment requires provisioning, credentials, workflows, and trigger configuration. This skill gives Codex, Claude, and Claude Code a focused OpenServ client reference.

## Install

```bash
npx skillstore add internet-court/openserv-client
```

## Metadata

- Status: approved
- Slug: internet-court-openserv-client
- Skillstore revision: r1
- Version status: missing
- Tree hash: 7643208f6a1acf7899c86e40001444fae090892964a7676be46ece160675b09a
- Author: internet-court
- GitHub username: internet-court
- License: MIT
- Repository: https://github.com/internet-court/internet-court-skill/tree/main/vendored/openserv/openserv-client
- Ref: 3f6e026a3363e0954ede7bef0cfe88d4475de137
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, env\_access, filesystem
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/internet-court-openserv-client
- Manifest: https://skillstore.pages.dev/api/skills/internet-court-openserv-client/manifest

## Capabilities

- Explains provision\(\) setup for agent registration, workflow creation, triggers, and credential binding.
- Documents PlatformClient methods for agents, workflows, triggers, tasks, integrations, models, payments, and web3.
- Shows TypeScript examples for creating agents, activating workflows, and firing webhook or x402 triggers.
- Covers environment variables for wallet and user API key authentication.
- Describes ERC-8004 on-chain registration, wallet funding, and deployment state behavior.
- Includes troubleshooting guidance for stuck tasks, sync issues, auth errors, and paywall fields.

## Use Cases

- Prototype an OpenServ Agent: Use the quick-start flow to plan provisioning, workflow creation, trigger setup, and local agent startup.
- Configure Paid Agent Access: Map x402 trigger settings, input schemas, wallet requirements, and paywall behavior before publishing a paid workflow.
- Operate Platform Resources: Use PlatformClient references to list, update, activate, debug, and clean up OpenServ agents and workflows.

## Prompt Templates

### Plan a Basic Agent

```
Use the openserv-client skill to outline a basic webhook agent setup. Include provisioning, credentials, workflow, trigger, and run sequence.
```

### Choose Authentication

```
Explain which OpenServ credential I should use for PlatformClient management calls. Cover wallet authentication, user API keys, and common mistakes.
```

### Design a Paid Workflow

```
Design an x402 OpenServ workflow for a paid agent service. Include trigger fields, payout wallet requirements, timeout settings, and test steps.
```

### Review Production Readiness

```
Review my OpenServ deployment plan for production readiness. Check provisioning, secret handling, trigger exposure, ERC-8004 registration, cleanup safety, and troubleshooting gaps.
```

## Limitations

- It is documentation and examples, not an installed OpenServ runtime.
- Examples require valid OpenServ credentials and network access to platform services.
- OpenServ APIs may change after the bundled reference was authored.
- Wallet and API key handling must be reviewed before production use.

## Best Practices

- Call provision\(\) before deployment so platform state and local credentials exist.
- Use long timeouts for webhook and x402 triggers that run complex agent tasks.
- Keep wallet private keys and OpenServ API keys out of source control and logs.

## Anti Patterns

- Using the agent API key for PlatformClient management calls.
- Publishing full webhook trigger URLs in public logs or documentation.
- Clearing wallet state when you want to preserve the same ERC-8004 agent identity.

## Security Audit

- Audited at: 2026-07-21T04:27:25.704\+00:00
- Summary: Static detections are predominantly false positives caused by Markdown code fences, TypeScript template literals, documented URLs, and named credential examples. Two contextual risks remain: provision\(\) persists a wallet private key to .env, and the cleanup example can bulk-delete resources without confirmation.

## Stats

- Views: 0
- Downloads: 5
- Favorites: 1
- Popularity score: 0