Publisher workflow

Register a skill package for review.

Submit a skillhub.json contract, run preflight checks, and send an exact version into verified review. Paid marketplace fields are collected only as prelaunch readiness metadata.

skillhub.json

DraftOrg-scoped

ReviewAutomated gates

RuntimePolicy evidence

PaidReadiness metadata

Publisher review and readiness journey

The publisher path proves authors have repeat work: draft packaging, exact-version review, repair, pricing intent, feedback, buyer demand, and paid-readiness metadata.

CurrentPublish entryNextPublisher workspace

Publish entryPaste a manifest, run preflight, save an organization-scoped draft.
Publisher workspaceOperate owned skills, versions, buyer demand, notifications, and paid-preview readiness signals.
Review repairUse reviewer notes, SLA, automated evidence, target fields, and next actions.
Paid-readiness metadataComplete profile, terms, paid-readiness metadata, verified review, and pricing intent.
Improve and retainRespond to feedback, buyer requests, paid-preview signals, refund/dispute notices, and placement appeals.

Current session

Publisher workspace access

Publisher operations cover manifest drafts, version review, repair loops, pricing intent, buyer demand, feedback, paid-readiness metadata, and notifications.

Sign-in requiredSign in

OrganizationSign-in required

Current rolesSign-in required

Required rolespublisher / owner / admin / super_admin

Session sourcenone

API actions remain role-enforcedThis panel explains access before a user clicks a control. The gateway still enforces organization membership and role checks for every write.

Signed-in user session

Self-service publisher access

httpOnly

Publishing uses the httpOnly user session created by login. No raw admin, service, OAuth, webhook, or user token is collected in this form.

Signed-in user sessionPublisher, owner, admin, or super admin role required

Registry APIhttps://api.useskillhub.com

Sign-in required

Enter through username/email password, configured Google/GitHub OAuth, or an invite/recovery token first. The form stays locked so publishers do not fill a manifest only to fail at submit time.

Operating pipeline

Upload is the first control point, not the finish line.

A marketplace listing is only trusted after the contract becomes draft state, exact-version review state, automated-check evidence, and public catalog readiness.

Publisher workspace

Paste manifestStart from a skillhub.json contract with identity, runtime, permissions, schemas, examples, and support paths.

Run preflightCatch malformed JSON, missing contract fields, insecure endpoints, sparse schemas, and high-risk permissions.

Save draftCreate or update the organization-scoped draft through the signed-in SkillHub user session.

Submit versionChoose the exact semantic version that should enter human review from the publisher workspace.

Automated checksManifest, runtime, example, and security checks become reviewer and publisher evidence.

Reviewer decisionVerified listings require approved review records and acceptable automated check results.

Paid readiness metadataPaid marketplace fields remain prelaunch metadata until review, terms, commission, and finance decisions are finalized.

skillhub.json