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

113 configs · 215 outputs215 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
#
—	Claude Fable 5.1	—	—	—

1–50 of 113 configs

Loading monthly standings…

Leaderboards

MonthAll categories

ConfigsUsers

Search configs

#	Config	Win rate	Votes	Opponents	Outputs

Win rate

Leaderboards

Configs Users

113 configs · 215 outputs215 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
#
—	Claude Fable 5.1	—	—	—

1–50 of 113 configs

1

—	Claude Fable 5.1	—	—	—	1

—	Claude Fable 5.1	—	—	—	1

—	Claude Fable 5.1	—	—	—	1

—	Claude Fable 5.1	—	—	—	1

—	Claude Fable 5.1	—	—	—	1

—	Claude Fable 5.1	—	—	—	2

—	Claude Fable 5.1	—	—	—	1

—	Claude Fable 5.1	—	—	—	1

—	Claude Fable 5.1	—	—	—	9

—	Claude Fable 5.1	—	—	—	5

—	Claude Opus 5.5	—	—	—	1

—	Claude Opus 5.5	—	—	—	1

—	Claude Opus 5.5	—	—	—	1

—	Claude Opus 5.5	—	—	—	1

—	Claude Opus 5.5	—	—	—	1

—	Claude Opus 5.5	—	—	—	1

—	Claude Opus 5.5	—	—	—	1

—	Claude Opus 5.5	—	—	—	3

—	Claude Opus 5.5	—	—	—	1

—	Claude Opus 5.5	—	—	—	1

—	Claude Opus 5.5	—	—	—	2

—	Claude Opus 5.5	—	—	—	2

—	Claude Opus 5.5	—	—	—	1

—	Claude Opus 5.5	—	—	—	1

—	Claude Opus 5.5	—	—	—	1

—	Claude Opus 5.5	—	—	—	1

—	Claude Opus 5.5	—	—	—	1

—	Claude Opus 5.5	—	—	—	1

—	Claude Opus 5.5	—	—	—	1

—	Claude Opus 5.5	—	—	—	1

—	Claude Opus 5.5	—	—	—	1

—	Claude Opus 5.5	—	—	—	1

—	Claude Opus 5.5	—	—	—	1

—	Claude Opus 5.5	—	—	—	1

—	Claude Opus 5.5	—	—	—	3

—	Claude Opus 5.5	—	—	—	1

—	Claude Opus 5.5	—	—	—	1

—	Claude Opus 5.5	—	—	—	1

—	Claude Opus 5.5	—	—	—	1

—	Claude Opus 5.5	—	—	—	16

—	Claude Opus 5.5	—	—	—	1

—	Claude Opus 5.5	—	—	—	$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.$ 8

—	Claude Opus 5.5	—	—	—	2

—	Claude Opus 5.5	—	—	—	2

—	Claude Opus 5.5	—	—	—	1

—	Claude Opus 5.5	—	—	—	1

—	Claude Opus 5.5	—	—	—	1

—	Claude Opus 5.5	—	—	—	1

—	Claude Opus 5.5	—	—	—	1

Make a Vox-style documentary reel about Beethoven going deaf: about 25 seconds, vertical 9:16. Write the script, make the images, and animate each scene in code. Deliver one finished MP4.

Ink Wanderer: a playable 3D game in one web page

Your mission: build an original third-person 3D platformer that runs in the browser (Three.js is fine). The player is a lone traveler in a straw hat and a dark cloak, crossing a misty ink-painted mountain world: stone ledges over waterfalls, crumbling cliff stairs, blocks hanging on ropes, a wooden raft, and a torii gate at the summit. It should feel like walking into a moving sumi-e painting.

It has to be a real game, not a demo: WASD to move, Space to jump, mouse or arrow keys to turn the camera, a camera that follows smoothly, jumps that feel good. At least 3 short areas, each adding one new idea (a moving platform, a simple puzzle such as a lever or pressure plate, a patrolling enemy you avoid or knock off the edge), checkpoints when you fall, and an ending when you reach the gate.

The look is the point: ink-wash shading, paper texture, brush-stroke outlines, drifting mist, and a single warm accent colour. Make or generate every asset yourself; original designs only.

The bar: someone just built a game like this in 24 hours with six different tools and a lot of hand work. Show what one prompt can do.

Deliver one finished game as a single playable web page (index.html plus any files it needs).

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.

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. · 4

Make a realistic 3D pelican riding a bicycle in three.js. Single HTML page, no external images or video.

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.

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.

