Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →michael-denyer/poteto-mode
poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work.
Passed 19 of 23 test cases with the skill, and 9 of 23 without it.
and 9 more in the full report
12 fixed7 passed either way2 still failing2 broke3 errored
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.8-flash on 10/21/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
When delegating a step to a subagent via the `Agent` tool, what default boolean flag value must be set for `run_in_background`?
| Checked | Without skill | With skill |
|---|---|---|
| Sets run_in_background to true. | Missed | Passed |
The instructions your model reads when the skill loads.
Bundled skills live at ../<name>/SKILL.md from this file, so put this file's absolute path in every poteto-agent prompt.
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 instead. On Muse, read references/muse-tools.md instead. Other runtimes can discover the same Agent Skills tree, but they must use their own tool, model, and configuration equivalents. No one of these mappings is a cross-runtime map.
Use the session's task-tracking tools for the todolist. On Claude Code these are TaskCreate and TaskUpdate, or TodoWrite when configured. Availability depends on the model; CLAUDE_CODE_ENABLE_TODO_TOOLS=1 enables them through the environment or a project's .claude/settings.local.json env block. See the task-tool documentation. If no task-tracking tool is available, keep an uncommitted todo.md Markdown checklist in the work dir, next to the decision trail, with the playbook steps verbatim and each skip: <reason> line. When several sessions share the checkout, name it .audit/<task-slug>.todo.md, beside that session's .audit/<task-slug>.tsv trail, so they never write one file.
The Principles section below grounds every trigger. In your reply, name each principle that shaped a decision and the specific choice it changed. Cite only principles whose leaf SKILL.md you read this session.
Remaining triggers:
AskUserQuestion on a "which approach", "how should I", or "what should this do" fork → classify it before you ask. If the answer is a fact you could observe by running something (behavior, timing, layout, output, perf, even whether an eval separates), it is not the human's to answer. Sketch it via the Prototype playbook (playbooks/prototype.md) and let the result decide. If the task is a read-only Investigation whose deliverable is a cited answer, stay in it and answer from the evidence rather than building a sketch. Reserve the question for a genuine product or preference call no experiment can settle. Under a full-autonomy grant, decide a call the grant covers, act on it, and report it, with no reply word and no offer. Under the grant, for a call only the operator can make, apply a default, report it with a full explanation, and say in plain words what the operator could tell you to do instead. The operator answers in their own words. Never give a shorthand token to type back. Gates the operator named and the Always-pause list in Autonomy still need the operator./technical-writing), on top of unslop./deslop)./no-comments).run ships with Claude Code and the model can invoke it for CLIs, TUIs, servers, and browser or Electron apps. The bundled verify runs only when the user types /verify, so for UIs use the project verify skill at .claude/skills/verify/ (generate it with /create-verification-skill) and fall back to run when the repo has none. For bug fixes, reproduce first on the same surface yourself. Hand to the user only under the narrow Bug fix step 1 exception.playbooks/babysit.md), not the bundled babysit skill, whose description matches the same words. Never triggered by merely opening a PR. Declare its mode before polling. The playbook's step 1 owns the request-to-mode mapping. Reaching for drive inside a phase agent stops that agent finishing its turn.playbooks/shipping.md). Green is not safe. Nothing gets armed before an independent per-PR verdict, and only the contiguous verified run from the root lands.references/bugbot-triage.md.Read the leaf skill in full for any principle you apply. Each entry names when it applies. Each leaf is the principle- skill, with the title in kebab case, hyphens kept and other punctuation dropped, unless the entry gives its name.
test cases passed, vs 9 / 23 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.