OpenServ Client
PassAudited by VirusTotal on May 12, 2026.
Overview
Type: OpenClaw Skill Name: openserv-client Version: 1.0.4 The OpenClaw AgentSkills skill bundle provides a client library for interacting with the OpenServ platform, including agent/workflow management, x402 payments, and ERC-8004 on-chain identity. All code and documentation align with this stated purpose, demonstrating legitimate interactions with the platform API and blockchain. While the skill handles sensitive credentials like `WALLET_PRIVATE_KEY` and `OPENSERV_API_KEY` (e.g., writing `WALLET_PRIVATE_KEY` to `.env` via `provision()`), this is a necessary function for its operation and does not show intent for unauthorized exfiltration or malicious use. No evidence of prompt injection, obfuscation, or other malicious behaviors was found in `SKILL.md`, `reference.md`, `troubleshooting.md`, or the example scripts.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If the local environment file or generated state leaks, someone could potentially access the OpenServ account, agent credentials, or wallet-controlled resources.
The examples show that provisioning creates or stores wallet and OpenServ credentials locally. This is expected for platform authentication, but those values are sensitive.
# Auto-populated by provision() - DO NOT fill manually WALLET_PRIVATE_KEY= OPENSERV_API_KEY= OPENSERV_AUTH_TOKEN=
Run this only in a trusted project directory, keep .env and .openserv.json out of source control, and rotate credentials if they are exposed.
Running the examples can create or update agents and workflows and make triggers callable on the OpenServ platform.
The normal provisioning flow mutates OpenServ platform resources and activates triggers. This matches the skill purpose, but it has real account impact when run.
Creates or updates the agent... Creates or updates the workflow with trigger and task... Activates trigger and sets workflow to running
Use a test account or test wallet first, review the workflow and trigger settings, and only provision when you intend to create or update platform resources.
If run with --all, the cleanup script can remove OpenServ workflows and agents from the authenticated account.
The cleanup example contains an explicit user-invoked --all option that deletes all listed workflows and agents. It is disclosed, but destructive.
if (args.includes('--all')) { ... await client.workflows.delete({ id: w.id }) ... await client.agents.delete({ id: a.id }) }Do not run cleanup.ts with --all unless you have verified the account and are sure those resources should be deleted.
Installing the package runs code from the npm supply chain rather than code fully reviewed here.
The skill relies on an external npm package that is not included in the reviewed artifacts. This is expected for a client guide, but package provenance is outside this artifact review.
npm install @openserv-labs/client
Verify the npm package name, publisher, version, and lockfile before using it in production.
Anyone who obtains the webhook URL may be able to trigger the associated workflow, depending on OpenServ controls.
The example prints a tokenized webhook URL used to invoke the workflow. This is purpose-aligned, but the URL/token should be treated as sensitive.
console.log(`Webhook: https://api.openserv.ai/webhooks/trigger/${result.triggerToken}`)Avoid sharing webhook URLs publicly unless intended, and rotate or recreate triggers if a tokenized URL is exposed.