bake-off
Skill0 starsChanged 7 months agoMITView on GitHub
Generates N parallel implementations of a prompt using sub-agents, presents them for comparison, and iterates until the user selects a winner to merge back.
- Deletes or force-pushes
- Installs packages
2 other projects use a version of this.
Adopted by
Most recently taken up by
- CorvusWing/CorvusWingtheir own version, first seen Nov 8, 2026
- Ahsan-ire/rag-pipeline-v1their own version, first seen Oct 12, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- CorvusWing/CorvusWing★ 1same name
- Ahsan-ire/rag-pipeline-v1★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 8 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
When the user invokes /bake-off [prompt], follow this sequence.
- Distinctive: line 22
When ambiguous between 1 and 2, prefer 2 (screenshots — it still allows for a running webserver).
- Distinctive: line 24
Determine base port: read the environment's configuration file / code for the default webserver port, the web servers will add an increment …
- Very specific: line 35
Start the container: cd .bakeoff/option-<i> && PORT=<host_port> CONTAINER_NAME=<name>-bakeoff-<i> make start
- Distinctive: line 40
Pause: Ask which option to keep, or what feedback/combination to apply.
- Very specific: line 103
URL in image labels: When annotating comparison images, include the live URL in each option's label (e.g.
- Distinctive: line 121
Pause: Ask which to proceed with.
- Distinctive: line 129
After each pause, apply the Anchor + Jitter pattern:
- Distinctive: line 151
When the user selects a winner and signals they are done:
- Distinctive: line 159
If the winner worktree has commits beyond the original branch (code was changed):
- Distinctive: line 164
If the winner is the unmodified original branch: nothing to merge — just clean up.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Bake-Off Workflow
When the user invokes /bake-off [prompt], follow this sequence.
0. Parameter Extraction
Determine N: Parse the prompt for an explicit count ("show me 2", "3 versions"). Default N = 4.
Determine Category by matching prompt signals:
| Category | Signals |
| 1 – UI Live Demo | "live", "running", "interact", "click around", "hot reload" |
| 2 – UI Screenshots | "screenshot", "mockup", "how it looks", "side-by-side", "show me the UI" |
| 3 – Raw Code / Logic | no UI mention; implementation, function, algorithm, module |
When ambiguous between 1 and 2, prefer 2 (screenshots — it still allows for a running webserver).
Determine base port: read the environment's configuration file / code for the default webserver port, the web servers will add an increment off this to set their own port
Category 1: UI Features (Live Demo)
- Fan-Out: Dispatch
Nsub-agents in parallel. Brief each agent with:- Their option number
i, assigned host portPORT + (i - 1), and a distinct UX approach (vary: layout, interaction model, visual density, data presentation, etc.) - Instructions:
- From the main workspace root:
git worktree add .bakeoff/option-<i> -b bakeoff-option-<i> - Implement the approach in
.bakeoff/option-<i>/ - Start the container:
cd .bakeoff/option-<i> && PORT=<host_port> CONTAINER_NAME=<name>-bakeoff-<i> make start - Report back: approach description, URL (
http://localhost:<host_port>), any caveats
- From the main workspace root:
- Their option number
- Terminal Output: Markdown table — Option # | Approach | URL | Status
- Pause: Ask which option to keep, or what feedback/combination to apply.
- Proceed to Iteration Loop.
Category 2: UI Screenshots
One-time Playwright setup (run once per session in any running container, don't reinstall playwright if already installed and available):
pip install playwright requests && playwright install chromium- Fan-Out: Dispatch
Nsub-agents in parallel. Brief each agent with:- Their option number
i, assigned host portPORT + (i - 1), and a distinct approach - Instructions:
git worktree add .bakeoff/option-<i> -b bakeoff-option-<i>- Implement the approach in
.bakeoff/option-<i>/ cd .bakeoff/option-<i> && PORT=<host_port> CONTAINER_NAME=<name>-bakeoff-<i> make start- Take screenshots (script runs inside container on internal port 8282, handles dev_login auth itself):
PNGs land inCONTAINER_NAME=<name>-bakeoff-<i> make exec -- \ python /script/that/logs/you/in/to/your/server \ --base-url http://localhost:8282 \ --out-dir /app/screenshots.bakeoff/option-<i>/screenshots/on the host (via the/appworkspace mount). - Report back: approach description, list of screenshot filenames captured
- Their option number
Fan-In — build comparison images: Once all agents finish, build a comparison grid for each captured page. Prefer a 2×2 grid for N=4 (matches common 16:9 monitor aspect ratio). For other N values, choose the layout closest to 16:9. Use Pillow (imagemagick
convertis often unavailable on the host). Annotate each panel with a label bar (dark background, white text) at the top containing the option number, live URL, and short approach name.from PIL import Image, ImageDraw, ImageFont import math def make_grid(panels, cols): rows = math.ceil(len(panels) / cols) w = max(p.size[0] for p in panels) h = max(p.size[1] for p in panels) grid = Image.new("RGB", (w * cols, h * rows), (240, 240, 240)) for idx, panel in enumerate(panels): grid.paste(panel, ((idx % cols) * w, (idx // cols) * h)) return grid # For N=4: make_grid(panels, cols=2) # 2×2 # For N=3: 2 on top, 1 centered on bottom — closest to 16:9, avoids a stretched single row # For N=2: make_grid(panels, cols=2) # single rowN=3 layout implementation (2 top, 1 centered bottom):
def make_grid_3(panels, bg=(20, 20, 20)): w = max(p.size[0] for p in panels) h = max(p.size[1] for p in panels) grid = Image.new("RGB", (w * 2, h * 2), bg) grid.paste(panels[0], (0, 0)) grid.paste(panels[1], (w, 0)) grid.paste(panels[2], (w // 2, h)) # centered return gridTerminal Output: Markdown table — Option # | Approach | URL | Pros | Cons. Always show absolute paths to comparison images (e.g.
/home/user/project/.bakeoff/visuals/comparison-stack-list.png) so the user can ctrl-click them directly in the terminal.URL in image labels: When annotating comparison images, include the live URL in each option's label (e.g.
Option 2: Kebab — localhost:9676/stack-list) so the user can navigate to the running container directly without hunting for the port.Playwright and overlays: Angular Material menus (and other CDK overlays) render outside the component tree. Playwright captures them correctly with
full_page=Trueas long as you wait for the overlay panel selector (.mat-mdc-menu-panel,.cdk-overlay-container) before screenshotting. This is reliable — if a menu-open screenshot shows a closed menu, the wait was too short, not a fundamental Playwright limitation.- Pause: Ask which option to keep, or what feedback/combination to apply.
- Proceed to Iteration Loop.
Category 3: Raw Code & Logic
- Fan-Out: Dispatch
Nsub-agents in parallel, each optimizing for a different variable most relevant to the prompt (choose from: readability, execution speed, minimal dependencies, testability, idiomatic style, error-handling robustness). - Each agent writes to
.bakeoff/code/option-<i>.<ext>in the project workspace and reports: approach name, pros, cons, file path. - Terminal Output: Markdown table — Option # | Approach | Pros | Cons | File
- Pause: Ask which to proceed with.
- Proceed to Iteration Loop.
Iteration Loop
After each pause, apply the Anchor + Jitter pattern:
- One anchor agent holds the best result from the previous round unchanged. If the user selected a specific unmodified option, that worktree/code is the anchor. If the user asked to combine or synthesize options, the anchor holds your synthesis.
- N−1 jitter agents each receive the anchor as context but are explicitly told to explore independently — vary the approach, don't just refine the anchor. The goal is genuine variety, not herding toward one solution.
Jitter agent brief (include verbatim):
"Option X from the last round is attached as reference. Use it as a hint about what's working. Approach the problem from a different angle — do not simply refine Option X."
Response handling
| User response | Anchor | Jitter agents |
| Selects an option, requests more iterations | That option (unchanged) | Explore independently with anchor as hint |
| "Combine X and Y" | One synthesis of X+Y | Different weight distributions of the same combination |
| Directional feedback ("more minimal", "different approach to X") | Best previous option with feedback applied | Explore independently with feedback as constraint |
| "None of these" / no clear winner | None (no anchor) | All N agents re-fan-out fresh |
| Selects winner, says done/finished | — | Enter Completion |
Completion
When the user selects a winner and signals they are done:
- Stop all bakeoff containers (UI categories):
for i in $(seq 1 $N); do CONTAINER_NAME=<name>-bakeoff-$i make stop 2>/dev/null; done - Merge the winner back to the original workspace:
- If the winner worktree has commits beyond the original branch (code was changed):
git merge --squash bakeoff-option-<winner> git commit # write a message describing the winning approach - If the winner is the unmodified original branch: nothing to merge — just clean up.
- If the winner worktree has commits beyond the original branch (code was changed):
- Clean up all temporary state:
for i in $(seq 1 $N); do git worktree remove --force .bakeoff/option-$i git branch -D bakeoff-option-$i done rm -rf .bakeoff/ - Confirm to the user that the winning approach is merged and all bakeoff state is removed. {code}
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

