Skills
All 34 skills, grouped the way the work is. Related work is one skill with playbooks, and you ask in plain words.
A skill is a packaged way of doing one kind of work. You rarely need its name: ask in plain words ("brief me", "set today's goals", "how's my site ranking") and the agent picks the skill and the playbook.
| To | Type |
|---|---|
| Run a skill by name | /agentlayer:<name> in Claude Code, $<name> in Codex. These docs use the bare name |
| Run one playbook | The playbook after its skill: briefing pulse, goals week, seo audit |
| See a skill's playbooks | help after its name: goals help |
How skills start:
- Three run only when you name them, because firing one unasked would cost too much:
init,releaseandrename-agent. - Every other skill may start on its own when your request clearly calls for it.
- A skill that writes still asks first. Nothing changes knowledge or task state without your confirmation, and the skills that edit code leave committing to you.
- A pack badge means the skill works once that pack is switched on through
configure-skills. Aseoplaybook whose key is missing names it and stops.
Plan and run
| Skill | Playbooks | What it's for |
|---|---|---|
attention | refresh · add · plan · organize · standup · checkpoint · checkpoint all · backfill | Your day: today cut to three, the week and month lanes, the roadmap in flight, what's waiting on you, your standup, and where every session left off. See Attention |
goals | day · week · month · year | Goals from today to the year, set by interview and written to your task hub; the day and the week get scored. See Daily rhythm |
briefing | morning · evening · pulse | The morning brief, the evening wrap, and a one-minute scan for anything on fire |
project | create · archive · handoff | Start a project with the right scaffolding, retire one cleanly, or hand a task to the team as a GitHub issue |
tax | setup · calendar · position · capture · close · estimate · accountant · optimize · year-end | Every entity's tax deadlines as dated tasks, receipts filed to a ledger, the monthly close, estimate planning. Never files, pays, or sends. See Tax and books |
roadmap | A strategic roadmap as one self-contained HTML page, its content kept as JSON attention can read | |
flywheel | A cross-project work session framed by the north-star roadmap, caught up on every session since the last one | |
adversarial-review | A second model on anything you made; the agent verifies each finding and fixes the real ones. See Second-model review | |
find-session | Find a past session by what it worked on, with its resume command | |
itinerary | Plan a trip into an interactive, print-ready HTML itinerary | |
guide | A guide someone else can follow, as one HTML page: setup steps they tick off, who does what, a process from start to finish |
Build and ship
| Skill | Playbooks | What it's for |
|---|---|---|
engineer | 21 for code (bug fix, feature, refactoring, performance, forensics, prototype, and more) · 4 for pull requests (review, replies, walkthrough, github sweep) | The method for code work, backed by 23 named principles and a comment pass before any diff. The pull-request playbooks need the GitHub pack. See Engineering |
setup-worktree | Create a sibling git worktree and bootstrap it; also the read-only worktree audit | |
plan-spec | A Socratic interview into a standalone spec, with a design section for code | |
api-collections API pack | Draft API requests as Bruno, Postman, or plain-curl collections you fire yourself | |
upgrade | Apply pending home migrations after a plugin update | |
release | Maintainer only: cut a versioned release with its Upgrade block. Runs only when named |
Reach and see
| Skill | Playbooks | What it's for |
|---|---|---|
seo SEO pack | audit · console · speed · serp · rank | How a site shows up in search, read-only: a full audit, Search Console, PageSpeed and Core Web Vitals, live Google results, domain authority. See SEO |
wordpress-rest SEO pack | WordPress posts, pages, and modified dates through the public REST API, for SEO or anything else | |
browser-flows Browser pack | Drive a visible browser through repeatable flows. See Browser | |
helpdesk Helpdesk pack | pulse · stats · ticket · account · draft · raise · reviews · setup · workflow | Your support queue in SupportCandy or Pylon: a ranked pulse, a ticket's story, replies left as private notes, bugs filed where you track them, the app's App Store reviews in the pulse, and a queue profile per project for its own workflow. See Helpdesk |
slack Slack pack | pulse · sort new channels | Read-only Slack through your own account: a pulse across your channels grouped by the channel map you own, one channel, a thread or a search, and new channels filed into the map. Never posts or reads DMs. See Slack |
media | summarize · ticket · transcribe · screenshots · remember | An audio or video file on your computer made readable: a timestamped transcript made on-device, screenshots, a summary of what was said and shown, repro steps from a bug-report video, or the recording saved to the brain. Needs yap (macOS 26+) and ffmpeg |
Brain and memory
| Skill | Playbooks | What it's for |
|---|---|---|
knowledge-compile | Compile raw sessions, feedback, and inbox items into wiki articles | |
sync | Every maintenance operation in one pass, ending in a status line and a next move | |
self-review | brain · rules | The monthly upkeep: prune stale tasks, memory and articles, then turn accumulated feedback into prompt and skill edits, pruning first. See Self-evolution |
dashboard | Refresh and open the dashboard, refresh the cmux sidebar alone, or pin a report to the dashboard's sidebar. See Dashboard | |
history | Local version history for the home in one question; kept outside a synced folder | |
seed | export · import | Hand a persona and setup to a teammate as a zip, or import one with fork semantics. See Seed bundles |
mermaid | Parse-check and visually critique a Mermaid diagram before it ships | |
humanizer | Strip the tells of AI-generated prose | |
configure-skills | Set up a pack's keys and permissions, install third-party libraries, or author a custom skill | |
init | Guided first-run onboarding that scaffolds the home. Runs only when named | |
rename-agent | Change the agent's display name across an existing home. Runs only when named |
Tool-only packs
Some packs add tools and no skill of their own. Every tool is listed in MCP tools.
| Pack | What its tools do | Used by |
|---|---|---|
| GitHub | Read pull requests, issues and workflow runs. Its writes open and label issues with screenshots attached, and update your own PR's description once you approve it. See GitHub pack | engineer's pull-request playbooks (Pull requests), adversarial-review with a pull request as its target, helpdesk raising tickets as cards |
| Database | Read-only Postgres queries, and a fork for risky schema work. See Database | Any session |
| App Store | One tool, appstore_reviews: any app's reviews from Apple's public feed, read-only and with no key. See App Store | The helpdesk pulse, when a queue profile names an app |
| Browser | Beside its browser-flows skill, the browser_* tools and web_search | Any session |
Extending a plugin skill
A plugin skill is the same in every home. To change how one works in yours, write the change in extensions/skills/<skill>.md, named for the skill, such as extensions/skills/helpdesk.md. It is plain markdown: rules, defaults, steps to add or skip, facts the skill should know.
- Every session lists them. Session start names each extension by skill, ahead of the other dynamic context so the size cap never cuts it. A home with none adds nothing.
- The skill reads its extension before it runs, and where the two disagree, the extension wins.
- It survives updates. The file lives in your home, not the plugin, so a plugin update never touches it, and seed bundles carry the folder to a teammate.
Third-party libraries
Content and marketing libraries that are prompts only are not bundled. configure-skills installs them from skills.sh into <HOME>/.claude/skills/ as symlinks, so upstream updates reach you.
| Library | Holds |
|---|---|
aaron-he-zhu/seo-geo-claude-skills | 20 skills, Apache-2.0 |
coreyhaines31/marketingskills | 23 playbooks |
Writing your own
Authoring a custom skill is not one of the plugin's skills. configure-skills points you at your host's skill-authoring tooling (Claude Code ships a skill-creator plugin).