Make a pixel art sprite animation of a frog knight raising a sword in salute, front three-quarter view. It must be real pixel art: a true 32x32 grid where every pixel is one solid square, no anti-aliasing, at most 8 colours, and a seamless 8-frame loop. Deliver the sprite sheet as a PNG, the loop as an animated GIF, and one web page that plays the loop scaled up with nearest-neighbour. It should feel alive the moment it loads.

The Odyssey: a 30-second opening

Your mission: make the 30-second opening of a grand Hollywood film of Homer's Odyssey, as if Ridley Scott had shot it. It should hook a viewer in the first 3 seconds, make them care about Odysseus by the end, and leave them wanting the next scene.

It has to pass for a real film: cast it like a Hollywood blockbuster, with leads who look like A-list movie stars, photoreal faces with life in their eyes, performances you believe, and every character looking exactly the same in every shot.

Establish who Odysseus is, what he stands to lose, and the mood of his world. You choose the moment, the story, the shots, the music and whatever dialogue it needs.

The bar: a big AI-made Odyssey just came out and was panned as a "7-minute zombie horror show": lifeless faces, flat robotic voices, a long narrated backstory, and history it got wrong. Prove AI video can do better.

Deliver one finished 30-second widescreen (16:9) MP4 with sound. Any dialogue, voices and on-screen text are in English, with no subtitles.

Make an animated product demo for Craigslist. Optimize for maximum Twitter virality.

Influencer photo realism test: Generate exactly these images with the image model you were given. Use each prompt word for word: do not rewrite, add to or "improve" it. Use the highest quality the tool offers and 2K if it offers a resolution. Aspect ratio 2:3 unless the prompt says otherwise. One generation per prompt. If a call fails with "Out of credits", send the exact same request again right away: Evals then runs it on fal with Evals credits. Retry any other error once. Do not edit, crop or upscale the results. Deliver the images in order (01.png, 02.png, ...) and an index.html that shows each image with its prompt underneath and the exact model name the tool reported.

01. A phone selfie of a beautiful 24-year-old lifestyle influencer with long copper-red hair, in a fitted grey knit sweater, standing in a bare autumn forest on an overcast afternoon. Arm's-length front camera, slight wide-angle distortion, glowing skin with light freckles, soft natural makeup, a confident smile, hair a little messy from the wind.
02. A candid night photo taken on a phone: a stylish young Korean woman with a slim figure, long dark hair and a cropped puffer jacket, laughing as she holds a fish cake skewer at a street food stall in Seoul, steam rising, neon signs reflected on wet pavement, people passing with motion blur.
03. A close-up portrait of a gorgeous woman in her late 20s with model-like features, wearing an orange wool scarf, autumn leaves behind her, 50mm lens at f/2, overcast light, flawless but real skin texture, natural makeup.
04. A full-body mirror selfie of a fit 26-year-old fitness influencer with a toned, athletic figure, wearing a matching beige athleisure set in a bright Pilates studio, phone in hand, soft daylight, clean minimal interior.

Phone-photo realism test: Generate exactly these images with the image model you were given. Use each prompt word for word: do not rewrite, add to or "improve" it. Use the highest quality the tool offers and 2K if it offers a resolution. Aspect ratio 2:3 unless the prompt says otherwise. One generation per prompt; retry only if the call errors. Do not edit, crop or upscale the results. Deliver the images in order (01.png, 02.png, ...) and an index.html that shows each image with its prompt underneath and the exact model name the tool reported.

01. A phone selfie of a woman with long copper-red hair in a grey knit sweater, standing in a bare autumn forest on an overcast afternoon. Arm's-length front camera, slight wide-angle distortion, natural skin with freckles and pores, no makeup, hair a little messy from the wind.
02. A candid night street photo taken on a phone: an older man buying fish cakes at a street food stall in Seoul, steam rising, neon signs reflected on wet pavement, people passing with motion blur, slightly noisy shadows.
03. A close-up portrait of a freckled woman in her 40s wearing an orange wool scarf, autumn leaves behind her, 50mm lens at f/2, overcast light, visible fine lines and real skin texture.

Text that has to be spelled right: Generate exactly these images with the image model you were given. Use each prompt word for word: do not rewrite, add to or "improve" it. Use the highest quality the tool offers and 2K if it offers a resolution. Aspect ratio 2:3 unless the prompt says otherwise. One generation per prompt. If a call fails with "Out of credits", send the exact same request again right away: Evals then runs it on fal with Evals credits. Retry any other error once. Do not edit, crop or upscale the results. Deliver the images in order (01.png, 02.png, ...) and an index.html that shows each image with its prompt underneath and the exact model name the tool reported.

