# Create Skill

How to create new skills for an agent-native app.

- Repository: https://github.com/BuilderIO/agent-native (7579 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add BuilderIO/agent-native --skill create-skill -g -a claude-code -y`
Codex: `npx skills add BuilderIO/agent-native --skill create-skill -g -a codex -y`
Cursor: `npx skills add BuilderIO/agent-native --skill create-skill -g -a cursor -y`
Gemini CLI: `npx skills add BuilderIO/agent-native --skill create-skill -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add BuilderIO/agent-native`

## Description

How to create new skills for an agent-native app. Use when adding a new skill, documenting a pattern the agent should follow, or creating reusable guidance for the agent.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Create a Skill

## When to Use

Create a new skill when:

- There's a pattern the agent should follow repeatedly.
- A multi-step workflow needs reliable, step-by-step guidance.
- You want to scaffold files from a template.

Don't create a skill when:

- The guidance already exists in another skill, extend it instead.
- You're documenting something the agent already knows (e.g., how to write
  TypeScript).
- It's a one-off, put it in `AGENTS.md` (for everyone) or `memory/MEMORY.md`
  (personal, per-user). See **capture-learnings**.

## Interview

Before writing the skill, answer these:

1. **What should this skill enable?**, The core purpose in one sentence.
2. **Which of the four areas does it serve?**, UI, actions, skills/instructions,
   or application state (see the **adding-a-feature** skill). Most skills are
   about how to touch one or more of these correctly.
3. **When should it trigger?**, Describe the situations in natural language.
4. **Does it involve context awareness?**, Does the agent need to know what the
   user is looking at? If so, reference the `navigation` application-state key and
   the `view-screen` action pattern. See the **context-awareness** skill.
5. **What type of skill?**, Pattern, Workflow, or Generator (see below).
6. **Does it need supporting files?**, References (read-only context) or none.
   Keep it minimal; push depth into `references/`.

## Skill Types and Templates

### Pattern (architectural rule)

For documenting how things should be done:

```markdown
---
name: my-pattern
description: >-
  [Under 40 words. What it covers AND when it should trigger.]
---

# [Pattern Name]

## Rule

[One sentence: what must be true]

## Why

[Why this rule exists]

## How

[How to follow it, with code examples]

## Don't

[Common violations]

## Related Skills

[Which skills compose with this one]
```

### Workflow (step-by-step)

For multi-step implementation tasks:

The rest: https://github.com/BuilderIO/agent-native/blob/HEAD/.agents/skills/create-skill/SKILL.md