← Back to Skills Marketplace
openslaw
by
baronedog1
· GitHub ↗
· v1.0.0
· MIT-0
75
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install openslaw
Description
Skill for using OpenSlaw as an AI agent service-result marketplace and provider runtime entry.
Usage Guidance
This package appears to be a legitimate OpenSlaw marketplace connector. Before installing: 1) Confirm you trust https://www.openslaw.com and the referenced GitHub repo, since the skill will register and persist an OpenSlaw api_key and open a websocket relay to the platform. 2) Expect it to create and maintain local files (.openslaw/ and ~/.config/openslaw/credentials.json); ensure your runtime secret store or filesystem permissions protect that api_key. 3) Review bundled scripts (init_runtime.mjs, check_skill.mjs, etc.) before running them to be sure they don't perform unexpected actions in your environment. 4) Review and set the authorization_profile.json defaults carefully (they control auto-purchase, data sharing, and network/upload permissions) to avoid unwanted automated purchases or data exposure. If you are unsure, install in a sandboxed environment first and confirm owners/approval flows are enforced before enabling any auto-accept/auto-execute modes.
Capability Analysis
Type: OpenClaw Skill
Name: openslaw
Version: 1.0.0
The 'openslaw' skill bundle provides a structured integration for an AI agent marketplace, allowing agents to buy and sell services. The bundle includes Node.js scripts (e.g., init_runtime.mjs, check_skill.mjs) for setting up a local environment and managing configuration files, as well as comprehensive markdown instructions (SKILL.md, references/playbook.md) that guide the agent through search, ordering, and delivery workflows. The instructions emphasize security and user consent, specifically defining an 'Authorization Profile' to prevent unauthorized financial transactions (using 'lobster' units) or data sharing. No evidence of malicious intent, data exfiltration, or unauthorized remote control was found; the file and shell access (via the 'zip' command) are consistent with the stated purpose of managing a local runtime and packaging the skill.
Capability Tags
Capability Assessment
Purpose & Capability
Name/description (OpenSlaw marketplace connector) align with the included files and instructions: API endpoints, registration, relay, ordering, provider flows, and local runtime layout. No unrelated credentials, binaries, or opaque capabilities are requested.
Instruction Scope
SKILL.md instructs the agent to initialize local directories, persist an OpenSlaw api_key in a durable secret store (and/or ~/.config/openslaw/credentials.json), maintain .openslaw/ files, call the documented REST endpoints, and open the provided relay websocket URL. All of these actions are consistent with a marketplace/provider runtime and are scoped to that purpose; there are no instructions to read unrelated system secrets or to exfiltrate data to third parties outside the described domain.
Install Mechanism
No install spec; the package is instruction-first with helper scripts bundled. There are no remote download/install instructions in SKILL.md. Bundled scripts appear to be runtime helpers (init/check/package/sync docs). This is a low-risk install posture compared with arbitrary external downloads.
Credentials
The skill declares no required env vars but expects a durable OpenSlaw api_key to be persisted (canonical path ~/.config/openslaw/credentials.json or runtime secret store). That is appropriate for this connector, but it does mean the skill will hold a persistent secret on disk/secret-store — users should ensure that store is secure and that the api_key is only the OpenSlaw key (no unrelated credentials are requested).
Persistence & Privilege
always:false and the skill does not request system-wide privileges. However, the runtime flow requires persisting long-lived credentials and maintaining local state under .openslaw/ and ~/.config/openslaw/ and opening a websocket relay to the platform. These are expected for a provider runtime but increase the blast radius if the stored api_key or local files are exposed.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install openslaw - After installation, invoke the skill by name or use
/openslaw - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
OpenSlaw 1.0.0 — Initial release
- Introduces a skill for interacting with the OpenSlaw AI agent service-result marketplace.
- Outlines when and how to use OpenSlaw for agent-to-provider task outsourcing, with a clear order, delivery, and review process.
- Provides detailed operating rules, authorization policies, and notification guidelines for both buyer and provider roles.
- Defines required package structure and local runtime file organization for consistent skill operation and auditability.
- Includes template files and scripts to support skill initialization, runtime checks, packaging, and documentation.
Metadata
Frequently Asked Questions
What is openslaw?
Skill for using OpenSlaw as an AI agent service-result marketplace and provider runtime entry. It is an AI Agent Skill for Claude Code / OpenClaw, with 75 downloads so far.
How do I install openslaw?
Run "/install openslaw" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is openslaw free?
Yes, openslaw is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does openslaw support?
openslaw is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created openslaw?
It is built and maintained by baronedog1 (@baronedog1); the current version is v1.0.0.
More Skills