poteto-help
Guides users through pstack setup, /poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help with a question.
michael-denyer · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add michael-denyer/pstack-claude --skill poteto-help技能说明
name: poteto-help description: Guides users through pstack setup, /poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help with a question.
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 installed skills, playbooks, and platform mappings that own the answers. Read the matching source before answering. Its instructions take precedence over this map and any upstream guide, which describes Cursor and may differ from this port. The local links point into the installed plugin, so give the user the file's public copy: https://github.com/michael-denyer/pstack-claude/blob/main/plugins/pstack/ followed by its path relative to the plugin root.
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 - 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:
- For model or routing questions, identify the runtime and installation type, then read
setup-pstackfor the sheet's location and how that runtime loads it. Check that configuration before saying whether defaults or overrides apply. - No project
verifyorverify-*skill or other app harness means agents have no scripted way to drive the app. Mention/create-verification-skillwhen the question is about proving a change works.
When the model sheet is missing and it matters, ask whether the user wants to pick a model for each role and a default effort 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-pstackto 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
- Identify the user's runtime and whether they want a native plugin/package or skills-only installation. Read its section in the README or shared installation reference, then give the matching install command.
- Read
/setup-pstack, including its Other runtimes table, before explaining model choices, effort, sheet loading, or automatic routing. For a bundled routing hook or extension, use its persistentsession hook: offsetting in the current runtime's sheet to turn routing off. - Offer a first task prompt with a goal and a check that can pass or fail, per
references/prompting.md. Use the current runtime's invocation syntax from the slash-command reference.
Before giving runtime-specific instructions or adapting a recipe, read the Codex mapping or Pi mapping when applicable. Their routing sections cover hook trust, extension loading, and skills-only installs. For other runtimes, use the runtime support reference.
If cost is the worry, say where the tokens go and how to spend less. pstack spends extra tokens on subagents and review panels. Rerun /setup-pstack and pick a lower effort or cheaper models. A role set to auto or inherit-parent runs on the chat's model, which costs less when the chat runs on a cheaper model. A shorter panel list runs fewer subagents, one for each entry. Save /poteto-mode for work that needs rigor.
Start a task with /poteto-mode
/poteto-mode matches the task to a playbook, copies the playbook's steps into the todo list, 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.
For whether later tasks route automatically, use the setup and runtime sources under Get set up. Check that routing is enabled for this installation before promising it. Without automatic routing, invoke poteto-mode for each new task. Mid-chat, "new task" makes the mode match a fresh playbook. For subagent defaults, read poteto-mode's Subagents section and the current runtime's mapping.
Pick a skill
The default answer is /poteto-mode, 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.
| The user wants to | Skill |
|---|---|
| Do any non-trivial task with rigor | /poteto-mode |
| 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 |