Claude Code Readiness Quiz

Score how set up your workflow is - and what to fix first.

  • $19 Free
  • 60 sec
  • No signup
1

Answer the setup questions

2

See your readiness score

3

Fix the top 3 it flags

You get: A readiness score plus your top 3 setup fixes, prioritized.

Score your setup

Answer all 7 questions. Your score and top fixes appear on the right.

1. CLAUDE.md

Do you have a CLAUDE.md that captures your project's conventions?

2. Permissions

Have you configured permissions (allow / ask / deny) for tools and commands?

3. Model choice

Do you match the model (Opus / Sonnet / Haiku) to the task?

4. Cost awareness

Do you have a sense of what your Claude Code usage costs?

5. MCP / extensions

Have you set up any MCP servers or custom extensions you actually use?

6. Workflow

Do you use a repeatable workflow - plan, then implement, then review?

7. Git hygiene

Do you commit often and use branches so the agent's work is easy to review and undo?

Your readiness

0 / 7

Answer all 7 questions to see your score and prioritized fixes.

This is a self-assessment, not a certification. It points you at the highest-impact setup gaps - the fixes are what actually move the needle.

Are you actually set up to build with Claude Code?

Most people install Claude Code, type a prompt, and start working - and it works, which is the trap. The gap between 'it runs' and 'it runs reliably, safely, and cheaply' is a handful of setup decisions that most users never make deliberately. This quiz scores seven of them: your CLAUDE.md, your permissions, your model choice, your cost awareness, your extensions, your workflow, and your git hygiene. Answer honestly and you get a readiness score plus your top three fixes, ranked by impact.

The seven dimensions of a solid setup

  • CLAUDE.md - the standing instructions loaded into every session. The single highest-leverage file in your setup.
  • Permissions - allow/ask/deny rules that decide what the agent can do without asking. The core of running it safely.
  • Model choice - matching Opus, Sonnet, or Haiku to the task instead of defaulting to one and overpaying or underpowering.
  • Cost awareness - knowing roughly what you spend and where the tokens go, so leaks get caught early.
  • MCP and extensions - the servers, skills, and subagents you actually use (and pruning the ones you do not).
  • Workflow - a repeatable plan-then-implement-then-review loop rather than 'build and hope'.
  • Git hygiene - frequent commits and clean branches so the agent's work is easy to review and trivial to undo.

Why these seven and not others

These are the dimensions where a small amount of setup produces an outsized, compounding return - and where skipping the setup quietly costs you every single session. A missing CLAUDE.md means re-explaining your conventions forever. Loose permissions mean either constant interruptions or unsafe actions. No cost awareness means surprise bills. No workflow means the agent confidently builds the wrong thing. Each one is cheap to fix once and expensive to leave broken, which is exactly what makes them worth scoring.

Fix the top three, then re-take it

Do not try to close every gap at once. The result ranks your fixes worst-first, so the top three are your highest-impact next steps. Do those, work for a week, then re-take the quiz. Readiness is a habit you build up, not a switch you flip.

What each score band means

  1. 80%+ (Dialed in) - foundations are strong. Sharpen the last edges and go deeper on extensions and workflow.
  2. 55-79% (Solid, with gaps) - it works, but a few important pieces are thin. Closing them moves you from 'works' to 'works reliably and cheaply'.
  3. 30-54% (Getting started) - you are running but leaving real leverage and safety on the table. Do the top three fixes first.
  4. Under 30% (Just beginning) - the perfect time to build good habits. Start with the top three, in order, and the rest follow.

Turn the fixes into action the same day

Every fix this quiz surfaces maps to a concrete next step, and most map to a free tool on this site you can use in a minute. Missing a CLAUDE.md points you at the CLAUDE.md generator. Unsure about model choice points you at the model picker. No cost visibility points you at the token cost calculator. Loose permissions point you at the permissions builder. The quiz is the diagnostic; the tools are the treatment - do not just read your gaps, close one right now.

Readiness is a moving target

Your setup that was dialed in six months ago may have drifted - a CLAUDE.md that bloated, MCP servers you no longer use, a model habit that no longer fits your work. Claude Code also keeps adding capabilities, which raises the ceiling on what 'ready' means. Re-take this quiz every so often, especially when a project changes shape or your bill jumps unexpectedly. Staying ready is cheaper than getting ready from scratch.

Frequently asked questions

  • Do I need to answer every question?

    Yes - the score and the prioritized fixes only appear once all seven questions are answered, because the ranking depends on comparing your weakest areas against each other. It takes about a minute.

  • What is the single most important thing to fix first?

    For most people it is a tight CLAUDE.md, since it loads into every session and shapes everything else. That said, the quiz ranks fixes worst-first for your specific answers, so trust the top item it flags for you.

  • Is a high score a certification of any kind?

    No. This is a self-assessment designed to point you at the highest-impact setup gaps. The value is in the fixes it surfaces, not the number - a high score just means fewer gaps to close.

  • I scored low - is that bad?

    Not at all. A low score early on is normal and it is the best time to build good habits. Do the top three fixes in order, work for a week, then re-take it. Readiness compounds quickly once you start.

  • Where do the fixes lead?

    Each fix maps to a concrete next step, and most map to a free tool on this site - the CLAUDE.md generator, model picker, permissions builder, token cost calculator, and MCP picker. The quiz is the diagnostic; those tools are how you act on it.

  • How often should I re-take it?

    Whenever a project changes shape, your bill jumps unexpectedly, or every couple of months as a check-up. Setups drift and Claude Code keeps adding features, so re-assessing keeps you from silently falling behind.

Liked this tool? The club is the next step.

Join Claude Code Club for $9/month. 650+ lessons, weekly updates, and the workflows behind every tool on this site.

  • No experience needed
  • Cancel anytime
  • Updated weekly