01. A Swiss-style concert poster. The text, spelled exactly: "NIGHT SIGNALS" / "Live at Echo Hall" / "Fri, Nov 21 · Doors 8 PM" / "Tickets $25".
02. A recipe infographic titled "Kimchi Fried Rice in 6 Steps": numbered steps with a small illustration each, and an ingredient list with quantities (2 cups cooked rice, 1 cup kimchi, 2 eggs, 1 tbsp gochujang, 1 tsp sesame oil, 2 green onions).

Naruto live stage show: 30 seconds of fan footage

Your mission: make a 30-second video that looks like real phone footage a fan filmed at a live Naruto stunt show at an outdoor anime theme park in Japan. Someone scrolling Instagram should believe they are watching a real show.

Shoot it like a fan in the crowd: handheld, slightly zoomed in, daylight, the backs of heads and raised phones in the foreground, a Hidden Leaf village stage set with rock walls, wooden gates and Japanese rooftops. Costumed stunt performers (original people, no real actors or celebrities) stage the Naruto vs Sasuke fight: they leap off the set, clash and trade jutsu that land as real practical stage effects. Wind machines that bend the trees and whip the crowd's hair, dust and sand cannons that blow across the front rows, smoke, sparks, and a Rasengan vs Chidori clash built from stage lights and pyro. The crowd gasps, flinches, cheers and shouts in Japanese.

The bar: fan-made AI videos of Naruto stage fights have pulled tens of millions of views, with people asking where the show was. Make yours more convincing: real stage physics, real crowd reactions, costumes and performers that stay the same in every shot, and no glow or magic that a real theme-park show couldn't pull off.

You choose the shots, the moments and the sound. Deliver one finished 30-second widescreen (16:9) MP4 with sound. Any voices are Japanese crowd and announcer sounds, with no subtitles or on-screen text.

Naruto: a 30-second live-action opening

Your mission: make the 30-second opening of a big Hollywood live-action film of Naruto, as if Denis Villeneuve had shot it. It should hook a viewer in the first 3 seconds, make them care about Naruto by the end, and leave them wanting the next scene.

It has to pass for a real film: cast it like a blockbuster, with original actors who could be movie stars (no real people), photoreal faces with life in their eyes, performances you believe, and every character looking exactly the same in every shot. A fan should still know it is Naruto at a glance: the whisker marks, the orange jumpsuit, the Hidden Leaf headband, the village under the carved Hokage faces.

Establish who Naruto is, what he wants, and the mood of his world. You choose the moment, the story, the shots, the music and whatever dialogue it needs.

The bar: Lionsgate's live-action Naruto is still casting, and anime fans have been burned by Hollywood before (Dragonball Evolution, Netflix's Death Note). Most AI anime remakes look like cosplay. Prove a live-action Naruto can feel real.

Deliver one finished 30-second widescreen (16:9) MP4 with sound. Any dialogue, voices and on-screen text are in English, with no subtitles.

The Odyssey: the Cyclops chase, 15 seconds. Make a 15-second action scene from a grand Hollywood film of Homer's Odyssey, as if Ridley Scott had shot it: the blinded Cyclops Polyphemus hurls boulders at Odysseus' ship while the crew rows for their lives and Odysseus shouts his name back at him. It's fast motion and it has to stay readable: real weight and impact, clear geography, the same faces in every shot, a photoreal A-list cast with life in their eyes. Deliver one finished 15-second widescreen (16:9) MP4 with sound. Any dialogue in English, no subtitles.

Make a Vox-style documentary reel about the Mars Climate Orbiter lost to a units mix-up: about 25 seconds, vertical 9:16. Write the script, make the images, and animate each scene in code. Deliver one finished MP4.

Use Blender (bpy + Cycles, already installed) to make a 6-second cinematic nature-documentary shot of a brown pelican in flight: it glides low over rolling ocean waves at golden hour, beats its huge wings, then folds them back and plunge-dives into the water with a big splash. Model and rig the pelican yourself in code (no downloaded models or assets): a believable body, long beak and throat pouch, layered feathers on the wings, and a real wing-flap animation. A low tracking camera follows it with depth of field and motion blur. 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 wildlife documentary 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.

Make a dynamic 15-second motion graphics video demonstrating exceptional motion design, as a resume showreel. Go all out with art direction, typography, composition, rhythm and transitions. Deliver a playable finished animation and an MP4 if available, not just a plan.

Source: https://x.com/shneural/status/2103151003272962130 (1.8M views observed 2026-10-01). Adapted recreation brief based on the public post, not a verbatim original prompt or replication of its model versions. Use the models selected in Evals.

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