ITU

KnowledgebaseFor providersThe review process

The review process

Every submitted skill source is reviewed by a human before its skills can be published, with each skill’s automated check report as evidence alongside it. AI output stays a hypothesis until validated - the review is where the marketplace validates it.

The queue

The queue lists source submissions: one row per publish action, however many skills the source carries. A reviewer claims a submission to work on it (its status becomes in_review); only the claiming reviewer - or a super admin - can decide it, and the decision covers every skill in the submission.

What the reviewer sees

  • The source’s verified repository metadata, snapshotted at submission: pinned deep link, stars, forks, licence, last push.
  • Every skill in the submission, exactly as it was pinned at submission time. Each skill opens on its own with its full bundle - SKILL.md, specs, schemas, rulebooks.
  • Each skill’s automated check report, including warnings, plus a source-wide summary.

Decisions

A decision applies to the submission as a whole - every skill in it, all or nothing.

DecisionEffect
ApproveEvery version in the submission is published. Previously published versions of the same skills are superseded, and an archived source returns to the catalog.
Request changesEvery version becomes changes_requested with the reviewer’s notes; the provider fixes the repository and resubmits the source.
RejectEvery version is rejected with notes; nothing is published.

The public review trail

Every published skill exposes its assurance history at /marketplace/<provider>/<source>/<skill>/review: the check results and the approval audit. Trust in the catalog is inspectable, not asserted.

After publication

The owning provider - or a super admin - can archive a whole source in one action: the source record and every published skill it carries leave the catalog together, and any submission of the source still waiting in this queue is withdrawn. History is not rewritten (the review trail stays public). Resubmitting the source relists it through a fresh review. See Roles and statuses.