poteto-mode
poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.
Before you install
- Last update
- Files in folder
- 73
- Scripts
- Contains scripts. Review them before running.
- SKILL.md size
- 26 KB (about 6,667 tokens of context each time it loads)
- License
- MIT
- Source on GitHub
- michael-denyer/pstack-claude
Skills are plain text instructions the agent follows, sometimes with scripts. Check the source, prefer repositories with many installs and stars, and read any script it ships.
Install
npx skills add michael-denyer/pstack-claude@poteto-modeRuns in a terminal with Node.js 18 or newer. Add -y to skip the prompts and -g to install for every project instead of this one.
Install for your agent
npx skills add michael-denyer/pstack-claude@poteto-mode --agent claude-code -y- Project install writes to
.claude/skills/poteto-mode- Global install writes to
~/.claude/skills/poteto-mode
Start a new session afterwards so the agent picks the skill up. In Claude Code you can also call it directly with /poteto-mode.
What it does
Poteto mode Bundled skills live at ../ /SKILL.md from this file, so put this file's absolute path in every poteto-agent prompt. Platform Adaptation These skills use Claude Code tool names (the Skill tool, the Agent tool, AskUserQuestion) and the Claude model names the Agent tool accepts, as each Models section lists them. On Claude Code they work as written. On Codex, read references/codex-tools.md for the Codex equivalent of a Claude tool, model, or skill named by these workflows. On Pi, read references/pi-tools.md instead. On GitHub Copilot, CLI or app, read references/copilot-tools.md…
Excerpt from the skill's own SKILL.md. Read the full file on GitHub before installing: skills run with your agent's permissions.
Categories
Related skills
- unslop
michael-denyer/pstack-claude
Cut AI tells from any writing.
- how
michael-denyer/pstack-claude
Use for \"how does X work\", code walkthroughs before changing something, and placement / ownership / layering questions (\"where should this live\", \"which package owns this\", \"is this the right layer\"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.
- arena
michael-denyer/pstack-claude
Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.
- blast-radius
michael-denyer/pstack-claude
Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', reviewing a small diff you don't trust, or a brief that asserts something about existing code ('make X public', 'X already handles Y') before you design against that assertion.
- architect
michael-denyer/pstack-claude
Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.
- interrogate
michael-denyer/pstack-claude
Use for \"interrogate\", \"adversarial review\", \"multi-model review\", \"challenge this\", \"stress test this code\", \"find blind spots\", or \"tear this apart\". Multiple LLM reviewers challenge changes from independent angles.