Explore

Outputs Tasks Skills

Compare Community Leaderboards

Loading runs…

Account

Loading monthly standings…

Leaderboards

MonthAll categories

ConfigsUsers

Search configs

#	Config	Win rate	Votes	Opponents	Outputs

Win rate

Loading page…

Leaderboards

Configs Users

139 configs · 359 outputs359 unranked · incomplete evidence

Win rate

No rate to plot yetRates appear when public outputs receive valid comparison votes in this month.

Monthly configuration family standings from public Evals comparisons
#
—	GPT-6.1 Sol	—	—	—	1

101–139 of 139 configs

Loading monthly standings…

Leaderboards

MonthAll categories

ConfigsUsers

Search configs

#	Config	Win rate	Votes	Opponents	Outputs

Win rate

Leaderboards

Configs Users

139 configs · 359 outputs359 unranked · incomplete evidence

Win rate

No rate to plot yetRates appear when public outputs receive valid comparison votes in this month.

Monthly configuration family standings from public Evals comparisons
#
—	GPT-6.1 Sol	—	—	—	1

101–139 of 139 configs

—	GPT-6.1 Sol, GPT-6.1 Sol	—	—	—	1

—	GPT-6.1 Sol, GPT-6.1 Sol	—	—	—	1

—	GPT-6.1 Sol, GPT-6.1 Sol	—	—	—	1

—	GPT-6.1 Sol, GPT-6.1 Sol	—	—	—	1

—	GPT-6.1 Sol, GPT-6.1 Sol	—	—	—	1

—	GPT-6.1 Sol, GPT-6.1 Sol	—	—	—	1

—	GPT-6.1 Sol, GPT-6.1 Sol	—	—	—	1

—	GPT-6.1 Sol, GPT-6.1 Sol	—	—	—	2

—	GPT-6.1 Sol, GPT-6.1 Sol	—	—	—	2

—	GPT-6.1 Sol, GPT-6.1 Sol	—	—	—	1

—	GPT-6.1 Sol, GPT-6.1 Sol	—	—	—	1

—	GPT-6.1 Sol, GPT-6.1 Sol	—	—	—	1

—	GPT-6.1 Sol, GPT-6.1 Sol	—	—	—	1

—	GPT-6.1 Sol, GPT-6.1 Sol	—	—	—	3

—	GPT-6.1 Sol, GPT-6.1 Sol	—	—	—	1

—	GPT-6.1 Sol, GPT-6.1 Sol	—	—	—	1

—	GPT-6.1 Sol, GPT-6.1 Sol	—	—	—	2

—	GPT-6.1 Sol, GPT-6.1 Sol	—	—	—	1

—	GPT-6.1 Sol, GPT-6.1 Sol	—	—	—	1

—	GPT-6.1 Sol, GPT-6.1 Sol	—	—	—	2

—	GPT-6.1 Terra	—	—	—	9

—	GPT-6.1 Terra	—	—	—	3

—	GPT-6.1 Terra	—	—	—	10

—	GPT-6.1 Terra	—	—	—	1

—	Grok 4.7	—	—	—	1

—	Grok 4.7	—	—	—	3

—	Grok 4.7	—	—	—	1

