← ClaudeAtlas

one-passlisted

ALWAYS load first, before any other skill, when the user asks to save tokens or to get it right the first time ("no gastes tantos tokens", "sin errores", "hazlo bien a la primera", "save tokens", "don't waste tokens", "token budget", "stop redoing"), then use the task's own skills. Also use at the start of any task that produces a deliverable (code, design, video, copy, report, data change) or hands work to another agent or chat. It removes the redo loops that burn the most tokens: it locks the target before work starts, reads each source once, batches tool calls, picks the cheapest real check, reviews the result against its own acceptance list before saying done, caps retries, and writes briefs that land the first time. It never skips safety or verification to save tokens. Complements terse-output skills (caveman) and context skills (context-budget): those shrink words, this one removes rework, which costs far more.
RabbitDesigns22/claude-skills · ★ 0 · AI & Automation · score 75
Install: claude install-skill RabbitDesigns22/claude-skills
# One Pass The most expensive token is the one spent doing the same work twice. A short answer that has to be redone costs more than a careful one that lands. This skill cuts loops, not quality. Every rule below prevents one of six leaks: | Leak | What it looks like | |---|---| | Rework | Delivering, getting it back, redoing it | | Re-reading | Opening the same file, page or transcript again | | Wandering | Exploring past the point where the answer is known | | Retry storms | Running the same failing command or approach again and again | | Bloat | Dumping whole files, logs or pages into context | | Chatter | Messages, status updates and agents that add nothing | ## 0. Size the task (5 seconds) - **Trivial** (one fact, one edit, one command): skip to the work. Just do it right and check it once. - **Normal** (a deliverable): apply steps 1-6. - **Delegated or multi-step** (other agents, chats or sessions): apply everything, especially step 7. Do not spend more tokens on the method than on the task. ## 1. Lock the target (before any work) Write, in at most 5 lines and only for yourself, the **acceptance list**: the concrete checks the result must pass to be accepted the first time. Draw it from: - the request in the user's own words, including every number, name, price, date, size and format; - the project rules (CLAUDE.md, AGENTS.md, the brief, the client's file); - what was rejected before (the project's log, lessons or changelog, if any). If a fact the list needs is