Today · Next boss resets at 00:00 UTC, in Next boss in 05:27:49same boss for everyone·one shot·no retries to buyPlayer 1 · the experttrain in the dojo·prove it·get foundPlayer 2 · the builderone folder, a coach·your dashboard·ten systemsFree play · five minibosses · no loginone kata a day·2P mode in the guildBoss select · seven in rotation · one a day
GitThe Merge Warden
AgileThe Cadence
CI / CDThe Pipeline
CloudThe Nimbus
SecurityThe Gatekeeper
KubernetesThe Orchestrator
SREThe Firewatch
Today · Next boss resets at 00:00 UTC, in Next boss in 05:27:49same boss for everyone·one shot·no retries to buyPlayer 1 · the experttrain in the dojo·prove it·get foundPlayer 2 · the builderone folder, a coach·your dashboard·ten systemsFree play · five minibosses · no loginone kata a day·2P mode in the guild
Live·Next boss resets at 00:00 UTC, in Next boss in 05:27:49
One boss a day. Two ways in.
Player 1 proves it in five minutes. Player 2 ships it with a coach. They meet in the Guild.
Player 1 · the expertYou’ve been on call for years
A boss a day. Train. Fight. Top the board.
Ready?
A boss a day.
Fourteen questions, one shot. The clock is the only pressure and the run is over in five minutes.
Today’s bossone run per UTC day
Next boss resets at 00:00 UTC, in Next boss in 05:27:49
SuperUltraBeast
14 questions
·
one shot
·
no retries to buy
Fight
Prove it.
Your result is computed by the run, never typed. It lives on a proof page anyone can open — add it to LinkedIn.
Example · representative proof
SkillBoss · DevOps
DevOps Skill Proof
◆ The OrchestratorKubernetesUltra · Reached
Today’s boss, proved.
Illustrative example — not a real run. It mirrors the SkillBoss proof card; a real run renders your theme, tier, and seal.
High score
Your name on the board.
The Guild is the high-score table builders read when one of the ten systems holds them back. Your belts are your entry — one per hall, and a hall is one subject’s practice track.
Paste one prompt. Your agent becomes a delivery coach: ten gates from Hello World to ship day, proof before every GO. No account. The kit makes no network call.
Your agentthe coach speaks
> Hello World
COACH ONLINE — SkillBoss Start Guide v2
CONTRACT ......... loaded (CONTRACT-CARD.md, 12 rules)
GATE MAP ......... 10 gates, 00-KICKOFF -> 90-SHIP
STATE ............ creating state/ from templates
NEXT ............. Gate 00 intake — I ask, you answer, nothing gets built yet.
HUD
Your dashboard.
A run screen rendered from the journal on every commit, never by hand: gates passed, guards that fired, what to do next.
Your dashboardthe kit’s example run
YOU ARE HERE — TALLY · day 12 · ORANGE
run █████░░░░░ 5/10 gates · 2/3 milestones
map 00[x] 05[x] 10[x] 20[x] 40[>] 50[ ] 60[~] 70[ ] 80[ ] 90[ ]
now 40-TESTS — 3 of 5 boxes still open
next one command to green, the one the pre-push guard will run
after 50-CICD opens when you GO this gate
left 5 gates. You can stop any time; the record holds your place.
Final check
Ten systems. Then meet the experts.
Ten systems sink new apps. Your agent runs the check and reports what it found — the house records it, dated. When one holds you back, a builder with a belt is one door away.
Today’s boss · demo round20 s · one pick, no take-backs · the review shows after
Press one button. It locks. Then the review.
Take a shotBonus round
One question. Twenty seconds. One answer — then it locks.
Demo questionDEMO
Your CI rebuilds the entire Docker image on every commit, so builds are slow even when only app code changed. Which Dockerfile change cuts rebuild time the most?
20s
20 seconds remaining.
Speed breaks ties in the official run — it never adds to the score.
Demo content — it counts toward no run, no score, no leaderboard.