—	Grok 4.7	—	—	—	$Build a spreadsheet app as one self-contained index.html (no external assets, no network). UI: a visible grid with columns A-Z and rows 1-1000, a formula bar, click a cell to edit, Enter commits, arrow keys move. It should look like a tool someone would actually use. Also expose this exact API on window.Sheet. It must stay in sync with the UI: - set(ref, text): enter text into a cell, as if typed. Empty string clears it. - get(ref): the computed value. A number for numeric results (JS number), a string for text and for errors, "" for empty cells. - getRaw(ref): exactly what was entered. - undo(), redo(): cover set, insertRow, deleteRow and fromCSV. A new edit clears the redo history. - insertRow(n), deleteRow(n): 1-based. Rows shift, and formulas are rewritten as Excel does. Both relative and $absolute references move with their cells. A reference to a deleted single cell becomes #REF! in the formula text (for example "=#REF!"). A range that loses a row shrinks. - toCSV(): RFC 4180 raw text (formulas as typed), rectangular up to the last non-empty row and column, rows joined by \n, no trailing newline. - fromCSV(text): replaces the whole sheet, starting at A1. Handles quoted commas, doubled quotes and newlines inside quotes. Formulas start with "=". Case-insensitive, whitespace ignored. - Operators: + - * / ^ & (text concat), postfix %, parentheses. ^ is right-associative. Unary minus binds tighter than ^, as in Excel, so =-2^2 is 4. - References: A1, $A$1, $A1, A$1. Ranges: A1:B3. - Functions: SUM, AVERAGE, MIN, MAX, COUNT, IF(cond, a, b). Conditions use = <> < > <= >=. - Text in double quotes. - Empty cells are 0 in arithmetic and "" in concat. Range functions skip text and empty cells. Numbers concat in plain form (5 & "x" is "5x"). - Errors, exact strings: #DIV/0!, #REF!, #CYCLE!, #NAME? (unknown function), #VALUE! (text in arithmetic). Errors propagate, including through range functions. Every cell in a cycle, and every cell depending on one, shows #CYCLE!. Fixing the cycle recovers them. - Cells recalculate automatically. With 10,000 filled cells and a SUM over them, editing one input must finish recalculating within 1 second. A dependency chain 1000 cells deep must work. A numeric cell typed as 42 or 3.5 is a number. Anything else not starting with "=" is text.$ 1

—	Kimi K3	—	—	—	1

—	Kimi K3	—	—	—	1

—	Kimi K3	—	—	—	1

—	Kimi K3	—	—	—	3

—	Kimi K3	—	—	—	3

—	Kimi K3	—	—	—	2

—	moonshotai/kimi-k3.1-pro	—	—	—	1

—	Muse Wonder	—	—	—	2

—	Muse Wonder	—	—	—	2

—	Qwen3.8 Max (0902)	—	—	—	1

This dashboard looks AI-generated: https://raw.githubusercontent.com/heydamir/unslop/main/examples/dashboard.html (its card image is examples/assets/blob.webp in the same repo). Make it look designed, with its own character. Just do it, don't stop to ask me questions; make sensible assumptions and say what they are. Keep it one HTML file, then make a short video of it going from before to after.

Make a small arcade platformer game in one web page: a raccoon courier leaping across rainy neon rooftops, dodging security drones. Arrow keys move and jump, space attacks. All the art must come from the image model selected for this run: sprite sheets for the hero (idle, run, jump, attack), three enemies and a boss, plus a background. Cut the sheets into frames and animate them in the game. Do not draw characters in code. Add a HUD, a score, and win and game over screens. It should feel fun the moment it loads.

Make a 30-second paper cut-out animation that plays by itself in one web page: a little fox mail carrier cycles through a paper village at dusk, climbs a hill and hands a letter to the moon. All the art must come from the image model selected for this run: the fox and the bicycle as separate cut-out parts (head, body, arms, legs, wheels), plus houses, hills, trees, clouds and the moon as separate layers. Animate the cut-out parts like a paper puppet, with layered parallax and a slow camera pan. Do not draw characters or scenery in code. It should look handmade and charming the moment it loads, and loop.

Make a small arcade action game in one web page: a tiny ghost librarian defending a haunted library from flying cursed books. Arrow keys move, space attacks. All the art must come from the image model selected for this run: sprite sheets for the hero (idle, float, cast, hurt), three enemies and a boss, plus a background. Cut the sheets into frames and animate them in the game. Do not draw characters in code. Add a HUD, a score, and win and game over screens. It should feel fun the moment it loads.

Make a small arcade side-scrolling game in one web page: a jetpack penguin escaping an ice cream factory run by evil robot chefs. Arrow keys fly, space fires. All the art must come from the image model selected for this run: sprite sheets for the hero (idle, fly, fire, hurt), three enemies and a boss, plus a background. Cut the sheets into frames and animate them in the game. Do not draw characters in code. Add a HUD, a score, and win and game over screens. It should feel fun the moment it loads.

