poteto-help
Guides users through pstack setup, /poteto-mode or $poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help or $poteto-help with a question.
- License 许可
- MIT
- 最近更新
- 2026-10-28
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- poteto-help
- description
- Guides users through pstack setup, /poteto-mode or $poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help or $poteto-help with a question.
- disable-model-invocation
- true
02 资源文件 2
- 参考文档references/prompting.md3.2 KB
- 参考文档references/recipes.md3.5 KB
03 SKILL.md 正文
Poteto help
Answer the user's question about pstack, hand them a prompt they can send, and link the file the answer came from. For a help question, don't start the work. The user asked how, and a pstack run spends real tokens, so let them send the prompt.
A message that asks for work, such as "use pstack to fix this bug", is not a help question. Read poteto-mode and do the work under it.
This file maps questions to the skills and guide pages that hold the answers. Those files own the details. Read the file you route to before you quote it, and trust it when it disagrees with this map. The links here point into the installed plugin, which the user may not be able to open, so give the user the file's public copy: https://github.com/cursor/plugins/blob/main/pstack/ followed by its path.
Find out what they need
Infer the need from the message and the conversation. A named situation, such as "which skill reviews a PR?", goes straight to its section. If the need is still unclear, ask one multiple-choice question with these options, then answer only the section they pick:
- Get set up
- Start a task with
/poteto-mode($poteto-modein Codex) - Pick a skill for a situation
- Fix a run that went wrong
- Make pstack my own
Check the state that changes the answer, and mention it only when it does:
- No
.agents/pstack-models.mdin the project's main checkout ("$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")/.agents/pstack-models.md", which may not exist) means the setup-pstack skill hasn't run for this project, so every role uses its default model. - No
verify-*skill or other app harness in the project means agents have no scripted way to drive the app. Mention/create-verification-skill($create-verification-skillin Codex) when the question is about proving a change works.
When the models file is missing and it matters, ask whether the user wants to pick a model for each role and a reasoning budget now. It matters when the user is new, the question is about setup or cost, or the answer depends on which models run. Ask at most once per chat. If the need is also unclear, ask both questions together. Offer two choices:
- Now: give them
/setup-pstack($setup-pstackin Codex) to type, and answer their question too. - Later: answer their question, and add one line saying every role keeps its default model until they run
/setup-pstack.
Get set up
- Install every pstack skill into the project's
.agents/skills/with theskillsCLI. They read each other, so take them all. - Run
/setup-pstack($setup-pstackin Codex). It asks for a reasoning budget, maps a model to each role, and writes.agents/pstack-models.mdin the project's main checkout ("$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")/.agents/pstack-models.md", which may not exist). Skills read it at each spawn. - Start a real task with
/poteto-mode($poteto-modein Codex), a goal, and a check that can pass or fail.
Installing changes nothing until the user invokes a skill. Only the setup-pstack skill loads from the user's words. Offer to word their first prompt with them, per references/prompting.md.
If cost is the worry, say where the tokens go and how to spend fewer. pstack spends extra tokens on subagents and review panels. Rerun /setup-pstack ($setup-pstack in Codex) and pick a smaller budget or cheaper models. A role set to inherit-parent runs on the chat's model, which saves tokens when the chat runs on a cheaper model. A shorter panel list runs fewer subagents, one for each entry. Save /poteto-mode ($poteto-mode in Codex) for work that needs rigor.
pstack is built for T3 Code, running Claude Code or Codex. Its skills use the Agent Skills format, so other tools can read them. But most workflow skills, including poteto-mode, how, why, and teach, spawn T3 child tasks with per-role models, and scheduled tasks are a T3 feature, so those parts may not work there.
Start a task with /poteto-mode ($poteto-mode in Codex)
The poteto-mode skill matches the task to a playbook, copies the playbook's steps into a visible step list (update_plan in Codex, the reply in Claude Code), and runs the other skills as the steps need them. A step it skips stays in the list as skip: <reason>. A good prompt states the goal and how to tell it's done. It doesn't list skills, because a hand-written sequence tends to drop or reorder steps the playbook would keep. Read references/prompting.md before you help word one.
Whether the poteto-mode skill stays on depends on how the user starts it:
- Enter on
/poteto-mode($poteto-modein Codex) attaches the skill to one message. It fades as the chat moves on. - To keep it on, start each new task with
/poteto-mode.
Mid-chat, "new task" makes the mode match a fresh playbook. The poteto-mode skill already uses poteto-agent for the subagents its playbook steps spawn. To get the same style from a subagent of your own, start its brief with "Read <abs>/pstack/agents/poteto-agent.md and act as that agent. The poteto-mode skill is at <abs>/poteto-mode/SKILL.md.", where <abs> is the absolute path of the folder that holds the pstack skills (resolve .. from this skill's folder).
Pick a skill
The default answer is /poteto-mode ($poteto-mode in Codex), which runs most of the others when its steps need them. Name a skill directly when the user wants more or less of something than the playbook gives. Read the skill before you recommend it, and give one example prompt.
In Codex, start with $ instead of /.
| The user wants to | Skill |
|---|---|
| Do any non-trivial task with rigor | /poteto-mode |
| Check that the agent understood their goal and the problem before it starts | /in-your-own-words |
| Aim a task higher before starting: more expert, more outcome-focused, not overspecified | /sharpen |
| Know how code works now, or where new code should live | /how |
| Know why code is shaped this way, or where a number came from | /why |
| Understand a change or subsystem, explained plainly | /teach |
| Catch up on their own recent work on a topic | /recall |
| Catch up on what changed in this chat since their last message, in a few plain sentences and small visuals, with enough context to decide each action item | /ketchup |
| Know what a small diff could break outside itself | /blast-radius |
| Settle types and module shape before code that crosses a function boundary | /architect |
| Get several attempts at one brief, merged into the best one | /arena |
| Run parallel checks over slices, or race workers | /swarm |
| Have different models review a diff and try to break it | /interrogate |
| Fix a bug test-first when a cheap local test exists | /tdd |
Apply TypeScript rules to .ts or .tsx work |
/typescript-best-practices |
| Strip comments before review, using a reviewer that didn't write them | /no-comments |
| Clean AI tells out of prose | /unslop |
| Write docs, an RFC, a README, a PR description, or a commit message to a standard | /technical-writing |
| Hear the last reply again in plain words | /bro |
| Give agents a scripted way to drive the app and prove behavior | /create-verification-skill |
| Bring a verification skill and its feature map back in line with the app | /maintain-verification-skill |
| Vet a performance number before reporting or acting on it | /benchmark-checklist |
| Run a large or cross-cutting change, or one to review after stepping away | /figure-it-out |
| Keep a decision log during a run, and review it afterward | /show-me-your-work |
| Pick a model for each role and a reasoning budget | /setup-pstack |
| Turn their own working habits into a personal mode skill | /automate-me |
| Turn what a finished task taught into skill edits | /reflect |
| Stop agents from repeating the same mistakes in this repo | /correct |
| Build a page whose buttons wake an agent thread over a webhook | /make-bot-ui |
| Find their way around pstack | /poteto-help |
If a skill directory next to this one is missing from the table, read its frontmatter and route by its description. The principle-* directories are covered under principles below.
Close calls:
- how explains what the code does. why explains the reasons. teach runs one or both and explains the result plainly.
- arena gives every worker the same brief and merges the best parts. swarm splits work into slices or a race and returns one report.
- architect implements right after it settles the design. Add "with checkpoint" to review the design before it writes code.
- interrogate reviews the diff. blast-radius looks for breakage outside the diff and proves the one fact that makes the change safe.
- recall rebuilds context across recent chats. ketchup covers only this chat since the user's last message. Resuming one specific chat or branch is the Session pickup playbook.
- figure-it-out designs one rigorous run. The Orchestrate playbook runs a program that spans days and many PRs. The Autonomous run playbook drives one task to a finish condition.
Not in pstack:
/deslopships separately, if it is installed. To drive the app, agents use the project's own verification skill, T3'spreview_*tools for a UI, or the shell for a CLI.- Repeating work on a timer uses T3's scheduled tasks (
schedule_task), not a pstack skill. - pstack has no
/orchestrateskill. Orchestrate is a playbook in the poteto-mode skill. If the slash menu shows/orchestrate, another plugin provides it.
Playbooks and principles
Playbooks are step lists inside the poteto-mode skill, not skills, so they have no slash command. Inside poteto-mode, describing the task picks one, and these phrases name one directly:
- "babysit this pr" or "check on pr 123" runs Babysit. It drives the PR to merge-ready and stops there. It doesn't merge unless the user asks to merge, land, or ship.
- "land the stack" runs Shipping.
- "take over this branch" runs Session pickup.
- "pause safely" runs Pause safely.
- "full autopilot on this queue" runs Autopilot-full. "stack them, don't ship" runs Autopilot-stack.
- "run the eval playbook" runs Eval.
Without the poteto-mode skill, a phrase such as "babysit this pr" can start another installed skill for the same job instead. The Playbooks section of poteto-mode lists every playbook and when it applies.
pstack has no planning skill. T3's plan mode works alongside it. For work that spans phases or stacked PRs, asking /poteto-mode ($poteto-mode in Codex) for a plan runs the Multi-phase plan playbook, which writes the plan and doesn't implement it. For a design question, the Prototype playbook or the architect skill settles it in code first.
Principles are one-rule skills that the poteto-mode skill reads and cites in its replies. The user rarely invokes one. They steer with the names instead, as in "apply prove it works. show me the real output." Typing /principle-<name> ($principle-<name> in Codex) still loads one on demand.
Fix a run that went wrong
| Symptom | Fix |
|---|---|
| The mode stopped applying after a few turns | It was attached to one message and faded. Start each task with /poteto-mode ($poteto-mode in Codex). |
| A question got treated as the next step of the last task | Say "new task", or say the turn doesn't need the mode. |
| A new model choice had no effect | Skills read the models file /setup-pstack ($setup-pstack in Codex) writes at each spawn. Check the role's line in it. |
| Runs cost more than expected | See the cost paragraph under Get set up. |
| A skill didn't load on its own | Only /setup-pstack loads from the user's words. The others load when the user types them or when /poteto-mode runs them, and it doesn't run every skill. |
| Parallel agents overwrote each other | Give each agent that writes its own worktree (isolation: "worktree"). |
| An overnight run moved but finished nothing | Looping until done needs a check that can pass or fail, not a duration. |
| The reply claims success from a green build | Ask for the real command, flow, stored value, or profile. That's the prove-it-works principle. |
For a run that drifts, references/prompting.md has one-line steers.
Make pstack my own
/automate-me($automate-mein Codex) drafts a personal mode skill from the user's own history, to use alongside/poteto-mode($poteto-modein Codex)./reflect($reflectin Codex) after a session turns its lessons into skill edits the user approves./poteto-mode write a skill for <workflow>runs the authoring playbook. The eval playbook tests a skill change blind.- Fix a misbehaving skill in its own PR, not inside the feature work where it went wrong.
Reply
Lead with the answer. Give at most one example prompt in a code block, adapted from references/recipes.md when one fits, then the link to that file. Keep it short unless the user asked for the whole map.
04 同仓库更多 Skills
patchbook-update
Pull upstreams into a repo that keeps its changes in a patchbook (.patchbook/), repair what broke from each change's intent, test and review, then merge and deploy only when the sync was clean or the test command passes, and otherwise ask, opening a pull request when there are commits to push. Use when a scheduled task or the user says to update a patchbook repo, or for /patchbook-update or $patchbook-update.
why
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
verify-patchbook
Drive the patchbook CLI from this checkout in a disposable sandbox (its own git repos, store, config and a fake model) and capture a transcript as proof. Use to reproduce a patchbook bug, run an issue's repro script, or prove a change to clone, init, record, the pre-commit hook, build, status, check, sync or upstream works the way a user would see it.
unslop
Cut AI tells from any writing.
typescript-best-practices
TypeScript best practices. Use when reading or editing any .ts or .tsx file.
technical-writing
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or $technical-writing, or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.