- Accordion
- Attachment
- Avatar
- Badge
- Breadcrumb
- Button
- Button Group
- Card
- Checkbox
- Code Block
- Collapsible
- Dialog
- Dropdown Menu
- Empty
- Field
- Hover Card
- Input
- Input Group
- Input OTP
- Item
- Label
- Marker
- Message
- Number Flow
- Pagination
- Popover
- Progress
- Radio Group
- Select
- Slider
- Sonner
- Spinner
- Switch
- Tooltip
- Separator
- Sheet
- Tabs
- Textarea
- Toggle
- Toggle Group
- Trace
Skills
Portable, machine-readable instructions that teach AI agents how to work with the Frakment registry.
A skill is a SKILL.md file that teaches an agent one focused capability.
Frakment ships skills that let any agent discover, fetch, and install
components without guessing.
Frakment publishes skills that follow the Agent Skills protocol. Each skill is self-contained, versioned in the repo, and served at a stable URL so agents can load it on demand.
Why skills?
Agents that rely only on tools are blind to context. Skills fill the gap: they describe when to act, not just what to call.
Available skills
| Skill | Purpose |
|---|---|
frakment-usage | Discover, fetch, search, and install Frakment components |
How agents load skills
Discover the available skills
curl https://frakment.vercel.app/.well-known/agent-skills/index.jsonFetch the skill markdown
curl https://frakment.vercel.app/.well-known/agent-skills/site-skill.mdLoad into context
Feed the markdown into the system prompt or tool context. The frontmatter description is what triggered the load; the body is what the agent follows.
Where skills live
Anatomy of a skill
Every skill is a single SKILL.md file: YAML frontmatter at the top, markdown
body below.
name: frakment-usage
description: Load when an agent needs to discover, fetch, or install Frakment components.
allowed-tools: ["fetch", "bash"]
version: 0.1.0| Prop | Type | Default | Description |
|---|---|---|---|
name* | string | — | Stable slug. Must match the folder name. |
description* | string | — | One sentence telling the agent when to load this skill. |
allowed-tools | string[] | — | Optional hint about which tools the skill expects. |
version | string | — | Semver for the skill body. |
Authoring a skill
Create the folder and SKILL.md
Register it in frakment.json
{
"skills": [
{
"name": "my-skill",
"source": "skills/my-skill/SKILL.md",
"version": "0.1.0"
}
]
}Build and publish
$ bun registry:build$ npm run registry:build$ pnpm registry:build$ yarn registry:build
FAQ
A skill is documentation: prose that tells an agent how to act. An MCP tool is executable: a function the agent can call. Skills describe intent, MCP tools perform actions.
No. Frakment publishes skills at /.well-known/agent-skills/index.json and /skills/<name>/SKILL.md. Point your agent there.
An emerging convention for exposing SKILL.md files at predictable URLs so
agents can discover and load them at runtime. Frakment follows the
schemas.agentskills.io discovery schema.