create-playbook

A guided skill for creating a new coding skill or playbook, meaning a reusable set of instructions for a particular job. It gathers requirements and chooses a template based on the work's complexity.

In plain words
What is it for?
Use it to define a skill's name and purpose, check for similar skills, and generate an appropriate starting template.
Why use it?
It removes the guesswork from structuring a new skill and helps avoid creating one that duplicates an existing skill.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/abilityai/abilities/create-playbook
Any agent
npx skills add Abilityai/abilities --skill create-playbook
Clone the repo
git clone --depth 1 https://github.com/Abilityai/abilities

Made for: Claude Code, Codex.

Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 8,689 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00025 $0.08689
Opus 5 $0.00013 $0.04345
Sonnet 5 $0.00005 $0.01738
Haiku 4.5 $0.00003 $0.00869

Measured 2d ago against content hash 062c180fc8e9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

create-playbook scanned grade B with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Enumerates other installed skillsmediumAgent snooping

Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.

ls -d .claude/skills/*/ 2>/dev/null | head -10
plugins/agent-dev/skills/create-playbook/SKILL.md · 448 lines

How it starts

The opening of the file, as written. The whole thing — 448 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create Playbook

ℹ️ First, set expectations: before anything else, print one short line with this skill's version and its most recent change — the top entry of metadata.changelog above — e.g. create-playbook vX.Y — recent: <summary>. Then proceed.

Create a new skill. Determines the right complexity tier and generates from the appropriate template.

For concepts and patterns, see the README. Tier templates are bundled with this skill in templates/ — reference them at runtime via ${CLAUDE_SKILL_DIR}/templates/.


Workflow

Step 1: Check for Existing Skills

ls -d .claude/skills/*/ 2>/dev/null | head -10
ls -d ~/.claude/skills/*/ 2>/dev/null | head -10

If similar skill exists, ask: update it, create variant, or proceed with new?

Step 2: Gather Core Requirements

Ask or extract from context:

  1. Name: lowercase-with-hyphens, descriptive. For project/personal skills the directory name is the command (name: is display-only); for plugin skills name: sets the command segment — keep name and directory identical so they never drift.
  2. Purpose → the description: field: third person, what it does + when to use it, key use case first — the skill listing truncates description + when_to_use at 1,536 characters.
  3. Tools needed: Which tools will it use?

Step 3: Determine Complexity Tier

Ask these questions to classify:

Q1: Does this skill read or write any files, APIs, or external state?

  • NO → Tier 1: Simple Skill (skip to Step 4)
  • YES → Continue to Q2

Q2: Will this run unattended, on a schedule, or need reliability guarantees?

  • NO → Tier 2: Stateful Skill (skip to Step 4)
  • YES → Continue to Q3

Q3: What automation level?

  • Safe to run completely unattended, no approval needed at any pointautonomous
  • Needs human approval at checkpoints → gated
  • Human monitors entire execution → manual

⚠️ Critical: If user says "autonomous" but also mentions approval/review steps, clarify:

"Autonomous playbooks cannot have approval gates — they run unattended and would hang waiting for approval that never comes. Should this be gated instead?"

Read the full file on GitHub · 448 lines

Files

What ships with it

5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 448 lines · 25 tokens per session scan B 062c180fc8e9

Subscribe to this mod's changes

create-playbook is a skill published in the GitHub repository Abilityai/abilities (11 stars, last pushed 14d ago), licensed MIT. It adds 25 tokens to every session and 8,689 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens