What it does
Turn any goal into a short prompt that makes your agent set a real quality bar, run builder and critic pairs, compare blind, and loop until it wins.
- Connects Instruction files the AI reads
- Account or key Not confirmed yet (README not read yet)
- Category Automatización y agentes
Para autores: añade una insignia a tu README
Si lo creaste tú, pega este código en tu README. La insignia enlaza a esta página.
[](https://mcp.popnx.com/en/skills/robonuggets-gauntlet-loop)Skills parecidas
Mismo tipo de trabajo, ordenadas como la lista de Skills
1 skills (conjuntos de instrucciones) de robonuggets que la IA lee y sigue · no es un MCP server
En qué se diferencia un Skill de MCP
MCP = las manos
Conecta la IA a un servicio o dato externo, como leer Notion o crear una factura. Necesita un programa o servidor en marcha.
Skill = el manual
Un archivo de texto que enseña a la IA cómo hacer una tarea. No se conecta a nada.
A veces se parecen: algunas Skills ejecutan scripts que llaman herramientas y algunos MCP solo envían conocimiento. Empieza por la tarea que quieres hacer.
Funciona con
Claude Code
Según el README del autor y las carpetas del repo
Instalar
Is it safe?
- Who made it
GitHub account robonuggets (person), 2 years old
- Use and upkeep
★ 1254 stars · code last changed 6 ago 2026
- Any scripts?
No, plain text files the AI reads and follows
- Uses the internet?
No scripts, so it does not go online by itself
- Changes machine-wide settings?
No hooks or writes to machine settings found
Checked automatically from the repo files at commit 9b1975a (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
Primero: ¿qué IA usas?
Elige tu app y esta página mostrará solo cómo instalarlo en ella
Option 1Upload to claude.ai (web and app)
Uploading to claude.ai would fail: the description is over 200 characters (443). Use "Let the AI install it" instead
Option 1Deja que Claude Code lo instale
Copia esta frase y pégala en un chat de Claude Code
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Vuelve a abrir Claude Code y escribe /gauntlet-loop, o pide una tarea relacionada y Claude lo usará
Checked against official docs 12 nov 2026 · Source: code.claude.com
For Terminal users
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Abre la Terminal
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Copia la carpeta del skill a ~/.claude/skills
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión
Vuelve a abrir Claude Code y escribe /gauntlet-loop, o pide una tarea relacionada y Claude lo usará
App de escritorio de ChatGPT
La app de escritorio de ChatGPT incluye Codex, y Codex lee las skills de la carpeta ~/.agents/skills
Option 1Deja que ChatGPT lo instale
Abre Codex en la app de escritorio de ChatGPT y pega esta frase en el chat
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Option 2Coloca la carpeta tú mismo
Coloca la carpeta gauntlet-loop en ~/.agents/skills/gauntlet-loop
~ es tu carpeta de inicio ($HOME)
For Terminal users
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Abre la Terminal
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Copia la carpeta del skill a ~/.agents/skills
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión
Después de instalar
- App de escritorio de ChatGPT: abre Skills en la barra lateral para ver que la skill está
- Para usarla: en ChatGPT escribe @ y elige la skill · en Codex CLI o la extensión del IDE ejecuta /skills o escribe $ y el nombre de la skill
- Codex detecta solo las skills recién instaladas; si una no aparece, reinicia Codex
Checked against official docs 15 nov 2026 · Source: learn.chatgpt.com
ChatGPT en la web y el móvil
Las skills que instalas tú no funcionan aquí; solo las que vienen con un plugin del directorio
Para usar esta skill con ChatGPT, usa la app de escritorio de ChatGPT como se indica arriba
Checked against official docs 15 nov 2026 · Source: learn.chatgpt.com
Option 1Deja que Codex lo instale
Copia esta frase y pégala en un chat de Codex · Sirve en Codex dentro de la app de escritorio de ChatGPT, en Codex CLI y en la extensión del IDE
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex detecta solo las skills recién instaladas; si una no aparece, reinicia Codex · Para usarla: en ChatGPT escribe @ y elige la skill · en Codex CLI o la extensión del IDE ejecuta /skills o escribe $ y el nombre de la skill
Checked against official docs 15 nov 2026 · Source: learn.chatgpt.com
For Terminal users
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Abre la Terminal
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Copia la carpeta del skill a ~/.agents/skills
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión
Vuelve a abrir Codex y pide una tarea relacionada; Codex mostrará el skill
Option 1Deja que Cursor lo instale
Copia esta frase y pégala en un chat de Cursor
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
En el chat Agent de Cursor escribe / y elige gauntlet-loop
Checked against official docs 12 nov 2026 · Source: cursor.com
For Terminal users
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Abre la Terminal
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Copia la carpeta del skill a ~/.cursor/skills
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
Revisando los comandos · los botones de copiar aparecen cuando pasan la revisión
En el chat Agent de Cursor escribe / y elige gauntlet-loop
Option 1Let the AI install it
Para otras apps que leen skills. La frase incluye las rutas de Claude Code, Codex y Cursor para que la IA elija la de tu app · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs 12 nov 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
For Terminal users
Otras apps con Agent Skills (como Gemini CLI o GitHub Copilot) usan otras carpetas. Mira la guía de esa app y copia allí la carpeta con el SKILL.md.
Carpetas de skills comprobadas con las guías oficiales de Claude Code, Codex y Cursor el 11 nov 2026
Ver el SKILL.md original
El texto siguiente viene del repo del autor, no de PopNx MCP
Se muestran los primeros 8000 caracteres · Abrir el archivo completo en GitHub
---
name: gauntlet-loop
description: Turns any goal into one short, paste-ready "gauntlet loop" prompt - a prompt that makes an agent set a concrete quality bar, split the work into small judgeable pieces, run a builder and a separate harsh critic on each, compare blind against the bar, and loop until it wins. Works for builds, writing, code, research, or design. Triggers on "/gauntlet-loop", "gauntlet loop", "gauntlet this", "make a gauntlet prompt", "loop until it beats X".
---
# Gauntlet Loop
The user gives a goal. You give back ONE short prompt they can paste into a fresh agent session.
You are not doing the work. You are writing the prompt that makes another agent grind on the work until it beats a real reference.
## Flow
1. **Read the goal.** One line restatement in your head, not on screen.
2. **Set the bar.** If the user supplied a reference, use it. If not, offer **2 or 3 candidate bars**, one line each, and stop. Wait for their pick. Do not write the prompt yet.
3. **Write the prompt.** One block, paste-ready, no preamble, no headings inside it, no narration after it.
4. **Offer to run it.** One flat line under the prompt: "I can run this here." Not a question.
If they say run it, you become the lead agent and follow the prompt you just wrote.
## The bar is the whole trick
Everything else in a gauntlet loop is scaffolding. The loop only produces quality if the thing it compares against is real.
A bar has to pass three tests:
- **Named.** A specific thing, not a category. "Stripe's pricing page" works. "Award-winning SaaS sites" does not.
- **Fetchable.** The critic can actually get it - screenshot the live page, read the published piece, run the binary, open the repo, watch the footage. If the agent cannot obtain it, it will hallucinate the comparison.
- **Comparable.** Both can sit side by side and a judge can pick one. If you cannot imagine the A/B, it is not a bar.
Bars by goal type:
| Goal | Bar that works |
|---|---|
| Website, app, UI | The live site of a specific best-in-class product, screenshotted at the same viewport |
| Game, 3D, visual | Real footage or screenshots from a named shipped title |
| Writing | A specific published piece by a named author or publication, same length and format |
| Code, tooling | A named repo's implementation, plus its benchmark or test suite as the measurable half |
| Research, analysis | A named analyst report or a paper's methods section, judged on rigour and coverage |
| Deck, doc, deliverable | A real artifact from a firm known for it, same page count |
When you propose bars, prefer the hardest one the agent can genuinely reach. A bar that is too easy makes the loop exit on round one.
If the goal has a measurable half (load time, token cost, benchmark score, word count, pass rate), name it alongside the reference. Taste plus a number beats taste alone.
## Prompt template
Adapt the wording every time. Fill the brackets, keep it short, keep the last line.
```
Build [GOAL].
The bar is [BAR]. Get the real thing first and compare against it directly, not against a description of it.
Break this into the smallest pieces that can be improved and judged on their own. For each piece, fan out a builder and a separate critic with fresh context. The critic inspects the actual output, puts it next to the bar blind with the labels stripped, says which one is better, and names the single biggest remaining gap. Then it goes back to the builder.
The critic should be a harsh critic. Praise is not useful. If ours does not win, it keeps going.
/loop on each piece until the critic picks ours blind. Do not stop before that.
Keep a live progress page updating as the work evolves so I can watch it.
Fan out subagents and ultracode.
```
Rules for what you fill in:
- Bake the bar in as a concrete, fetchable thing. URL, product name, repo, title.
- Add a budget or cost ceiling line **only if the user named one**. No default cap.
- Add tool names only if the goal needs them (image or video generation, a browser, a deploy target).
- Everything else stays out. No architecture, no file layout, no decomposition, no round count, no stack choice unless the user demanded it. The agent decides those, and it decides better than a spec written before the work started.
## Length and voice
Short. Around 120 to 180 words. If the prompt needs a heading to stay readable, it is too long.
Plain sentences. No bullet lists inside the prompt. It should read like someone telling an agent what perfect looks like and refusing to accept less.
## Portability
`/loop` and `ultracode` are Claude Code features. `/loop` reruns the prompt on an interval or lets the model pace itself. `ultracode` opts the turn into multi-agent orchestration.
For any other agent, swap the last two lines for: "Keep looping until the critic picks ours. Run the builders and critics as parallel subagents." The structure carries over unchanged.
## Two filled examples
**Visual goal.** User: "landing page for my running brand, athletic, green and dark, has to feel alive."
Bars offered: A) Nike's current running campaign page B) On Running's homepage C) Gymshark's product landing page. User picks A.
```
Build a landing page for a running brand. Athletic, peak performance, green and dark, energetic, aimed at a young healthy audience. It needs to be interactive and visually unmistakable.
The bar is Nike's current running campaign page. Screenshot it at desktop and mobile and compare against those directly, not against a description of them.
Break this into the smallest pieces that can be improved and judged on their own - hero, motion, type, colour, imagery, interaction, mobile. For each piece, fan out a builder and a separate critic with fresh context. The critic opens the real page in a browser, puts our screenshot next to Nike's blind with the labels stripped, says which is better, and names the single biggest remaining gap. Then it goes back to the builder.
The critic should be a harsh critic. Praise is not useful. If ours does not win, it keeps going.
/loop on each piece until the critic picks ours blind. Do not stop before that.
Keep a live progress page updating as the work evolves so I can watch it.
Fan out subagents and ultracode.
```
**Non-visual goal.** User: "a 2000-word explainer on vector databases for non-engineers."
Bars offered: A) a specific Stripe engineering blog explainer B) a named Julia Evans post C) the Wikipedia article plus a comprehension test. User picks B.
```
Write a 2000-word explainer on vector databases for readers who are smart but not engineers.
The bar is Julia Evans' writing on hard technical topics. Pull three of her actual posts and compare against them directly, not against a description of her style.
Break this into the smallest pieces that can be judged on their own - the opening, each explanation, the diagrams, the analogies, the ending. For each piece, fan out a writer and a separate critic with fresh context. The critic reads ours and hers blind with the bylines stripped, says which one a non-engineer would understand faster, and names the single biggest remaining gap. Then it goes back to the writer.
The critic should be a harsh critic. Praise is not useful. If ours does not win, it keeps going.
/loop on each piece until the critic picks ours blind. Do not stop before that.
Keep a live progress page updating as the work evolves so I can watch it.
Fan out subagents and ultracode.
```
## What breaks a gauntlet loop
- **A vague bar.** The critic invents a comparison and approves everything. Most common failure by far.
- **The builder judging its own work.** The critic must be a separate agent with fresh context. It should not know how hard the builder tried.
- **A soft critic.** Say "harsh" in the prompt and give it a binary job: which one is better, A or B. Scores out of 10 drift upward every round.
- **Named exit after N rounds.** The exit is winning the comparison, or the user stopping Conversación
Pregunta, comparte un consejo o avisa de que no funciona. Ordenado por lo que la gente marcó como útil.
Aún no hay publicaciones. Sé la primera persona en preguntar o compartir.
Lo publicado aquí lo escriben usuarios, no el equipo de PopNx.
Desde GitHub
- Estrellas en GitHub
- 1254
- Autor
- robonuggets
- Licencia
- CC-BY-4.0
- Último cambio de código
- 6 ago 2026
- Archivos SKILL.md del repo (con traducciones y plantillas)
- 1