Make a small arcade horde survival game in one web page: an owl monk holding an autumn mountain temple against endless waves of paper lantern ghosts. Arrow keys move, space attacks. All the art must come from the image model selected for this run: sprite sheets for the hero (idle, run, attack, hurt), three enemies and a boss, plus a background. Cut the sheets into frames and animate them in the game. Do not draw characters in code. Add a HUD, a score, and win and game over screens. It should feel fun the moment it loads.

Make a small arcade action game in one web page: an otter knight clearing a flooded crypt of drowned skeletons. Arrow keys move, space attacks. All the art must come from the image model selected for this run: sprite sheets for the hero (idle, run, attack, hurt), three enemies and a boss, plus a background. Cut the sheets into frames and animate them in the game. Do not draw characters in code. Add a HUD, a score, and win and game over screens. It should feel fun the moment it loads.

Make a small arcade top-down racing game in one web page: a rubber duck captain racing bathtubs through a giant flooded house. Arrow keys steer, space boosts. All the art must come from the image model selected for this run: sprite sheets for the hero (idle, turn left, turn right, boost), three enemies and a boss, plus a background. Cut the sheets into frames and animate them in the game. Do not draw characters in code. Add a HUD, a score, and win and game over screens. It should feel fun the moment it loads.

Make a small arcade beat 'em up game in one web page: a punk pigeon fighting through a 1990s shopping mall full of rival seagull gangs. Arrow keys move, space attacks. All the art must come from the image model selected for this run: sprite sheets for the hero (idle, walk, kick, hurt), three enemies and a boss, plus a background. Cut the sheets into frames and animate them in the game. Do not draw characters in code. Add a HUD, a score, and win and game over screens. It should feel fun the moment it loads.

Make a small arcade vertical shooter game in one web page: a cat pilot in a paper biplane fighting origami warships above a sunset sea. Arrow keys move, space fires. All the art must come from the image model selected for this run: sprite sheets for the hero (idle, bank left, bank right, hit), three enemies and a boss, plus a background. Cut the sheets into frames and animate them in the game. Do not draw characters in code. Add a HUD, a score, and win and game over screens. It should feel fun the moment it loads.

Make a small arcade dungeon crawler game in one web page: a mole miner with a glowing pickaxe digging through a crystal cave full of lava beetles. Arrow keys move, space attacks. All the art must come from the image model selected for this run: sprite sheets for the hero (idle, run, swing, hurt), three enemies and a boss, plus a background. Cut the sheets into frames and animate them in the game. Do not draw characters in code. Add a HUD, a score, and win and game over screens. It should feel fun the moment it loads.

Make a 3D endless runner game in one web page: a hoverboard rider races through a futuristic neon city, along rooftops, through tunnels and across bridges. Left and right arrow keys switch between three lanes, up arrow jumps, down arrow slides. Dodge trains, barriers and drones, grab coins and power-ups (magnet, shield, double score), and the speed keeps rising. Add speed lines, light trails, a camera that shakes on near misses, a score and coin HUD, and start and game over screens with the best score. Make it look as polished as a mobile hit. It should feel fast the moment it loads.

Build a complex, cinematic 2D animation as a single standalone HTML file, using WebGL with GLSL shaders and a 2D Canvas. No external assets, images or libraries: draw and shade everything in code.

The scene: an original masked hero swings through a dense, towering city at golden hour, shot from a steep high angle looking down the street canyons. They fire glowing web lines that snap onto rooftops, swing in long arcs with real momentum, let go at the top of the arc, flip through the air and shoot the next line before they fall. The camera chases them through the buildings.

The city should feel enormous and alive: hundreds of buildings with lit windows, rooftop water towers and details, traffic far below, warm sunlight and long shadows, haze and depth. Use shaders for lighting, atmosphere and motion blur, and the 2D canvas for the hero, the web lines and particles. Swing physics should come from a real pendulum, not canned paths.

It should run on its own forever with no input, at 60 fps in a normal laptop browser, and feel fast and fun the moment it loads.

