Poteto mode Agent Skill

poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work.

Context cost
15.8k tokensestimated from the bundle, loaded when it triggers
Bundle
20 files · 63.2 kBtext throughout, nothing executable
Licence
GPL-3.0the author’s own terms
Last change
—no release on file
Servers it uses
Noneruns standalone

What it does

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.

What this skill changes about the agent has not been set out here as a list. Its SKILL.md, shown below, says it in the author’s own words.

agentproductivity

The skill itself

A skill is instructions the model reads, so you can see what you are getting: below is the start of its SKILL.md. The front matter loads with every session, the body loads when the skill triggers, and the whole file comes with the install.

SKILL.md16.4 kB · preview
--- name: poteto-mode ---
6# Poteto mode
7
8## Platform Adaptation
9
10These skills use Claude Code tool names (the Skill tool, the Agent tool, AskUserQuestion) and Claude model slugs (claude-opus-4-8). On Claude Code they work as written. On Codex and other runtimes, the skills are the same files; only the tool, model, and built-in-skill names resolve differently. When a skill names a Claude tool, a claude-* model, or a Claude built-in skill (run, verify, plugin-dev:skill-development), read [references/codex-tools.md](references/codex-tools.md) for the Codex equivalent.
11
12## Non-negotiables
13
14**Start every multi-step task with a todolist whose first item is to read the Principles section below in full.** The principles ground every trigger here. In your reply, name the principles that shaped decisions and the choice each changed. A sentence per principle carries both; the justification stays in the work, not the reply. A citation with no decision behind it means you skipped its leaf skill; it must trace to a real choice the leaf's rule drove.
15
16Remaining triggers:
17
18- Nontrivial change, architecture decision, or "are we sure?" → the **how** skill.
19- About to 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. The ask is the slow path. A throwaway probe usually answers faster, and it hands the human a result to react to instead of a decision to make.
20- Any code → name the data shape first, and choose its organizing structure per **principle-model-the-domain**.
21- Code crossing a function boundary → the **architect** skill, parallel design exploration before implementing.
22- Contested design → the **interrogate** skill (multi-model adversarial) before shipping.
23- Nontrivial multi-step → write the throughput checkpoint (Feature step 3).
24- Any prose surface → the **unslop** skill. Your reply is a prose surface; write it per **Writing the reply**. Agent-facing prose also follows the **plugin-dev:skill-development** skill (Claude Code's authoring guidance for SKILL.md files).
This is a preview of SKILL.md. Download or install the skill to get the whole thing.
In the file
SKILL.md2,379 words
Files20
LicenceGPL-3.0
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈60
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
15,740
on trigger
The instruction body and 19 supporting files, read only when the skill fires.
7.9%
of a 200k window
Ten skills this size would take about 79% of the window before you open a file.
050k100k150k200k context window

15.8k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Heavy. Teams tend to install this one per project rather than globally, and load it only when the job comes up.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

The procedure it runs

The procedure has not been set out here step by step. It is in the body of its SKILL.md: the start of it is shown above, and the whole file comes with the install.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

Its SKILL.md does not declare which tools it asks the agent for, so what it touches is whatever the instructions themselves ask for — read them before you install it.

What it asks for
Writes filesnot declared
Network accessnot declared

This SKILL.md carries no allowed-tools line, so neither is declared. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

20 files, 63.2 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md16.4 kB
  • playbooks/authoring-a-skill.md1.0 kB
  • playbooks/autonomous-run.md1.5 kB
  • playbooks/bug-fix.md2.8 kB
  • playbooks/eval.md3.2 kB
  • playbooks/feature.md3.0 kB
  • playbooks/hillclimb.md4.5 kB
  • playbooks/investigation.md1.1 kB
  • playbooks/multi-phase-plan.md0.1 kB
  • playbooks/opening-a-pr.md1.4 kB
  • playbooks/pause-safely.md1.5 kB
  • playbooks/perf-issue.md3.6 kB
  • playbooks/prototype.md2.6 kB
  • playbooks/refactoring.md4.0 kB
  • playbooks/runtime-forensics.md1.5 kB
  • playbooks/session-pickup.md2.2 kB
  • playbooks/trace-forensics.md2.1 kB
  • playbooks/visual-parity.md1.4 kB
  • references/codex-tools.md4.2 kB
  • references/plan.md5.1 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 20 files you can review in full before installing. The GPL-3.0 licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# Poteto mode · 15.8k tokens when loaded · macOS, Linux mkdir -p .claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/poteto-mode/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/poteto-mode" ] && { [ ! -e .claude/skills/poteto-mode ] || { mv .claude/skills/poteto-mode "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/poteto-mode" .claude/skills/ && echo "Installed .claude/skills/poteto-mode"
On Windows, or any OS with Node 20+
npx mcprush@latest skill add geiserx/poteto-mode

Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither. Writes to .claude/skills/poteto-mode/ in the current project. For every project instead, run mkdir -p ~/.claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/poteto-mode/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/poteto-mode" ] && { [ ! -e ~/.claude/skills/poteto-mode ] || { mv ~/.claude/skills/poteto-mode "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/poteto-mode" ~/.claude/skills/ && echo "Installed ~/.claude/skills/poteto-mode" (macOS, Linux) — or add --global to the npx line. The curl line replaces .claude/skills/poteto-mode/ only after the download succeeds, so files left there by another skill of the same name, or by an older release, do not mix in. A copy already there is moved aside, not deleted, and the line prints where.

Which clients pick it up on their own

A skill is a folder of text. Most of these read a skills folder and pick it up without being told; the rest take the same folder another way — an upload in the app, a parameter on an API call — and then choose it by its description just the same.

Claude Code.claude/skills/
Claude DesktopCustomize › Skills
ChatGPTSkills › Create › Upload
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok Build.grok/skills/
Microsoft CopilotSkills › Upload a skill
PerplexityComputer › Skills › Upload a skill
DeepSeek Harness.dsh/skills/
Zed.agents/skills/
Devin Desktop.devin/skills/
Windsurf (legacy).windsurf/skills/
OpenAI Agents SDKInstructions or sandbox Skills
HTTP / APIa request parameter
This release
Versionnot versioned
Publishedno release date on file
PriceFree
Referencegeiserx/poteto-mode

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

—no reviews yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Sign in to review it

A review is tied to an account so it can be answered, edited and taken down by the person who wrote it.

Sign in
Who can post

Anybody with an account, one review each. It carries the version that was current when you wrote it, and the publisher may reply once.

Publisher
Servers9
Claim this skill