ZhenSkill Whitepaper
This whitepaper defines what ZhenSkill is, how the marketplace operates, what trust boundaries exist, and how commercial delivery is governed for buyers, developers, and platform operators.
Last updated: 2026-04-09
1. Marketplace mission and scope
ZhenSkill is the public marketplace for OpenClaw-compatible skills. It combines marketing pages, docs, skill catalog browsing, paid and free distribution, reviews, developer submission flows, moderation tools, and payment integrations in one production site.
The platform scope in this repository is intentionally limited to the marketplace main site. It does not operate a separate ZhenContract escrow runtime, contract-specific APIs, or escrow webhook flows.
2. Operating model
The marketplace serves three primary roles: buyers who discover and acquire skills, developers who submit and maintain skill packages, and operators who review content and observe platform health.
Public content is optimized for discovery, while commercial fulfillment is handled through authenticated APIs, entitlement records, download delivery controls, and payment session tracking.
- Catalog and skill detail pages drive discovery and conversion.
- Developer workflows cover registration, upload, submission, and dashboard reporting.
- Admin workflows cover moderation, review queues, and operational oversight.
3. Trust and safety model
Marketplace trust relies on layered controls rather than a single gate. Submission permissions, package storage boundaries, review workflows, rate limiting, audit data, and health endpoints together define the production safety posture.
Paid package delivery must not expose raw storage paths to anonymous users. Skill access is enforced by entitlement checks and protected download routes so that commercial rights are aligned with runtime delivery.
4. Commerce and delivery
ZhenSkill supports direct payment provider integrations and webhook-driven status updates. Payment completion must propagate through provider verification, order updates, entitlement activation, and controlled fulfillment.
Delivery for packaged skills is governed by protected download APIs, download logging, and server-side file access rules. Public marketing visibility is separate from fulfillment authorization.
- Provider events must preserve signature validity through the routing layer.
- Order status changes must activate the correct buyer entitlement.
- Protected downloads must map to internal package storage instead of public asset aliases.
5. Product roadmap and governance
The near-term governance focus is to keep the marketplace transaction loop stable while continuing to close non-commerce blocking gaps such as standards publication, public protocol documentation, and web chat workflow coverage.
All externally promised capabilities should have a matching public entry point, operational route, and test evidence before being treated as production-complete.