Skip to main content
Fygment
<- Docs home

Guides

Live

Review and approve Skills

Use lifecycle states, proposal review, version decisions, and owner/admin approvals to keep install decisions clear.

Audience
Owners, admins, maintainers, and reviewers managing Skill lifecycle.
Updated
2026-05-20

Governance is the difference between a shared Skill library and a loose pile of files. Review decisions decide what can be installed and trusted.

Lifecycle states

Fygment separates draft, pending review, approved, current, deprecated, blocked, revoked, archived, and reactivated states so users can understand which version is safe to use.

Approved versions are treated as immutable. Changes should create a new version or proposal rather than editing a package in place.

Review flow

  1. 1

    Open the approval queue or Skill versions tab

    Review the source, validation status, package checksums, release notes, and visible risks.

  2. 2

    Approve, reject, or request changes

    Approving can make a version current when policy allows. Rejecting and needs-changes decisions preserve the previous current version.

  3. 3

    Use block or revoke for unsafe versions

    Blocked and revoked versions should fail closed in resolver, install, check, and update flows.

Related docs

  • Import Skills

    Import turns an existing Skill into a validated Fygment package. Start with one selected package or public source and review the validation result before broader migration.

  • Create a Skill

    The creation flow gives you a valid starting package so you can focus on useful instructions instead of hand-building manifest state.

  • CLI reference

    The CLI is the local bridge between a governed workspace and writable AI harness targets. Use it for setup, install state, update checks, readiness, and selected imports.