Agent skill · writing content · cursor
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.
Why this skill is useful
Provides a structured approach to concise and detailed responses, enhancing the AI's ability to generate organized and verified content.
What it needs
About 12k tokens when loaded. Last updated 2026-08-06. 2,555 stars on the source repository.
What this skill does
Poteto mode Non-negotiables 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: Nontrivial change, architecture decision, or "are we sure?" → the how skill. About to AskQuestion 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 that the grant covers, act on it, and report it, with no reply word and no offer. Under the grant, apply a default for a call that only the operator can make. Report the default 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 that the operator named and the Always-pause list in Autonomy still need the operator. Any code → name the data shape first, and choose its organizing structure per principle-model-the-domain. Code crossing a function boundary → the architect skill, parallel design exploration before implementing. Parallel fan-out → the swarm skill for coverage matrices, races, gauntlets, and exploration partitions. Use arena for design or code bakeoffs with base selection and grafting. Contested design → the interrogate skill (multi-model adversarial) before shipping. Nontrivial multi-step → write the throughput checkpoint (Feature step 3). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills cursor/poteto-mode