# Agent Skills

> Install OTF as an Agent Skill — drive the SDK and kits from Claude Code, Cursor, Codex, Eve, and 70+ agents with one command.

OTF ships as installable **[Agent Skills](https://www.skills.sh/otf-kit/skills)** — an open format (originally
from Anthropic) for giving a coding agent specialized knowledge it loads *on demand*. Instead of
pasting context every time, your agent reads only a skill's name + description until a task
matches, then pulls in the full instructions. The same skill works across **Claude Code, Cursor,
Codex, Windsurf, Gemini CLI, Goose, Vercel Eve, and 70+ skills-compatible agents**.

## Install the SDK skills

The free, MIT SDK ships four self-contained skills. Install all of them with one command:

```bash
npx skills add otf-kit/skills
```

| Skill | What it teaches your agent |
| --- | --- |
| **otf-cross-platform-ui** | One component API for web + native; which package to import |
| **otf-ui** | Build web UI with `@otfdashkit/ui` (React · Radix · Tailwind v4) |
| **otf-ui-native** | Build native iOS/Android/web UI with `@otfdashkit/ui-native` (Expo) |
| **otf-tokens** | Theme any app with `@otfdashkit/tokens` — same palette on web + native |

Source: [github.com/otf-kit/skills](https://github.com/otf-kit/skills). Want just one?
`npx skills add otf-kit/skills --skill otf-ui`.

## Where skills install

The `skills` CLI drops each skill into your agent's skills directory. It auto-detects the
agents you have, or you can target them:

| Agent | Skills directory |
| --- | --- |
| **Claude Code** | `.claude/skills/` |
| **Cursor** | `.cursor/skills/` |
| **Vercel Eve** | `agent/skills/` |
| **Others** | `.agents/skills/` (universal) |

```bash
# install to a specific agent
npx skills add otf-kit/skills -a claude-code

# or list what's in the repo first
npx skills add otf-kit/skills --list
```

## Every kit ships its own skill

Each OTF kit includes a skill that captures *that kit's* conventions and tested recipes — at
`skills/otf-<kit>/SKILL.md`. When you open a kit you bought, drop its skill into your agent's
skills directory and the agent immediately knows the stack, the file map, and the exact
procedure for common changes (add a screen, add an entity, change the theme, deploy). The skill
routes to the recipes already in the kit's `ai/prompts/`, so there's a single source of truth —
nothing to keep in sync.

## How this relates to `CLAUDE.md` / `.cursorrules`

They're complementary:

- **`CLAUDE.md` / `.cursorrules` / `AGENTS.md`** (see [AI tool integration](/docs/ai-tools/overview))
  are *project-level* context — auto-loaded for whatever repo you're in.
- **Agent Skills** are *portable* and *on-demand* — install them once and carry the OTF know-how
  into any project and any skills-compatible agent, with the agent loading only what a task needs.

Use both: the kit's `CLAUDE.md` grounds the agent in your repo; the skills make OTF's component
and theming knowledge available everywhere.

## Links

- **Install + leaderboard:** [skills.sh/otf-kit/skills](https://www.skills.sh/otf-kit/skills)
- **Source (MIT):** [github.com/otf-kit/skills](https://github.com/otf-kit/skills)
- **The SDK:** [github.com/otf-kit/sdk](https://github.com/otf-kit/sdk) · live [components](/components)
