Publisher Review

Submission gate

A submission must include publisher identity, version, runtime, input/output schemas, permission notes, examples, support path, changelog, and pricing intent when the Skill is paid-marketplace.

Operator checks

SkillHub reviews JSON structure, required manifest fields, semantic versioning, schema shape, permission scope, runtime declarations, sample responses, support ownership, and marketplace placement.

Runtime readiness

Runtime URLs, health checks, sample inputs, response shape, failure modes, timeout behavior, and rate-limit behavior must match the manifest before a Skill is marked verified.

Review states and next actions

Review states are written as operational handoffs so publishers and buyers can tell what happens next.

• Draft: publisher completes manifest, examples, support path, and permission notes.
• Submitted: SkillHub queues automated validation and operator review.
• In review: operators check trust, runtime, policy, and marketplace fit.
• Needs changes: publisher fixes the listed issue and resubmits the draft or a new version.
• Verified: buyers may evaluate the Skill with the current manifest, permissions, and runtime contract.
• Restricted or rejected: distribution is blocked until the reason is resolved or appealed.

Paid marketplace boundaries

Paid marketplace listings may show price intent or active price records. Checkout, refunds, commissions, taxes, and payouts require explicitly enabled provider and finance flows.

Change control

Publishers should submit a new version or revise draft metadata rather than mutating verified behavior in place.

• Open publisher skill workspace
• Runtime or permission changes require a new review before the verified label should carry forward.
• Pricing changes remain preview-only unless checkout and provider billing are live for that listing.
• Restricted or rejected decisions should stay visible so operators can audit the resolution path.