poteto-help
Explain Pstack setup, BB Pi workers, skills, playbooks, and recovery. Do not start work for a help-only question.
- License 许可
- MIT
- 最近更新
- 2026-10-24
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- poteto-help
- description
- Explain Pstack setup, BB Pi workers, skills, playbooks, and recovery. Do not start work for a help-only question.
- disable-model-invocation
- true
02 资源文件 2
- 参考文档references/prompting.md3.1 KB
- 参考文档references/recipes.md4.2 KB
03 SKILL.md 正文
Poteto help
Answer the question, give a usable prompt, and link the actual installed skill or reference with an absolute file path. Do not link an upstream Cursor page as if it described this BB adaptation.
For a help-only question, do not start workers. For a request to do work, read Poteto Mode and follow its route.
Setup and first task
- Install this Pi package and the standalone Pstack BB plugin. The plugin exposes
pi_workerandbb pstack worker, using BB’s unchanged Pi provider with native startup tool settings. - Use
/setup-pstackin Pi to choose role models, or keep the inherit-parent defaults. Settings live in~/.pi/agent/pstack/models.json. - In BB, ask the agent to use Poteto Mode with a goal and a checkable outcome. For example: “Use $poteto-mode to fix the failed login. Show the working login and its regression check.”
Poteto Mode is sticky in Pi until /poteto-mode off. The /pstack off switch hides the model-visible Pstack skill entry; explicit skill loading still works. Neither switch disables role-model lookup.
If a project has no verification harness, explain that gap and offer Create verification skill. Do not call compilation proof of working behavior.
BB workers
Read BB interaction and workers.
Workers are fresh, visible, nested BB Pi threads. Pi enforces their explicit tool selections. The coordinator decides fanout, dependency order, judging, and retries. There is no Herdr or native-child fallback.
Desktop is the normal host. Server60 and Endurance serve work tied to their local hardware or services. Projectless personal work is valid.
Questions normally go through the coordinator, but the operator can open and talk to any worker. Consequential direct scope changes must reach the coordinator. BB Stop affects the selected thread. Completed workers stay nested during the run, then are archived after results and work are preserved.
Choose a skill
Recommend Poteto Mode for a complete task. Recommend a specific skill when the operator wants a bounded result. Read that skill before describing its method.
| Need | Skill |
|---|---|
| Explain current code or find an implementation location | How |
| Investigate why code has its current shape | Why |
| Teach a subsystem plainly | Teach |
| Review a PR, diff, or branch | Code review, Audit |
| Challenge a design or implementation | Code review, Challenge |
| Compare independent candidate solutions | Arena |
| Cover verification slices or run a race | Swarm |
| Settle architecture before implementation | Architect |
| Estimate and verify the effect outside a diff | Blast radius |
| Test a performance claim | Benchmark checklist |
| Catch up on prior work | Recall |
| Catch up on changes since your last message | Ketchup |
| Restate the user's goal before work | In your own words |
| Refine the approach and constraints, then do the task | Sharpen |
| Turn a completed run into proposed lessons | Reflect |
| Correct repeated mistakes | Correct |
| Write or revise technical prose | Technical writing |
| Restate an answer plainly | Bro |
For another skill, inspect its frontmatter. Principle skills are indexed in Poteto Mode.
Playbooks and recovery
Playbooks are task steps inside Poteto Mode, not separate slash commands.
- “Check PR 123” routes to Babysit. It does not grant merge authority.
- “Take over this branch” routes to Session pickup.
- “Plan this multi-PR change” routes to Multi-phase plan.
- A standing multi-day program routes to Orchestrate.
- An authorized implementation-and-landing run routes to Autopilot-full.
Recover existing BB workers before spawning replacements. Read full worker outputs; completion notices can be abbreviated. Do not delete conversations or workspaces as routine cleanup.
Explain consequential choices in chat. Use BB's browser and file viewer for comparison and inspection, and Plannotator for annotations. Add plugins only for demonstrated gaps.
Upstream
Cursor Pstack is the source of workflow methods. This Pi package translates execution and interaction to BB. Its importer preserves upstream invocation settings, approved performance guidance, and Pi-owned PR policy overlays. Do not install the Cursor plugin into Pi as a substitute for this adaptation.
04 同仓库更多 Skills
sidekick-browser
Use the pinned local AXI launcher for explicit, isolated browser verification in a Sidekick child.
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.
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 /skill:technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
teach
Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.