Skip to main content
A skill is a set of instructions the agent loads when a request fits: a release checklist, how your team writes emails, how to handle PDFs. Each skill is a folder with a SKILL.md file, and every skill you add reaches all of your sessions from their next message. For the skills Alpha already includes, see Skills that ship with Alpha. To give the agent new tools rather than new know-how, add an MCP server.
The Skills page, with Skills in its top bar. A cover image of a dusk sky over clouds, with a ladder rising to a small round moon, carries the title Skills and the lede Your sessions have 9 skills. Below the cover are the tabs Explore (selected) and Installed, a search box with the placeholder Search skills — PDF, CI, security, design…, an Import from GitHub button and a white Write a skill button with a plus icon. The Catalog shelf follows, with a Most popular order menu on its right. Its cards sit two across, each with a tinted icon of geometric shapes. Design Taste Frontend shows its directory name design-taste-frontend, the line tasteskill v2, the anti-slop frontend skill. Art…, the source written by the agent in a session with 1+ installs, and an Install button. Algorithmic Art reads Generative art with code, then Creating algorithmic and generative art — p5.js sketches, seeded randomness, composition — as code, with the GitHub mark, anthropics/skills and an Install button in its footer. Canvas Design (Posters, covers and visual pieces on a canvas) and Doc Co-authoring (Co-write documents with the user) start the next row.

Explore opens first, on the catalog of skills you can install.

​
How should you add a skill?

There are four ways in. Whichever you pick, the skill is yours: it reaches your sessions only, never another account’s.
Not sure? Do the work once in a session, then ask the agent to make it a skill. It writes the instructions from what actually worked.

​
Install a skill from the catalog

Click Skills in the sidebar. The row’s badge counts the skills your sessions have. The page opens on Explore, where the Catalog shelf lists public skills from GitHub. Type in the search box to filter by name, description or keyword, and use the order menu to sort. Each skill’s icon is a pattern of four shapes that is its own, on a tile tinted by category: sky for Engineering, violet for Workflow & GitHub, emerald for Documents & files and rose for Design & visuals. Skills that ship with Alpha take their category’s colour too. Skills an admin shared are orange, and your own skills that didn’t come from the catalog are amber. The footer links to the skill’s source on GitHub and shows an install count such as “12+ installs”. Click Install. Alpha fetches the skill’s folder from GitHub, the button becomes a green check with Installed, and a banner confirms: “pdf installed — your sessions have it from their next message.” The skill appears under Your skills. The Installed tab lists those alone, as full-width rows with their size and file count.
The Skills page with the Installed tab selected, under the cover reading Skills and Your sessions have 9 skills. The search box, Import from GitHub and Write a skill stay beside the tabs. The Your skills shelf reads 9 on, 0 off at its right. Full-width rows follow, each with an icon, a display name in bold, the directory name in monospace, a one-line description and a source line with the file count and size. Agent builder (agent-builder) reads ships with Alpha, 8 files, 63 KB, and Design system (design-system) reads ships with Alpha, 9 files, 55 KB; both end in 1d ago, a switch turned on and a chevron. Design To Motion (design-to-motion) reads written by the agent in “AI Design Skills”, 1 file, 47 KB, and ends in 16h ago, a switch turned on, a chevron and a trash icon.

Installed lists every skill you have, with where it came from and a switch on each row.

​
Add your own skill

Click Write a skill or Import from GitHub. Both open the Add a skill dialog, and its toggle switches between Write it here and Import from GitHub.
1

Name it

Name is what calls the skill: $name in Codex, /name in Claude Code. Use letters, digits, - and _, up to 64 characters and starting with a letter or digit, such as booking-emails.
2

Say when to use it

When to use it is the description the agent reads to decide whether the skill fits. Be concrete about the trigger: “Use when writing or changing the emails Harbor sends to students.”
3

Write the instructions

Instructions (SKILL.md) opens with a short template. Replace it with the steps, conventions and things to avoid. To keep a SKILL.md you already have, paste the whole file, frontmatter included, and Alpha keeps that frontmatter instead of the two fields above.
The Add a skill dialog, with a back arrow beside the title and a close button at the right. The description reads: A skill is a SKILL.md — a name, a one-line description of when to use it, then the instructions — with any reference files beside it. Write one here, or import a directory from GitHub. It's yours: your sessions get it, nobody else's. The toggle shows Write it here selected, beside Import from GitHub. The empty Name field shows the placeholder release-checklist in monospace, with the hint What calls it — $name in codex, /name in Claude Code: letters, digits, - and _. When to use it shows the placeholder Use when cutting a release: version bump, changelog, tag, with the hint The description the agent reads to decide — be concrete about the trigger. The Instructions (SKILL.md) box holds a template: the heading What this skill is for, a line asking you to explain when the agent should reach for the skill and what good output looks like, a Steps heading with two numbered placeholders, and a Notes heading with Conventions, commands, files to look at, things to avoid. The footer shows Cancel and a dimmed Add to your skills with a check icon.

Each field starts empty, and Instructions (SKILL.md) opens on a template to replace.

4

Click Add to your skills

Leave Let the agent use it on its own on so the agent picks the skill up whenever the task fits. Turn it off to run the skill only when a message mentions it.
The saved file looks like this:

​
Turn session work into a skill

Ask for it in plain words, in any session. The agent writes the skill into its own skills folder, with a SKILL.md and any scripts beside it. When the turn ends, Alpha installs it as your skill. Alpha will:
  1. Have the agent write release-steps from the commands this session ran.
  2. Install it under your skills when the turn ends.
  3. Add a line to the transcript, and give every session the skill from its next message.
On the Skills page its source reads “written by the agent in “Harbor bookings””, and in its dialog that line links back to the session. It stays in step with that session: when the agent changes the skill there, your copy follows at the end of that turn. If the transcript instead says “The skill $release-steps in this sandbox was not published”, the reason follows it, usually a name that’s already taken.

​
Switch, edit and mention a skill

A row’s switch takes the skill in or out of your sessions. Click elsewhere on the row to open its dialog. To use a skill on purpose, mention it in the composer. In a Codex session, type $ and pick from the list. In a Claude Code session, skills appear under / with the other commands. Type /skills in any session to see what the agent can use there.
Removing a skill you wrote here deletes its only copy, and it can’t be undone. Switch it off instead if you might want it back. A skill imported from GitHub can be imported again.

​
Who can change a shared skill?

Alpha’s own skills, such as Design system and Slides, read ships with Alpha and are on for everyone. An admin can share one of their own skills the same way, or put it in the catalog under From Alpha for each account to install. Your switch on a shared skill is yours alone. Turning it off takes the skill out of your sessions, and other accounts keep theirs. If you have a skill of your own with the same name, the shared one shows yours instead and your version is the one your sessions get. Admins only Only an admin edits a shared skill. Everyone else sees its SKILL.md as read-only. Alpha’s own skills are read-only for admins too. An admin shares or takes back a skill from the ⋯ menu in its dialog, and each action asks first: Alpha’s own skills can never be removed. A skill an admin shipped can be removed only once an admin switches off Ships with Alpha in its dialog, which moves it to the catalog. See the Admin dashboard for who counts as an admin.

​
Fix a skill that won’t add or save

These limits are fixed, so no setting changes them.

​
Next steps

Skills that ship with Alpha

Seven skills every session starts with, from slides to voice agents, and what to ask for.

MCP servers

Give the agent new tools. Figma and Linear skills work best paired with their servers.

Prompt Alpha well

Mention a skill with $name to make sure a prompt follows it.

Connect GitHub

Needed before you import a skill from a private repository.