- In short
- A Project is the right home for requirements-extraction work that recurs, because its standing instructions hold the extraction format, its knowledge base holds prior worked examples for consistency, and Skills, which apply at the account level across all Projects, hold repeatable formatting steps. A recurring task run in a fresh Chat each time forces all of this to be restated on every use.
The moment a task stops being a one-off
Extracting requirements from a single document is a one-off job, and a plain Chat handles it. But most valuable requirements work is not a single job. A proposal team processes every incoming RFP the same way; a support team turns every incident report into the same structured shape. Once the same extraction recurs, the Claude Certified Associate - Foundations (CCAO-F) exam expects you to stop treating each instance as fresh and to set the work up as a Project. This is an apply-level skill: recognising the recurrence and choosing the container that fits it.
The cost of not doing so is quiet but real. In a fresh Chat each time, the extraction format has to be described again, the desired output shape re-explained, and the sense of what a good result looks like reconstructed from memory. That repetition is not just wasted effort; it is a source of drift, because the instructions are never phrased quite the same way twice and the output slowly loses consistency. A Project removes the repetition by making the setup persist.
- A Project for recurring extraction
- A Project is a persistent container for a recurring task where the standing instructions hold the extraction format, the knowledge base holds prior worked examples for consistency, and account-level Skills supply repeatable formatting steps. It replaces the pattern of restating all of this in a fresh Chat every time a similar document arrives.
What the Project holds so you do not have to restate it
A Project keeps three things in place that a Chat forgets. The standing instructions hold the extraction format: the fields you want, the shape of the table, the marking convention for answered versus open. Because they live in the configuration, they apply to every conversation in the Project without being typed again. This is the same persistence principle behind using a Project to stabilise design context across iterations, applied to extraction instead of design.
The knowledge base holds prior worked examples. When Claude can see how three previous documents were extracted, it matches that pattern, which keeps the output consistent from one use to the next rather than reinventing the format each time. Past winning proposals, earlier processed reports, or a reference example all serve this role: they anchor the new extraction to the established shape. Together the standing instructions and the knowledge base mean a new document dropped into the Project gets processed the same way the last one did, with no re-explanation.
Skills live at the account level, not inside one Project
The third piece is the one candidates most often get wrong. A Skill encodes a repeatable formatting step, and Skills apply at the account level across all your Projects. A Skill you configured while working in one Project is available in every other Project too, including this one. It is not trapped inside the Project where you first used it.
This distinction matters because it changes how you think about where capability lives. Standing instructions and the knowledge base are scoped to the Project; they belong to that recurring task. A Skill is broader: it is an account-wide capability you can lean on from any Project. So the mental model is layered. The Project supplies the task-specific format and examples, and account-level Skills supply the reusable procedural steps that any Project can call on. Assuming a Skill only works where it was created leads to needlessly rebuilding the same capability in each Project.
What the CCAO-F exam trips candidates on
The exam tests two traps. The first is recreating the extraction instructions from scratch in a new Chat each time a similar document arrives, when the recurrence clearly called for a Project. A scenario will describe a team doing the same extraction repeatedly and typing the format afresh every time; the credited move is to move the work into a Project so the instructions, examples, and steps persist. The second trap is assuming a Skill only works inside the Project where it was first used. The exam wants you to know that Skills apply account-wide, so a formatting Skill built in one context is available across all Projects.
Both traps come down to knowing where each piece of setup lives. Task-specific format and examples belong in the Project; reusable procedural steps live as account-level Skills; and a recurring task should never be run as a fresh Chat.
Worked example
A proposal team responds to a steady stream of client RFPs. Each time one arrives, an analyst opens a new Chat, describes the required table format, pastes in a past proposal as a reference, and asks for the extraction. A colleague suggests this could be set up better. How should the team restructure it?
The current pattern wastes effort and invites drift. Every RFP triggers the same manual setup: re-describing the table format, re-attaching a reference proposal, re-explaining what a good extraction looks like. Because the instructions are retyped each time, they vary slightly with each analyst and each occasion, so the outputs slowly diverge in shape even though the task is identical.
The fix is to make this recurring task a Project. The standing instructions hold the extraction format once, so every RFP processed in the Project inherits it without anyone typing it again. The knowledge base holds the past winning proposals, so Claude has concrete examples to match and the outputs stay consistent. New RFPs are simply added to the Project and processed against the same setup.
The formatting steps that recur, such as normalising section references or applying a house table style, are best encoded as Skills. And because Skills apply at the account level, those same steps are available not only in this Project but in any other Project the team runs, so they never have to be rebuilt per Project. The result is that a new RFP goes from a from-scratch setup to a drop-in, with the format, the examples, and the steps all already in place.
Common misreadings to avoid
Misconception
A recurring extraction is fine to run in a new Chat each time, since you can just re-describe the format.
What's actually true
Misconception
A Skill only works inside the Project where it was first configured.
What's actually true
How this shows up on the exam
Domain 4 questions on this knowledge point describe a repeated extraction task and ask how to structure it, or they test whether you know that Skills are account-wide rather than Project-scoped. The reliable reading is that a recurring task belongs in a Project whose standing instructions and knowledge base persist the format and examples, while account-level Skills supply reusable steps available across every Project.
This knowledge point builds on requesting structured output from messy inputs, which defines the extraction the Project will run repeatedly, and it pairs with using a Project to stabilise design context across iterations, the same persistence idea applied to design work. The extractions a Project produces still need pressure-testing before they are trusted.
A support team turns every incoming incident report into the same structured requirements table, and does it dozens of times a week by re-explaining the format in a new Chat each time. Which change best fits this recurring work?
People also ask
When should you use a Project instead of a one-off Chat?
What does a Project knowledge base hold?
Do Skills work only inside one Project?
Watch and learn
Official Anthropic Academy lessons first, then hand-picked walkthroughs. Videos load only when you press play.
No videos curated for this concept yet
We are still curating the best official and community videos for this topic.
Official prep for this domain
Anthropic's own free prep module for this part of the syllabus, on the official prep course. Free with an Anthropic Academy sign-in.
References & primary sources
Master this concept with Archie
Practice it inside an adaptive study session. Archie, your Socratic AI tutor, tracks your mastery with Bayesian Knowledge Tracing and schedules the perfect next review.