Creator entry

Upload a resource

Create a resource draft first. Manifest metadata, package integrity, scan evidence, publisher and capability readback, and publish review happen in the next steps.

Sign in before creating a draft.

Draft ownership is bound to your account and cannot be supplied from the browser.

Submission requirements

Describe what the agent does and who it helps.
Declare runtime, model, framework, tool, capability, and environment compatibility.
Attach a manifest with package metadata, integrity hashes, capabilities, and required environment variable names only.
Use bundles for related resources; bundle import steps must stay metadata-only.
Keep credentials, tokens, local paths, private files, executable commands, lifecycle hooks, and custom workflow code out of submissions.
Skill packages require exact SKILL.md casing, safe frontmatter, supporting-file hashes, and passed scan evidence.
Workflow templates are sanitized before readback; protected fields and executable nodes are stripped or marked for review.
Published resources remain free for public browsing and download.