Building Your First Capability
This is the fastest path from zero to a working custom capability. By the end you'll have a SKILL.md file on disk that Exponential resolves automatically whenever an agent's plan needs it.
For the full picture on resolution, frontmatter, and writing style, see Managing Capabilities and the Capability File Format reference.
Step 1 — Open the Create Capability flow
From the Capabilities page in the sidebar, click Create Capability.
You'll see a two-tab header:
- Create — the AI wizard. Describe the capability in plain language and the system drafts the full
SKILL.mdfor you. - Configure — the manual form. Fill in name, steps, rules, and examples yourself.
If this is your first capability, start in Create. The wizard is built for exactly this — going from "I keep doing X by hand" to a ready draft in a few messages.
Step 2 — Describe the skill you want to reuse
The best first capability comes from a workflow you've already done two or three times manually. Some good seeds:
"Generate a release-notes markdown file from the last N commits, grouped by feature/fix/chore."
"Take a Figma export and produce a TailwindCSS component with proper a11y attributes."
"Review a SQL migration for unsafe operations on large tables and suggest safer alternatives."
The wizard replies with a draft and shows it in the live preview on the right. Iterate by adding constraints:
- Missing a step? "Also verify the output opens in the browser before returning."
- Too generic? "Assume the project uses Prisma — reference
schema.prismaspecifically." - Need rules? "Never modify existing migration files."
When the preview looks right, click Apply to drop the draft into the form.
Step 3 — Review the form (optional but recommended)
Switching to Configure shows the same draft as an editable form. The key sections to glance over:
- Name and description — these show up wherever the capability is resolved (cards, picker, plan preview).
- Tools — which built-in tools the capability needs.
bash,read,write,edit,glob,grep. Pick only what's needed. - Tags — lowercase kebab-case. These help discovery later.
- Body — the
## Steps,## Rules,## Examplesmarkdown that teaches the agent how to execute. Specificity wins here. "Runnpx prisma migrate dev --name <description>" beats "Run the migration tool."
You can switch back to the wizard at any point and ask for more changes.
Step 4 — Save
Click Save. Exponential writes a SKILL.md file to:
| Location | Scope |
|---|---|
~/.claude/skills/your-capability/SKILL.md | Available in all spaces |
your-project/.claude/skills/your-capability/SKILL.md | Available only in that project's space |
The filename on disk stays SKILL.md for runtime compatibility — Exponential surfaces it as a capability in the UI.
The capability shows up in the Capabilities grid immediately, and is available to every agent in scope.
Step 5 — Test resolution
Create a task whose plan would naturally call for your capability ("draft release notes for the last 20 commits" if you built the release-notes capability) and watch the plan preview. You should see a Resolved Capabilities card listing your new capability next to whatever else was detected.
If it doesn't get picked up:
- Open the capability and check that the
descriptionactually mentions the use case. - Tighten the
tags— discoverability depends on the right keywords being present. - Read Managing Capabilities → resolution for the full resolution flow.
Where to go next
- Managing Capabilities — full guide on resolution, community installs, and writing style
- Capability File Format — the complete
SKILL.mdspecification - Building Your First Agent — create a custom agent to pair with your capability
- Capabilities concept — mental model and three-tier trust hierarchy