Skip to main content
Fygment
Get started
<- Docs home

Guides

Create a Skill

Start a new Skill from one of six starter templates, fill in a short form, then write the instructions in the SKILL.md editor.

Audience
Anyone who wants to write a new Skill for themselves or their team.
Updated
2026-10-25

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.

Create from a template

  1. 1

    Choose a starter

    Pick one of six templates: Code Review Partner, Product Planning Partner, Debugging Partner, Documentation Partner, Research Partner, or Deployment Prep Partner. Each one fills in the form for you.

  2. 2

    Fill in the form

    Enter a name, slug, and description. Then choose the source, visibility, risk level, category, and tags. The slug is the Skill’s permanent handle for installs and updates, so pick one that will last.

  3. 3

    Create the Skill

    Fygment builds the package and saves the first version as the approved, current version. The new Skill starts with the Draft label. It can be installed once it is shared with a team or published to the workspace.

  4. 4

    Write the instructions

    Open the Skill and use the Edit SKILL.md tab to write the instructions. Each save creates a new version that waits for review. The current version stays in use until the new one is approved.

Who can see a new Skill

Personal visibility means only you can see and use the Skill. Every plan can create personal Skills.

Team and workspace visibility need the Team plan. Only workspace owners and admins can create a Skill that the whole workspace can see. Your workspace policy decides who can create team Skills.

Members who want to share a personal Skill more widely send a request to the Approval Queue.

Related docs

  • 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.

  • Review and approve Skills

    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.

  • 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.

  • Security and privacy boundaries

    The Fygment trust model is metadata-minimizing: keep customer Skill content, package bodies, prompts, secrets, tokens, and raw local paths out of admin, support, analytics, and billing surfaces.