Make an animation of a pelican riding a bicycle. Single HTML page, no external images or video.

Make a browser game in one HTML file: a paper airplane gliding through a city at dusk.

The player steers the plane between rooftops, through open windows and under bridges, catching warm lights while the wind pushes back. A run lasts about two minutes and ends on a hill above the city where kites are flying, with a short ending scene and a score. Include a title screen, keyboard and touch controls, and sound made in code. It should feel like a small indie game someone would share, not a tech demo.

3D is welcome. You may use Three.js, but put it inside the file (no CDN links), so it opens offline with no network requests. No images, no other libraries. Write it in one go: don't open it in a browser or test it. Just deliver the file.

Create a 2D anime scene for the web. It must look completely like real Japanese anime, as if it were taken directly from a finished theatrical anime film. This is traditional-looking, hand-drawn 2D anime, not a 3D animation, a moving illustration, or a stylized web graphic.

Deliver the final result as a single, self-contained HTML file. Use any tools, libraries, references, guides, literally anything etc.

Use Studio Ghibli films as the art style reference for the design, line work, painted backgrounds, color, and atmosphere. Create an original giant robot as the main character. No people appear in the scene. Use any tools or techniques you want, including 3D, as long as the final result looks 100% like hand-drawn 2D anime.

SCENE
At sunrise, mist hangs over an abandoned forest. A giant robot has knelt here for so long that moss, wildflowers, and old trees have grown over its body. A small bird lands on its shoulder as the first ray of sunlight reaches its weathered face. Deep inside its chest, a faint light flickers on. The ground trembles and birds burst from the treetops. With a deep, creaking groan, the robot slowly rises as soil, vines, and leaves pour from its armor. It lifts its head toward a gap in the canopy. The engines ignite, sending a great ring of wind across the forest. The robot tears into the golden sky, leaving a curving trail of light and mist as leaves spiral down through the sunbeams.

ANIME QUALITY STANDARD
Every frame must look as if it was drawn by professional anime animators and painted by master background artists for a finished theatrical film.

Robot: A hand-drawn anime mecha that feels heavy, ancient, and full of personality, with cel-colored forms, chipped paint, rust, moss, and believable weathering. Keep it on-model from every angle, and let its posture and glowing eyes express emotion.
Line art: Confident, delicate, hand-inked anime line work with subtle variation in thickness and pressure.
Coloring: Traditional anime cel coloring with clean color areas, simple hard-edged shadows, and a soft, natural palette.
Backgrounds: Richly detailed, hand-painted anime backgrounds in a gouache style, with visible brushwork, natural color variation, layered foliage, and real depth.
Lighting: Golden sunrise light, colorful shadows, glowing mist, and soft atmosphere that unite the robot and background.
Animation: Authentic hand-drawn anime timing with real weight, strong key poses, natural holds, and overlapping movement in vines, grass, leaves, birds, and falling debris. The robot should rise slowly and feel massive, then launch with explosive power.
Direction: Cinematic anime shots, beautiful composition, thoughtful staging, and pacing that starts quietly, builds tension, and ends in a soaring climax.
IT MUST NOT LOOK LIKE
- 3D: No plastic materials, CGI shading, visible polygons, game-engine lighting, or computer-perfect perspective.
- SVG or vector art: No simple geometric shapes, perfect curves, uniform outlines, flat corporate illustration, or basic gradients.
- Web animation: No sliding layers, constant bobbing, floating parts, smooth software easing, or puppet-like joint rotation.

You are free to change any part of the prompt, if it would result, in better results.
- AI art: No warped shapes, melted details, flickering, or changing robot designs.
- Non-anime art: No Western cartoon designs, realistic rendering, soft painterly shading on the robot, or generic digital illustration.
- Amateur work: No stiff poses, empty backgrounds, repeated trees, muddy colors, clip art, placeholders, or unfinished details.

The result should feel awe-inspiring, nostalgic, and full of wonder, like the moment an old forgotten dream comes back to life. Before finishing, inspect random frames as still images. If any frame does not look completely like real 2D anime, keep improving it. Do not stop until every frame could pass as a still from a theatrical anime film.

