AgentLayer▸docs
Reference

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.

ToType
Run a skill by name/agentlayer:<name> in Claude Code, $<name> in Codex. These docs use the bare name
Run one playbookThe playbook after its skill: briefing pulse, goals week, seo audit
See a skill's playbookshelp after its name: goals help

How skills start:

  • Three run only when you name them, because firing one unasked would cost too much: init, release and rename-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. A seo playbook whose key is missing names it and stops.

Plan and run

SkillPlaybooksWhat it's for
attentionrefresh · add · plan · organize · standup · checkpoint · checkpoint all · backfillYour 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
goalsday · week · month · yearGoals from today to the year, set by interview and written to your task hub; the day and the week get scored. See Daily rhythm
briefingmorning · evening · pulseThe morning brief, the evening wrap, and a one-minute scan for anything on fire
projectcreate · archive · handoffStart a project with the right scaffolding, retire one cleanly, or hand a task to the team as a GitHub issue
taxsetup · calendar · position · capture · close · estimate · accountant · optimize · year-endEvery 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
roadmapA strategic roadmap as one self-contained HTML page, its content kept as JSON attention can read
flywheelA cross-project work session framed by the north-star roadmap, caught up on every session since the last one
adversarial-reviewA second model on anything you made; the agent verifies each finding and fixes the real ones. See Second-model review
find-sessionFind a past session by what it worked on, with its resume command
itineraryPlan a trip into an interactive, print-ready HTML itinerary
guideA 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

SkillPlaybooksWhat it's for
engineer21 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-worktreeCreate a sibling git worktree and bootstrap it; also the read-only worktree audit
plan-specA Socratic interview into a standalone spec, with a design section for code
api-collections API packDraft API requests as Bruno, Postman, or plain-curl collections you fire yourself
upgradeApply pending home migrations after a plugin update
releaseMaintainer only: cut a versioned release with its Upgrade block. Runs only when named

Reach and see

SkillPlaybooksWhat it's for
seo SEO packaudit · console · speed · serp · rankHow 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 packWordPress posts, pages, and modified dates through the public REST API, for SEO or anything else
browser-flows Browser packDrive a visible browser through repeatable flows. See Browser
helpdesk Helpdesk packpulse · stats · ticket · account · draft · raise · reviews · setup · workflowYour 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 packpulse · sort new channelsRead-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
mediasummarize · ticket · transcribe · screenshots · rememberAn 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

SkillPlaybooksWhat it's for
knowledge-compileCompile raw sessions, feedback, and inbox items into wiki articles
syncEvery maintenance operation in one pass, ending in a status line and a next move
self-reviewbrain · rulesThe monthly upkeep: prune stale tasks, memory and articles, then turn accumulated feedback into prompt and skill edits, pruning first. See Self-evolution
dashboardRefresh and open the dashboard, refresh the cmux sidebar alone, or pin a report to the dashboard's sidebar. See Dashboard
historyLocal version history for the home in one question; kept outside a synced folder
seedexport · importHand a persona and setup to a teammate as a zip, or import one with fork semantics. See Seed bundles
mermaidParse-check and visually critique a Mermaid diagram before it ships
humanizerStrip the tells of AI-generated prose
configure-skillsSet up a pack's keys and permissions, install third-party libraries, or author a custom skill
initGuided first-run onboarding that scaffolds the home. Runs only when named
rename-agentChange 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.

PackWhat its tools doUsed by
GitHubRead 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 packengineer's pull-request playbooks (Pull requests), adversarial-review with a pull request as its target, helpdesk raising tickets as cards
DatabaseRead-only Postgres queries, and a fork for risky schema work. See DatabaseAny session
App StoreOne tool, appstore_reviews: any app's reviews from Apple's public feed, read-only and with no key. See App StoreThe helpdesk pulse, when a queue profile names an app
BrowserBeside its browser-flows skill, the browser_* tools and web_searchAny 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.

LibraryHolds
aaron-he-zhu/seo-geo-claude-skills20 skills, Apache-2.0
coreyhaines31/marketingskills23 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).

On this page