Four steps to
objective proof.
Pick → Build → Score → Ship. Each step is designed to capture what matters and ignore what doesn't.
Pick a problem.
Browse the Shipyard and find a real problem that interests you — building features, fixing production bugs, extending existing systems. These aren't toy exercises. They're drawn from the kind of work companies actually pay for.
BUILD
Ship a feature from scratch against a spec and a deadline.
DEBUG
Diagnose a broken codebase and land a working patch.
Clone and build.
One command clones the challenge repo, connects GoShip MCP, and starts Claude Code. The MCP server runs silently alongside your editor, observing how you work — prompting, iterating, debugging — without ever touching your source code.
No separate install step. No config files. Just run the command and start building.
$ claude mcp add goship -- npx -y @goship/mcp-server
● GoShip MCP server added
$ claude
● Claude Code ready. Start building.
Four dimensions. One score.
GoShip MCP observes your workflow (not your code) and scores across four dimensions: AI Fluency, Output Quality, Judgment, and Speed. Each one measures something different about how you work with AI — not just the output, but the process.
Composite Score
Your code stays yours.
We measure how you work, never what you build. No source code leaves your machine. Period.
Ship it. Prove it. Get paid.
Your score goes on your profile. Companies see it. Bounty winners get paid.