The Curio standard
How Curio credentials are earned
Every Curio credential is graded on Curio's servers against the bar on this page. Nothing is self-declared, and the bar is the same for every learner.
Standards year 2026. Every number below is read from the code that grades each attempt.
Silver
Mastery Check
How it works
- Each attempt draws 5 objective questions (up to 2 of them interactive) and 2 written answers from the track's question bank, so no two attempts match.
- Objective questions are graded in code against a stored answer key. Written answers are graded by an AI grader against a rubric of checkable points, citing evidence from the answer.
The pass bar
- At least 4 of 5 objective questions correct (80 percent).
- Every written answer scores at least 60 out of 100, and the written answers average at least 70.
- No answer is empty or flagged as gaming the grader.
Every condition must hold; any miss is a fail. A pass earns Silver. Gold adds the Doctor Proctor oral defense, scored 80 or above.
Silver and Gold
Doctor Proctor oral defense
How it works
- 8 exchanges with an AI examiner, about 20 minutes, answered in your own words and applied to your own work. Extended time is available.
- An independent grader scores each of the track's competencies (listed below) and one unfamiliar scenario that tests transfer, each from 0 to 100, quoting your answers as evidence.
- The transfer scenario carries 25 percent of the score and the competencies share the rest equally. When short interactive questions are mixed in, they carry 15 percent.
The tiers
- Gold: a score of 80 or above, with every competency and the transfer scenario at 70 or above. Defended the credential with Doctor Proctor: demonstrated applied understanding of every core competency, transferred the ideas to an unfamiliar scenario in your own reasoning rather than restating examples, and engaged critically throughout, weighing claims and assumptions rather than taking them at face value.
- Silver: a score of 65 to 79. Demonstrated solid applied understanding across the core competencies, applying the ideas correctly to your own situation, with only minor gaps and limited transfer to unfamiliar cases.
Signals that answers may not be the holder's own can cap a result at Silver. They never raise one.
Applied AI
Practitioner Check
How it works
- Choose one of 6 briefs, build the work product it asks for, and submit it with a short reflection.
- An AI examiner then asks 4 questions about your submission. The grader scores the brief's weighted criteria from 0 to 100, quoting your work as evidence; a criterion with no verifiable quote scores zero.
- A score of 70 or above passes.
Automate a reporting step
- Process mapping 25 percentNames the real manual steps and data sources of the current report concretely enough that a colleague could follow them.
- Model fit 30 percentPuts the model only where it genuinely helps (drafting, summarizing, structuring) and keeps deterministic steps deterministic.
- Instruction quality 25 percentThe instructions given to the model are specific: inputs, output format, tone, and what to do when data is missing or looks wrong.
- Human checkpoint 20 percentDefines what the human reviews before the report ships and which errors that review is designed to catch.
Brief a retrieval grounded assistant
- Corpus definition 20 percentDescribes the document set concretely: what is in it, roughly how much, how it changes, and what is deliberately out of scope.
- Grounding design 30 percentTies every answer to retrieved passages with citations, so a reader can check the source instead of trusting the model.
- Failure behavior 30 percentDefines what the assistant does when the documents do not contain the answer: it says so and points somewhere useful, never guesses.
- Audience fit 20 percentThe answer format and tone match the real people who will ask, with a concrete example question and its ideal answer.
Design an evaluation
- Task definition 20 percentStates the task, its inputs, and what a good output looks like precisely enough that two people would score the same output the same way.
- Test set 30 percentBuilds a test set that mirrors real traffic and deliberately includes the hard and rare cases, with honest counts.
- Scoring method 30 percentScores outputs in a repeatable way: what is checked, who or what judges it, and how disagreement or ambiguity is handled.
- Decision rule 20 percentSets an explicit numeric bar for shipping a change and says what happens when a change wins overall but loses on an important slice.
Draft a guardrailed workflow
- Risk identification 25 percentNames the specific harms this workflow could cause, tied to concrete steps, not generic AI risk language.
- Boundary design 30 percentDraws a clear line between what the model does and what it is never allowed to do in this process, with the reason for each boundary.
- Checks and approvals 30 percentPlaces input and output checks and human approval points where they actually catch the named risks before anything ships.
- Failure path 15 percentDefines what happens when a check fails: who is told, what stops, and how the work resumes safely.
Run a model comparison
- Fair setup 25 percentRuns both candidates on identical inputs under comparable conditions and says exactly what was held constant.
- Judging criteria 25 percentJudges with named criteria chosen before looking at the outputs, not an after-the-fact impression.
- Observed evidence 30 percentReports concrete, specific differences actually observed in the outputs, including where the candidates tied.
- Recommendation 20 percentMakes a clear pick with its tradeoffs and names the situation in which the other candidate would win.
Ship a prompt system for a team
- Template design 30 percentThe template has clearly marked slots, a specified output format, and enough fixed structure that different users get consistent results.
- Usage guide 25 percentThe guide shows one worked example end to end and names the common mistakes that degrade the output.
- Quality consistency 25 percentExplains what keeps output quality uniform when ten different people use the template on ten different inputs.
- Maintenance 20 percentDefines who owns the template, how a proposed improvement is checked before it replaces the current version, and how changes reach the team.
By track
Competencies by track
The Doctor Proctor grader scores each competency below. The Mastery Check tests the same tracks through its question bank.
- AI Foundations
- Prompt Engineering
- AI Agents and Tool Use
- Retrieval Augmented Generation
- AI Evaluation
- AI Model Architecture
- AI Safety and Reliability
- Applied AI Strategy
- Everyday AI Fluency
- AI Assisted Writing
- AI for Knowledge Work
- AI for Everyday Life
- Everyday AI Practice
- AI Operator Method
AI Foundations
- What learning from data meansCan tell whether a system actually learns from data and explain what that changes about how it behaves and fails.
- Training versus inferenceCan reason about the split between expensive one-time training and cheap per-use inference, and what it implies for cost, timing, and change.
- How a language model produces textCan explain how next-token prediction produces useful text and what that mechanism implies about confident errors.
- Tokens, context, and working memoryCan predict how token costs and the context window shape a real task and design around the limits.
- Representations and similarityCan explain how meaning becomes comparable numbers and pick a real use where similarity search genuinely helps.
Prompt Engineering
- Specifying the task, not just describing itCan turn a vague request into a precise one that names the concrete deliverable, the constraints, and the facts the model lacks, so it returns something usable the first time.
- Teaching by example, on purposeCan decide when a few worked examples will steer the model better than instructions, and design the example set so it teaches the intended pattern and not an accidental one.
- The instruction hierarchy and the trust boundaryCan place durable rules in the higher-priority system layer, keep untrusted input as data the model evaluates rather than obeys, and explain what that boundary does and does not guarantee.
- Output that code can trustCan make a model return output another system can consume reliably, using a defined schema, closed value sets, explicit handling of missing fields, and validation with a fallback.
- Treating a prompt like codeCan diagnose why an answer missed, choose the right lever to fix it, and manage prompts with the discipline of code: test cases, one change at a time, and reconciled instructions.
AI Agents and Tool Use
- The line between an agent and a workflowCan tell whether a system is genuinely an agent, one that chooses its own next step toward a goal, or a model wired into a fixed workflow, and judge when a task actually needs one.
- Giving a model hands, safelyCan reason about how a model decides to call a tool, design the tool surface so calls are reliable and checkable, and handle the fact that tool calls can fail or repeat.
- Closing the loop and knowing when to stopCan trace the plan, act, observe loop, explain why observing each result matters, and design stopping conditions that avoid both quitting early and running away.
- Putting the human where it countsCan place a human checkpoint where an error is most costly, give the reviewer what they need to judge, and pause a run without holding compute, avoiding oversight that is real in name only.
- Orchestrating specialists and catching their errorsCan decide when splitting work across agents pays off, carry context across handoffs, reconcile their outputs, and set up a critic that has ground truth and actually gates what ships.
Retrieval Augmented Generation
- When retrieval is the right toolCan tell when grounding a model in retrieved documents is the right approach and what problem it actually solves compared with the alternatives.
- Search by meaning and its limitsCan explain how meaning-based search finds relevant text, and predict where it beats keyword search and where it fails.
- Chunking and indexing for retrievalCan split and organize documents so the passage that answers a question is the one retrieval returns, whole.
- Diagnosing retrieval versus generation failuresCan tell whether a wrong RAG answer came from what was retrieved or from what the model did with it, and act on the right one.
- Freshness, staleness, and maintenanceCan keep a retrieval system accurate as its content and models change, and know when a confident, well-cited answer is still stale.
AI Evaluation
- Why measurement beats intuitionCan explain why demos and anecdotes cannot tell you a change helped, and what a credible comparison needs instead.
- Building an eval set you can trustCan build a test set whose score actually reflects real-world quality, and spot when a number does not.
- Using a model to grade, carefullyCan use a model to grade outputs at scale while guarding the specific ways an automated judge misleads.
- Hallucination and groundingCan explain why models state false things confidently and how grounding reduces, but does not eliminate, the problem.
- From scores to a shipping decisionCan turn evaluation results into a sound decision about whether to ship a change, including a model swap.
AI Model Architecture
- Attention and how context shapes meaningCan explain how attention lets a model weigh every other token when interpreting each one, and predict how changing the surrounding words changes the meaning.
- How generation commits one token at a timeCan explain that text is produced one token at a time, each built on what came before and never revised, and use that to predict behavior and speed.
- The context window as a bounded working memoryCan treat the context window as a bounded, per-call working memory and design a real task so the right information is present and affordable.
- Fine-tuning versus prompting versus groundingCan decide whether a need calls for changing the weights, changing the prompt, or supplying data at inference, and defend the split.
- Multimodal models and one shared representationCan explain how one model reasons over images, audio, and text together, and predict where that reasoning is reliable and where it is not.
AI Safety and Reliability
- Predicting where a model failsCan predict where a model will confidently fail in a real use, and explain why a fluent, confident answer is no evidence it is right.
- Bias in systems that learn from historyCan explain how a system trained on past decisions inherits and can amplify their bias, and why matching the past is not the same as being fair.
- Prompt injection and the trust boundaryCan spot when untrusted text could hijack a model's instructions, and design defenses that hold even if the model is fooled.
- Capability, autonomy, and blast radiusCan reason about how more capability or autonomy raises the stakes, and set a system's permissions by its worst case rather than its best demo.
- Guardrails, oversight, and monitoringCan add the guardrails, human oversight, and monitoring a real deployment needs, placed where they actually catch harm.
Applied AI Strategy
- Designing for the model being wrongCan design the experience around a model so its inevitable errors are cheap to catch, correct, and recover from.
- Dividing work between people and AICan split a real workflow so AI handles what it is reliably good at and people own the uncertain, high-cost decisions.
- Proving the value is realCan prove whether an AI feature moved a metric that matters, against a credible baseline, not just usage or a benchmark score.
- Build, buy, or fine-tuneCan decide whether to buy, fine-tune, or build a capability based on differentiation, total cost, and how fast requirements change.
- Keeping it honest after launchCan spot when a shipped AI workflow is quietly degrading and correct it, instead of trusting that launch-day behavior lasts.