Skills

Skills: reusable playbooks for your AI coding agent.

A skill is a short playbook in a plain file: how you write, test, review or release. Put it in your project once and your AI coding agent follows it whenever the work calls for it, so you stop repeating yourself in every chat.

How skills work

Loaded when relevant, never all at once.

Described in one line

Each skill starts with a name and a short description. The agent reads those first, which keeps its context small.

Opened on demand

When the task matches a description, the agent opens the full playbook and follows it. You see the skill load in the chat.

Shared with specialists

When work is handed to the designer or the engineer, the skills it needs go with it, so the whole team follows the same rules.

The file format

A SKILL.md is just a Markdown file.

Keep skills in .revampkey/skills or .agents/skills. Each skill is a folder with a SKILL.md at its root, a name and description at the top, and plain instructions below.

.revampkey/skills/booking-conventions/SKILL.md
---
name: booking-conventions
description: How we store times, hold slots and write
  booking tests. Use when changing anything in bookings.
---

# Booking conventions

- Store every time in UTC with the client's time zone.
- A held slot expires after 5 minutes.
- A reschedule moves a booking; it never creates a second one.
- Every booking change needs a test for the double-booking case.

Because it is a plain file in your repository, a skill is reviewed, versioned and shared like any other code. Skills written for another coding agent in the same format work once they are in your skills folder.

Starter ideas

Three skills worth writing first.

How we test

Which command runs the checks, what must pass before a commit, and which cases always need a test.

How we write

Naming, folder layout and the patterns your team prefers, so new code looks like the old code.

How we release

Branch and commit conventions, the changelog format and the steps before shipping.

Skills pair well with scheduled runs and the specialist AI coding agents: the same playbook applies wherever the work happens.

Questions

Skills for AI coding agents, answered.

What is a skill?

A short playbook in a plain file that tells the AI coding agent how your team does one thing, such as writing tests, reviewing changes or cutting a release. It is loaded only when the work matches.

Where do skill files go?

In .revampkey/skills or .agents/skills inside your project. Each skill is a folder with a SKILL.md file, so you can review and version it like code.

What does a SKILL.md file look like?

It starts with a name and a one-line description, followed by the instructions in plain Markdown. The agent reads the description first and opens the full file only when the task fits.

Can I use skills written for another coding agent?

Skills use the common SKILL.md format, a name and a description at the top, so a skill written for another coding agent works once it is in your skills folder.

Do the specialist agents get my skills?

Yes. When work is handed to a specialist such as the designer or engineer, the skills it needs go with it. The chat shows each skill as it loads.

Keep exploring

How it works

Follow one idea through the researcher, product manager, designer, engineer and QA.

See the whole loop →

Plans and reports

Reports you can sort and question, and plans split into reviewable steps.

Explore plans and reports →

Schedules

Ask for a follow-up in plain words or cron and it comes back on its own.

See schedules →
Start

Start with one idea.

Describe something you have been putting off. Read the plan, approve the screens, and decide whether to let it build.

macOS 12+ · Windows 10+ · Ubuntu 20.04+  ·  See what shipped in 2.8.0