Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Skills Overview

What a skill is

A pstack skill is a single Markdown file named SKILL.md, placed in its own folder under skills/. It contains instructions, not code. A short header (the frontmatter) gives the skill’s name and a description of when to use it; the body sets out the steps, the criteria for judging the result, and the shape of the reply. When the agent loads a skill, it follows those instructions.

Skills vary considerably in size. /in-your-own-words is a single sentence, whereas /arena and /statechart run to several phases, and /statechart also ships helper scripts and a reference file next to its SKILL.md. What the larger skills have in common is that they define where to stop and what counts as evidence, so that a careful way of working can be repeated rather than improvised.

pstack 0.15.44 contains 58 skills. 24 of them are principles (folders named principle-*), and the remaining 34 are the working skills this part of the book describes.

How skills are invoked

Through /poteto-mode

The usual entry point is /poteto-mode. It reads your request, matches it to one of its playbooks (a predefined sequence of steps for a kind of task), opens a todo list whose first items are that playbook’s steps, and calls other skills as the steps require them. According to the README, the skills it routes to on its own include why, architect, arena, swarm, interrogate, unslop, no-comments, technical-writing, tdd, and the principles. You therefore do not need to memorize individual skills to benefit from them. See /poteto-mode and Playbooks Overview.

By typing /name yourself

You can also call any skill directly as a slash command, for example /how do we cancel runs?. In Claude Code, plugin commands carry a prefix, so /poteto-mode becomes /pstack:poteto-mode.

Every working skill except /setup-pstack sets disable-model-invocation: true in its frontmatter. In practice this means the agent does not start such a skill on its own initiative because its description happens to match the conversation; the skill runs when you type it or when another skill, such as /poteto-mode, names it as a step. The README states this explicitly for /poteto-help, /in-your-own-words, and /sharpen: each “runs only when you type” it.

Principles: same format, different role

The 24 principle-* folders use the same file format, but each one states a rule for judgment rather than a procedure. /poteto-mode contains an inline index of all 24 and reads it when a task starts. The standalone files exist so that other skills can cite a principle by name and so that the index can point to the full text of each rule. The index sorts them into 5 groups:

GroupCountExamples
Core10Laziness Protocol, Foundational Thinking, Attack the Premise, Subtract Before You Add
Architecture6Model the Domain, Boundary Discipline, Type System Discipline
Verification5Prove It Works, Fix Root Causes, Sequence Work into Verifiable Units
Delegation2Guard the Context Window, Never Block on the Human
Meta1Encode Lessons in Structure

The Principles Overview covers them in detail.

How skills depend on each other

Many skills are self-contained, but several call others as building blocks. The main dependencies, taken from the SKILL.md files themselves, are these:

  • /architect hands a large or contested design to /arena instead of sketching alone.
  • /interrogate reuses part of the /arena procedure (choosing runners and fanning out in parallel) and states the intent with /in-your-own-words.
  • /blast-radius presents itself as a companion to /how and /why, runs as an /arena for a large change, and writes its result through /unslop.
  • /figure-it-out uses /architect (and therefore /arena) for one-way design decisions and /show-me-your-work for its decision log.
  • /teach runs /how and /why and weaves their findings into one explanation.
  • /ketchup-video builds on /ketchup, and each verification skill generator is paired with a maintainer (/create-verification-skill with /maintain-verification-skill, /create-formal-verification-skill with /maintain-formal-verification-skill).
  • /recall, /automate-me, /show-me-your-work, and /technical-writing all pass their prose through /unslop.

Skills with no such references, for example /unslop, /why, /how, /tdd, and /bro, work on their own.

The 34 working skills by chapter

This book assigns each working skill to exactly one of six reference chapters.

/poteto-mode is listed with the skills about pstack itself, next to /poteto-help and /setup-pstack, because it is the plugin’s own entry point. It is large enough to have a chapter of its own, /poteto-mode, which is where it is described in full.

How to use the reference chapters

Each reference chapter describes its skills from the same four angles:

  • what the skill does;
  • when to use it;
  • how it proceeds, summarized from its SKILL.md;
  • caveats and limits.

There are 3 sensible ways to read them:

  1. Start with /poteto-mode and the playbook chapters to see how the whole system runs. At that stage it is enough to know that the individual skills exist.
  2. Read in advance only the chapters that match situations you meet often, such as reviewing, investigating, or designing.
  3. When a skill surprises you in practice, return to its section and check the caveats.

If you are not sure which skill fits a task, ask /poteto-help before searching these chapters. It finds out what you are trying to do, answers that part, and gives you a prompt you can send; it does not start the work itself. The chapter Choosing Between Similar Skills compares skills whose names or purposes overlap.