---
name: self-equip
description: Add a new skill to yourself (or another coding agent) so a capability persists across sessions. Use when the user says "remember this as a skill", "make this reusable", "teach yourself to…", or asks to install a capability into Claude Code, Codex, Cursor, Gemini, opencode, or Amp.
---

# Add a skill to yourself

A skill is a folder `<name>/SKILL.md` with `name` + `description` frontmatter and a Markdown body.
You add one by writing that folder into your provider's skills directory; next session it is
available — auto-invoked when a request matches the description, or run as `/<name>`.

## Steps

1. Detect your provider by its home marker: `~/.claude` → Claude Code · `~/.codex` → Codex ·
   `~/.cursor` → Cursor · `~/.gemini` → Gemini · `~/.config/opencode` → opencode · `~/.config/amp` → Amp.
2. Write `<name>/SKILL.md` to that provider's skills directory (below). Project scope = under the
   repo; global scope = under `~`.
3. Give it a sharp one-line `description` — that string is the auto-invocation trigger.
4. Confirm by listing the directory. It loads next session.

## Where a skill goes, per provider

- Claude Code: `.claude/skills/<name>/` (project) · `~/.claude/skills/<name>/` (global)
- Codex: `.agents/skills/<name>/` · `~/.agents/skills/<name>/`
- Amp: `.agents/skills/<name>/` · `~/.config/agents/skills/<name>/`
- opencode: `.opencode/skills/<name>/` · `~/.config/opencode/skills/<name>/`
- Gemini: a slash command at `.gemini/commands/<name>.toml` (no skills dir)
- Cursor: `.cursor/rules/<name>.mdc` (passive context, not a `/name` command)

Filename casing is exact (`SKILL.md`). Keep the body short and imperative — one skill, one job.