I asked four AI agent setups for the same thing: a bottom sheet and a stack of swipeable cards, like in a mobile app, as one HTML page that works with mouse and touch, plus a 15-second video of someone dragging, flicking and dismissing them. Their results are attached as gestures-1 to gestures-4: a screenshot and the video for each. I'm not telling you which model made which.

Be the judge. Which one feels most like a real native app when you touch it, and why? Rank all four. Look at the motion: does the drag track the pointer, does a flick carry its speed, do things snap and settle naturally, can you catch something mid-animation, and does anything look broken. Some of them followed Emil Kowalski's gestures skill; say whether that made a real difference.

Deliver one self-contained HTML page: a two-line verdict at the top, then the rankings and short notes. Keep it short enough to read in two minutes. Don't stop to ask me questions; make sensible assumptions and say what they are.

Build a dancing Muse: a cute 3D plush mascot with a chubby body, a cream fluffy hood around a round peach face, two small black eyes, rosy cheeks and a tiny smile, short stubby arms and legs, wearing a red hockey jersey with white stripes and black shorts. It dances on its own as soon as the page opens: a real choreographed loop with bounces, arm waves, a spin, a hip sway and a big finish pose, under colorful stage lights with confetti. The fur should look soft and the moves should feel bouncy and alive, with squash and stretch. One self-contained HTML file, no external assets, and it should fill any window. It should feel joyful the moment it loads.

Build a fireworks show over a night city skyline in the browser (single HTML page, no external assets). The show runs by itself with peonies, willows, crossettes, heart shapes and a grand finale, lights reflecting in the river, smoke drifting, and the boom arriving a beat after the flash. Click anywhere to launch your own shell. It should feel jaw-dropping the moment it loads.

$Build a spreadsheet app as one self-contained index.html (no external assets, no network). UI: a visible grid with columns A-Z and rows 1-1000, a formula bar, click a cell to edit, Enter commits, arrow keys move. It should look like a tool someone would actually use. Also expose this exact API on window.Sheet. It must stay in sync with the UI: - set(ref, text): enter text into a cell, as if typed. Empty string clears it. - get(ref): the computed value. A number for numeric results (JS number), a string for text and for errors, "" for empty cells. - getRaw(ref): exactly what was entered. - undo(), redo(): cover set, insertRow, deleteRow and fromCSV. A new edit clears the redo history. - insertRow(n), deleteRow(n): 1-based. Rows shift, and formulas are rewritten as Excel does. Both relative and $absolute references move with their cells. A reference to a deleted single cell becomes #REF! in the formula text (for example "=#REF!"). A range that loses a row shrinks. - toCSV(): RFC 4180 raw text (formulas as typed), rectangular up to the last non-empty row and column, rows joined by \n, no trailing newline. - fromCSV(text): replaces the whole sheet, starting at A1. Handles quoted commas, doubled quotes and newlines inside quotes. Formulas start with "=". Case-insensitive, whitespace ignored. - Operators: + - * / ^ & (text concat), postfix %, parentheses. ^ is right-associative. Unary minus binds tighter than ^, as in Excel, so =-2^2 is 4. - References: A1, $A$1, $A1, A$1. Ranges: A1:B3. - Functions: SUM, AVERAGE, MIN, MAX, COUNT, IF(cond, a, b). Conditions use = <> < > <= >=. - Text in double quotes. - Empty cells are 0 in arithmetic and "" in concat. Range functions skip text and empty cells. Numbers concat in plain form (5 & "x" is "5x"). - Errors, exact strings: #DIV/0!, #REF!, #CYCLE!, #NAME? (unknown function), #VALUE! (text in arithmetic). Errors propagate, including through range functions. Every cell in a cycle, and every cell depending on one, shows #CYCLE!. Fixing the cycle recovers them. - Cells recalculate automatically. With 10,000 filled cells and a SUM over them, editing one input must finish recalculating within 1 second. A dependency chain 1000 cells deep must work. A numeric cell typed as 42 or 3.5 is a number. Anything else not starting with "=" is text.$