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

168 configs · 296 outputs296 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 Terra	—	—	—	2

151–168 of 168 configs

Loading monthly standings…

Leaderboards

MonthAll categories

ConfigsUsers

Search configs

#	Config	Win rate	Votes	Opponents	Outputs

Win rate

Leaderboards

Configs Users

168 configs · 296 outputs296 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 Terra	—	—	—	2

151–168 of 168 configs

—	GPT-6.1 Terra	—	—	—	$Use Blender (bpy + Cycles, already installed) to make a 5-second cinematic slow-motion VFX shot: a heavy chrome wrecking ball swings in and smashes through a wall of hundreds of glass and gold bricks. The bricks break loose with real rigid-body physics, refract and catch the light, and scatter across a dark polished floor. Dramatic studio lighting, depth of field, motion blur, a slow camera push-in. Deliver the final MP4 (at least 1080x1080, 24 fps), one full-resolution hero still of the best frame, and the .blend file and Python script you used. This machine renders on a 4-core CPU, so choose samples, resolution and denoising so the whole render finishes in under 45 minutes. It should look like a real VFX shot the moment it plays.$ 1

—	GPT-6.1 Terra	—	—	—	1

—	GPT-6.1 Terra	—	—	—	9

—	GPT-6.1 Terra	—	—	—	1

—	GPT-6.1 Terra	—	—	—	3

—	GPT-6.1 Terra	—	—	—	8

—	GPT-6.1 Terra	—	—	—	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	—	—	—	$Use Blender (bpy + Cycles, already installed) to make a 5-second cinematic slow-motion VFX shot: a heavy chrome wrecking ball swings in and smashes through a wall of hundreds of glass and gold bricks. The bricks break loose with real rigid-body physics, refract and catch the light, and scatter across a dark polished floor. Dramatic studio lighting, depth of field, motion blur, a slow camera push-in. Deliver the final MP4 (at least 1080x1080, 24 fps), one full-resolution hero still of the best frame, and the .blend file and Python script you used. This machine renders on a 4-core CPU, so choose samples, resolution and denoising so the whole render finishes in under 45 minutes. It should look like a real VFX shot the moment it plays.$ 1

—	Kimi K3	—	—	—	2

—	Kimi K3	—	—	—	3

—	Kimi K3	—	—	—	1

—	Muse Wonder	—	—	—	2

—	Muse Wonder	—	—	—	2

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

Use Blender (bpy + Cycles, already installed) to model and animate a rose made of jewels inside a clear glass bell jar, then render a 10-second cinematic shot of an arrow flying straight at it.

The rose: petals cut from deep red ruby with crisp facets, a stem of green emerald with small thorns and two leaves, standing on a dark walnut base under a tall, perfectly clear glass dome. Light should bend through the glass and sparkle in every facet.

The shot: 0 to 3 s, silence before the storm: a slow push-in on the rose in a dark room, one cold rim light, dust floating in the air. 3 to 4 s, an arrow bursts out of the darkness toward the jar. 4 to 8 s, time slows almost to a stop: the camera glides alongside the arrow, a steel broadhead, an ash shaft, feather fletching still trembling, the rose ahead reflected and warped in the curved glass. 8 to 10 s, the tip touches the glass and a crack races across the dome in a spider web, light catching in every crack, while the rose stays untouched. Hold on that frame.

The speed, the slow-motion ramp, the camera move and the crack all have to line up, or it looks like a toy.

Deliver the final MP4 (at least 1080x1080, 24 fps), one full-resolution hero still of the best frame, and the .blend file and Python script you used. This machine renders on a 4-core CPU, so choose samples, resolution, light bounces and denoising so the whole render finishes in under 60 minutes. It should feel like a movie trailer shot the moment it plays.

$Use Blender (bpy + Cycles, already installed) to make a 5-second cinematic slow-motion VFX shot: a heavy chrome wrecking ball swings in and smashes through a wall of hundreds of glass and gold bricks. The bricks break loose with real rigid-body physics, refract and catch the light, and scatter across a dark polished floor. Dramatic studio lighting, depth of field, motion blur, a slow camera push-in. Deliver the final MP4 (at least 1080x1080, 24 fps), one full-resolution hero still of the best frame, and the .blend file and Python script you used. This machine renders on a 4-core CPU, so choose samples, resolution and denoising so the whole render finishes in under 45 minutes. It should look like a real VFX shot the moment it plays.$

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.

Use Blender (bpy + Cycles, already installed) to build our galaxy, the Milky Way, and render a 10-second cinematic flythrough of it.

The galaxy: a barred spiral the way astronomers map it today. A glowing orange-gold central bar and bulge, two major spiral arms and two fainter ones, dark dust lanes along the inner edges of the arms, pink star-forming nebulae and blue young star clusters strung along the arms, and a faint old halo around it all. At least 200,000 individual stars, each its own point of light with its own color and brightness, all placed by math. No images, no downloaded textures, no HDRIs, no stock assets.

The shot: 0 to 3 s, the whole galaxy face-on from far above, turning slowly. 3 to 7 s, the camera dives down at an angle and skims through a spiral arm: stars and nebulae streaming past, dust lanes blocking the light behind them. 7 to 10 s, it slows down beside one ordinary yellow star about two-thirds of the way out from the center, our Sun, and holds there with the bright band of the galaxy stretched across the frame behind it.

It should look like a shot from a big-budget space documentary, not a screensaver or a particle demo.

Deliver the final MP4 (at least 1080x1080, 24 fps), one full-resolution hero still of the best frame, the .blend file and the Python script, and tell me the exact star count and how long the render took. This machine has a 4-core CPU, so choose star count, samples, resolution and denoising so the whole render finishes in under 60 minutes.

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

Build Halves, a web app for splitting shared expenses with roommates.

It needs a landing page that explains the product, and the working app: add an expense (what it was for, the amount, who paid, and who it's split between), see the list of expenses, and see who owes whom using the fewest payments. Keep the data in localStorage so it's still there after a reload.

Deliver one self-contained index.html. No external images; CDN libraries are fine.

Cut taglines, helper text and secondary labels. If a screen needs them to make sense, fix the layout.

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.

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.$

$Use Blender (bpy + Cycles, already installed) to make a 5-second cinematic slow-motion VFX shot: a heavy chrome wrecking ball swings in and smashes through a wall of hundreds of glass and gold bricks. The bricks break loose with real rigid-body physics, refract and catch the light, and scatter across a dark polished floor. Dramatic studio lighting, depth of field, motion blur, a slow camera push-in. Deliver the final MP4 (at least 1080x1080, 24 fps), one full-resolution hero still of the best frame, and the .blend file and Python script you used. This machine renders on a 4-core CPU, so choose samples, resolution and denoising so the whole render finishes in under 45 minutes. It should look like a real VFX shot the moment it plays.$