Guides
Review and approve Skills
How sharing requests, new versions, and change proposals are reviewed in the Approval Queue, and who can approve each one.
- Audience
- Workspace owners, admins, team leads, Skill owners, and Skill managers who review Skills.
- Updated
- 2026-10-25
Members can use the Skills they import right away. Review is for sharing more widely and for new versions. Each decision is made by someone with authority over that Skill or team, and every version approval re-runs the trust review.
Lifecycle
Every Skill has one lifecycle label: Draft, Pending review, Published, Team shared, Archived, Blocked, Revoked, or Deprecated.
Published means the whole workspace can use the Skill. Team shared means one or more teams can use it. Pending review means a version or request is waiting for a decision. Blocked and Revoked mean the Skill must not be used. Deprecated means it still works but should be replaced. Archived means it has been retired.
Approved versions do not change. An edit creates a new version instead.
Who reviews what
Workspace owners and admins publish and share Skills directly, without a request. They see every request in the Approval Queue.
Members send requests to share a Skill with a team or the whole workspace. They follow their requests under My requests and cannot approve their own.
Team leads can approve a request to share a Skill with teams, but only when they lead every team in the request. They cannot approve their own request, and they cannot publish to the whole workspace unless they are also an owner or admin.
New versions of a Skill can be approved by the Skill owner, a Skill manager, or a workspace owner or admin.
Review a version
- 1
Open the Skill’s Versions tab
Check the source, validation result, checksums, release notes, and trust review findings.
- 2
Approve, reject, or ask for changes
Approving re-runs the full trust review on the stored package. If the review blocks the version, or is still running, approval is refused and you can try again later. When approval succeeds, the version becomes the current version.
- 3
Keep the previous version when you reject
Rejecting a version, or asking for changes, leaves the current version in place.
Proposals, blocks, and rollback
A proposal is a suggested change to a Skill. Reviewers approve or reject it in the Approval Queue. Approving a proposal that changes the package re-runs the trust review first.
Fygment will not hand out the package of a blocked or revoked version, so installs, checks, and updates stop instead of using it.
Workspace owners and admins can roll a Skill back to an earlier approved version from its Versions tab. The rollback is recorded in the audit log.
Related docs
- Trust review
Every Skill you import is checked by the SkillSpector trust scanner before Fygment saves it. A Skill the scanner rejects, or cannot clear, is not imported. The scanner lowers risk, but it cannot guarantee that a Skill is safe.
- Import Skills
Import turns a Skill you already have into a Fygment Skill. Each import is validated and trust reviewed. A Skill that passes is ready for you to use right away. Sharing it more widely is a separate step.
- Create a Skill
Creating a Skill gives you a valid package from the start, so you can focus on the instructions. The first version is approved and current as soon as you create it.
- Workspaces, members, and access
A workspace is the unit of trust in Fygment. Membership, role, invite, install, report, and billing behavior all resolve through that boundary.
- 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, setup checks, and selected imports.