Submission requirements
A Skill submission needs identity, version, runtime, input/output schemas, permissions, examples, support path, changelog, and preview pricing intent when applicable.
Publisher trust
Publisher Review
Marketplace trust depends on a review path that is understandable to publishers and buyers.
Manifest and schema validation
SkillHub checks JSON structure, required fields, semantic versioning, schema shape, examples, and runtime declarations.
Permission review
Network, browser, filesystem, secrets, sensitive data, destructive actions, and payment-related permissions require explicit review.
Runtime endpoint review
Runtime URLs, health checks, sample inputs, response shape, failure modes, and rate-limit behavior must match the manifest.
Verification states
Draft, Submitted, In review, Verified, Restricted, Rejected, and Preview states are shown honestly so buyers understand adoption risk.
How publishers fix issues
Publishers should submit a new version or revise draft metadata rather than mutating verified behavior in place.