Approve / publish a version

How a new skill version becomes what agents actually run.

Project skills — approve

1. Author creates or edits a draft (or addresses changes_requested).
2. Author submits → status under_review (scan gate may apply).
3. Reviewer opens the review board / version detail, reads the diff, checks scan findings.
4. Reviewer approves → version becomes active (previous active may move to deprecated depending on product rules), or requests changes.

After approval, consumers run:

pm-skills status    # may show "update available" or "new in resolution"
pm-skills update    # or pull, depending on lockfile state

Organization / global — publish

Org and marketplace skills use publish: scan-gated promotion to active without the project review board. Marketplace publish is stricter on overrides.

Rollback

Activate a previous approved version from the version history (or pin an older SHA via install management / pm-skills update --to <sha> when updating local pins). Prefer governance in the UI over editing files on disk.

Related concepts

Lifecycle · Security scanning