NewFree guided workflows for designers, PMs and developers
How to install

AI skillsinstall, use and create

What skills are, how to install one in Claude, ChatGPT, Gemini or a coding agent, and how to write your own. Skills follow an open standard (SKILL.md), so one skill works in all of them.

01What skills are

Know-howyou install once

A skill is a folder with instructions, and sometimes scripts or templates, that teaches your AI tool how to do one kind of task well: build a deck in your house style, write a PRD, review an interface for accessibility.

You install it once and the agent uses it whenever a task calls for it, so you stop pasting the same prompt. Installing many skills is fine: the agent only reads each skill's short description up front and loads the rest when it's needed, so ten skills don't slow your chats down.

02Install a skill

How to install a skillwherever you work

Pick where you use AI. Every skill page on SkillHub has the same choice, with a download or the install command, and links to its source.

Use it in

In Claude

The Claude app on the web or desktop. No terminal, works on every plan.

  1. 01

    Turn on file creation

    Settings → Capabilities, switch on Create and edit files (code execution). Skills need it to run.

  2. 02

    Get the skill as a .zip

    On the skill page, choose Use it in: Claude and download the .zip. No download button? Open the source on GitHub, download the folder with SKILL.md in it and zip it.

  3. 03

    Upload it

    Customize → Skills → + → Create skill → Upload a skill. Pick the .zip as it is; the skill shows up in your list, switched on.

Then just ask
There's nothing to call. Describe the task (“turn these notes into a 10-slide deck”) and your AI tool picks the matching skill. If it doesn't, name the skill in your message.
Install from sources you trust
A skill can include scripts that your AI tool runs. Skim the SKILL.md and any scripts before you install, as you would with any code from the internet.
04Create your own

Write a skillin plain Markdown

No programming needed. If you keep explaining the same process to your AI tool, that process is a skill. The minimum is one folder with a SKILL.md file.

Folder
your-skill/
├── SKILL.md       # required
├── reference.md   # optional
└── scripts/       # optional
    └── check.py
SKILL.md
---
name: your-skill
description: What it does and
  when to use it.
---

# Your skill

Steps, rules and examples.
See reference.md for details.
name
Up to 64 characters: lowercase letters, numbers and hyphens, like reviewing-prds. Match the folder name, or the upload fails.
description
Up to 1,024 characters. Say what it does and when to use it: it's the only part the agent reads before deciding to load the skill.

How an agent loads a skill

In three layers, so a long skill costs nothing until it's used.

  1. 01

    Name and description, always

    About 100 tokens per skill. Enough for the agent to decide whether the skill fits the task.

  2. 02

    SKILL.md body, when the skill fits

    The steps, rules and examples, read once the task matches the description.

  3. 03

    Other files, only when needed

    Reference docs, scripts and templates cost nothing until the agent opens them.

Tips for a skill that works

Write the description for the trigger
A vague description means the skill never loads. Name the task and the moment: “Review a PRD for missing goals, metrics and edge cases. Use when someone shares a PRD or spec.” Not: “Helps with documents.”
Keep it short
Stay under 500 lines in SKILL.md and only add what the agent can’t know: your process, your standards, your examples. Move long reference material to separate files.
Strict where it matters, loose where it doesn’t
Give room for creative work and analysis. Spell out exact steps (or a script) for anything that breaks easily, like migrations or file formats.
Test it on a real task
Try it in a fresh chat, on each model you use; smaller models need more explicit steps. Did the skill load? Did the agent follow it? Adjust, then share it.

Made something others can use? Put it on GitHub and submit it to SkillHub.

05Skills vs MCP

A skill teaches howa connector gives access

They work best together: the Figma connector lets your AI tool read your file, a design-review skill tells it what to look for. Setting up a connector? See the connectors guide.

Skills
Know-how: steps, standards and scripts your AI tool loads when a task needs them.Use it for: work you repeat, done your way
Kits
The skills for one domain, in install order.Use it for: starting without twenty installs
Workflows
One job in steps, with the right skill for each step. A guided workflow is one skill that leads you through the job.Use it for: getting a job done, not just installed
Connectors (MCP)
Access to another app or live data: Figma, GitHub, Notion, a database.Use it for: reading from and acting in your tools
Plugins
A bundle of skills, connectors and commands you install in one go.Use it for: a complete setup for a team or role
Projects
Shared files and instructions for one body of work.Use it for: context that stays with one project
Prompts
Instructions for a single chat.Use it for: one-off requests

Find your first skill

Start with the kit for your role, or browse the whole catalog.