15 quick questions covering everything in the guides above. Score 12 or more and you'll get a shareable "Claude 101 Graduate" badge you can download or post. Nothing you enter here leaves your browser.
Question 1 of 15
What's the best way to think about how Claude generates a response?
It generates a response from patterns learned in training, plus your conversation's context
It looks up the exact answer in a live database
It automatically fact-checks itself against the internet every time
It only works if you use a special command
Question 2 of 15
What generally improves a prompt's result the most?
Adding more exclamation marks
Giving specific, relevant context instead of a vague ask
Keeping every prompt under 10 words
Repeating the same question three times in a row
Question 3 of 15
What's the main advantage of a Project over a plain chat?
Projects load faster than a regular chat
You can't use Claude at all without one
You attach reference material once, and every chat inside already has that context
Projects automatically delete old chat history
Question 4 of 15
What does an MCP connector actually let Claude do?
Make Claude's answers longer
Increase the model's context window
Automatically translate your prompts into code
Reach into real tools like Slack, Gmail, or your calendar and take action
Question 5 of 15
You want something that runs on a schedule, without you opening anything. What's the right tool?
Claude Code, or a Scheduled Task
A plain chat conversation
A Project
Turning on dark mode
Question 6 of 15
What's a practical way to get more done without hitting usage limits or paying for the biggest plan?
Never use Projects
Match the model and effort to the task instead of maxing out every request
Always use the most powerful model, for everything
Ask the same long question multiple times in a row
Question 7 of 15
When you're brand new to Claude, what's a good way to spend your first week?
Read the documentation cover to cover before typing anything
Only use the mobile app until you're comfortable
Try real prompts from your actual day, like drafting an email or explaining a concept
Avoid asking anything you don't already know the answer to
Question 8 of 15
When comparing Claude to other AI assistants, what actually matters most for picking one?
Whichever one has the flashiest launch video
Whichever one is used by the most people on social media
Whichever one is free forever with no limits
How well it fits your actual day-to-day tasks and workflow, not marketing claims
Question 9 of 15
The "Six Decisions" framework is mainly about...
The handful of practical choices that shape most interactions with Claude, like where to open it and which model to use
Choosing a favorite Claude nickname
A billing plan comparison chart
Deciding which browser to use
Question 10 of 15
What's a more effective way to get through a messy spreadsheet with Claude?
Copy-paste small snippets of the data as plain text every time
Attach the actual file and describe what's wrong with it in plain language
Manually clean the whole spreadsheet first so Claude has nothing to do
Avoid uploading files altogether
Question 11 of 15
What's one thing admins can actually control on the Claude Team plan?
Which font each user's chat window uses
Nothing - all settings are fixed for every org
Per-user spend caps and which connectors or plugins the team can install
How many words are in each user's replies
Question 12 of 15
What does Claude Design actually do?
It's a spellchecker for chat messages
It automatically redesigns your operating system
It's a plugin that only works inside spreadsheets
It's a prototyping workspace that turns descriptions into working visual drafts like UI mockups
Question 13 of 15
Roughly speaking, what's the difference between an MCP Connector and a Skill?
A connector reaches into an external tool; a Skill packages reusable instructions or knowledge for Claude to use
They're the exact same thing with two different names
A connector is a paid upgrade; a Skill is always free
Skills only work inside Claude Code, never in chat
Question 14 of 15
What defines an "agentic workflow" compared to a normal back-and-forth chat?
It requires exactly one message and one reply, nothing more
Claude plans and carries out multiple steps toward a goal with less manual back-and-forth
It only works with images, never text
It's just a chat with a longer response
Question 15 of 15
What does the Claude API give you that the chat interface doesn't?
A friendlier font
Unlimited free usage
Direct, programmatic control to build Claude into your own tools and products