Marketplace IA

A governed path for skills, plugins, recipes, and templates

The marketplace surface is intentionally documentation-first until manifest validation, permission review, and submission workflows are ready.

No upload flow before validation

The public surface explains submission expectations without accepting unreviewed artifacts.

Every listing must make runtime access, secrets, network calls, and regional assumptions explicit.

Prompt and config bundles that teach an agent a repeatable workflow.

Runtime integrations that expose tools without occupying prompt context.

Task-specific Discover -> Inspect -> Call examples with expected parameters.

Starter projects that combine QVeris APIs, UI, auth, and deployment defaults.

nameRequired

Human-readable listing name.

slugRequired

Stable URL and manifest identifier.

versionRequired

Semantic version for upgrade and rollback decisions.

authorRequired

Person, team, or organization responsible for maintenance.

kindRequired

One of skill, plugin, recipe, or template.

permissionsRequired

Network, file, secret, browser, or tool permissions needed at runtime.

compatible_surfacesRequired

OpenClaw, CLI, MCP clients, IDEs, or hosted agents that can run it.

examplesRequired

Runnable examples that show expected inputs, outputs, and failure handling.

quality_statusRequired

Observed install success, smoke result, docs completeness, and owner freshness.

review_stateRequired

draft, submitted, reviewed, verified, or deprecated.

source_urlRequired

Repository, package, or release artifact used for review.

security_notesOptional

Known limitations, sandbox assumptions, data handling, or regional constraints.