Who can create and share
Decide who may create or import skills, and how widely each person can share them.
| Can share with | Self | Team | Company |
|---|---|---|---|
| Members | |||
| Team leads | |||
| Admins |
Bring your skills together, keep track of every version, and use them in the AI tools you already work with.
External skills get a security check with SkillSpector.
Examples use a fictional team and skills.
Security analysis with SkillSpector
Set each rule for the whole company, a team or a single skill.
Decide who may create or import skills, and how widely each person can share them.
| Can share with | Self | Team | Company |
|---|---|---|---|
| Members | |||
| Team leads | |||
| Admins |
Allow only the sources you trust, for example your company GitHub and never public sources.
Choose the AI tools that may receive your skills, for example Claude and Copilot but not personal accounts.
Choose what must be reviewed before anyone can use it, and who gives the approval.
Offer the latest reviewed version or pin one, decide how strongly updates are pushed, and roll out to one team first.
Give each skill a risk level. The riskier it is, the more often its owner reviews it again.
Start with a local skill inventory for free. Upgrade when imports, AI review, team governance and enterprise controls become part of how you work.
For one person
Freeforever
A simple local setup before you bring in external sources or team workflows.
For teams and AI imports
$14per seat per month
AI-assisted skill intake, a private registry and governed rollout for your team.
For regulated and large organisations
Custom
Identity, deployment, compliance and audit depth for organisations with strict requirements.
Create a workspace, connect the AI tool you already use, and put a skill to work.
Prefer the terminal? npx fygmentCLI docs