poteto-help
Explain pstack setup, poteto-mode, and how to choose a Codex skill for a task.
- License 许可
- MIT
- 最近更新
- 2026-11-03
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- poteto-help
- description
- Explain pstack setup, poteto-mode, and how to choose a Codex skill for a task.
- disable-model-invocation
- true
02 资源文件 2
- 参考文档references/prompting.md3.1 KB
- 参考文档references/recipes.md3.6 KB
03 SKILL.md 正文
pstack help for Codex
Read the Codex adapter. Answer a help question without starting the task. If the user requests work, follow poteto-mode instead.
- Setup: install
pstackfrom this repository's local Codex marketplace, then invokesetup-pstackif model preferences are needed. The active model is the default. - General work: invoke
poteto-modewith a goal and an observable check. It chooses a playbook and coordinates the relevant skills. - Understand code:
how,why, andteach. Design and implementation:architect,tdd,figure-it-out. Review and cleanup:interrogate,unslop,technical-writing, andno-comments. - Formal verification: use
create-formal-verification-skillto create a check for a property. After covered code changes, usemaintain-formal-verification-skillto bring the check back in line and distinguish drift from a code bug. - Before sending a task, use
sharpento rewrite its prompt with an expert's sources, methods, and an outside check. It returns the prompt without executing it. - Use
statechartto check a TLA+ model, draw its states and shortest bug paths, and render its chart as SVG. - Use
ketchup-videofor a recap as subtitled slides. It needs an available local video renderer; useketchupfor a text recap. - Use the bundled guide and read the relevant skill before giving detailed advice. Link the bundled file in the answer.
make-bot-uiand Benny automations are excluded; their reasons are recorded in the repository compatibility matrix. Cursor-only steps may be unavailable; check the adapter for their replacements.
If the need is unclear, ask one focused question. Give a concrete example prompt for the recommended skill.
04 同仓库更多 Skills
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 /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'.
tdd
Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.