- In short
- A Skill encodes a repeatable, multi-step procedure that Claude should follow consistently for a task type. Skills live at the account level under Customize, not inside any single Project, so a Skill built once is available to every Project that needs it. This is what distinguishes a Skill from a standing instruction: an instruction is a single behavioral rule scoped to one Project, while a Skill is a reusable procedure shared across all of them.
The third slot: procedures, not rules or facts
Once you can tell a behavior rule from a fact, the next distinction the CCAO-F exam wants is the one that separates a single rule from a multi-step procedure. A standing instruction is one behavioral rule. A Skill is a whole procedure: an ordered set of steps Claude should follow the same way every time it does a particular kind of task. Recognising which of the four configuration mechanisms a need calls for depends on catching that difference.
The higher-value thing the exam tests, though, is where Skills live. They do not live inside a Project. They live at the account level, under Customize, and that placement is the whole point of the mechanism.
- Skill
- An account-level configuration mechanism that encodes a repeatable, multi-step procedure Claude should follow consistently for a given task type. Skills are built once under Customize at the account level, not inside any single Project, and are then available to every Project that needs the same procedure. A Skill differs from a standing instruction in that it carries a procedure rather than a single behavioral rule.
What makes something a Skill rather than an instruction
The dividing line is single rule versus procedure. "Use a formal register" is one rule and belongs in a Project's standing instructions. "Turn a set of findings into our standard report: a one-line summary, then risk-rated sections, then a decisions table, then an appendix of sources" is a procedure with several ordered steps, and it belongs in a Skill.
The tell is repetition plus structure. If Claude should do the same task the same way every time, and that way has steps, it is a Skill. If it is a single how-to-behave rule, it is an instruction. Trying to squeeze a multi-step procedure into the instructions field as a long paragraph is a common miss; it works loosely but it is neither reusable nor cleanly maintained.
Why account-level placement is the payoff
Because Skills live at the account level, a Skill you build once is instantly available to any Project that needs it. A firm-wide status-report formatter built as a Skill produces the same structure whether it runs in Client A's Project or Client B's, and nobody has to re-describe the procedure in each Project's instructions.
That is the leverage. Duplicated procedural instructions, one copy per Project, drift apart over time and multiply the maintenance burden. One account-level Skill is a single source of truth for the procedure, updated in one place. The reusability is not a nice-to-have; it is the reason the mechanism sits at the account level rather than inside a Project.
What the CCAO-F exam trips candidates on
The exam sets two traps. The first is assuming a Skill must be recreated inside each new Project rather than reused from the account level. A scenario shows someone re-writing the same procedure in Project after Project; the credited answer builds it once as an account-level Skill and reuses it. Recognising that re-creation is unnecessary is the point.
The second is confusing an account-level reusable Skill with a Project-scoped standing instruction that happens to describe steps. A long, step-listing instruction inside one Project can look like a Skill, but it is not reusable across Projects and it is not maintained as one artifact. When a procedure should be shared and consistent everywhere, the answer is a Skill, not a verbose instruction pinned to a single Project.
Worked example
A consultant runs one Project per client. In each new client Project, they paste the same eight-step 'weekly status report' procedure into the standing instructions. Over a few months the reports start looking slightly different across clients. What is the underlying configuration problem, and what is the fix?
The problem is that a reusable procedure has been implemented as a per-Project instruction, so there are now many copies of it, one per client Project, and they have drifted apart.
A weekly status-report procedure is a repeatable, multi-step task that should run identically everywhere, which is the definition of a Skill. Because Skills live at the account level, the consultant should build the status-report formatter once under Customize and let every client Project use that single Skill. The reports then share one structure by construction.
Pasting the eight steps into each Project's instructions is the exact trap: it looks like it captures the procedure, but it creates duplicate copies that diverge as each is edited independently, and it burdens every new client setup with re-describing the same steps. Rebuilding it as one account-level Skill removes the duplication and the drift in a single move.
Common misreadings to avoid
Misconception
A Skill has to be set up separately inside every Project that uses it.
What's actually true
Misconception
A long standing instruction that lists steps is effectively the same as a Skill.
What's actually true
How this shows up on the exam
Domain 5 questions describe a repeatable, structured task and ask which mechanism fits. If it is a multi-step procedure that should run the same way across contexts, it is a Skill built once at the account level, not an instruction copied into each Project.
This connects forward to selecting the right mechanism for a client workspace, where a firm-wide formatter is precisely an account-level Skill, and to Skills versioning behavior, which governs how a Skill stays current once built. It also pairs with the instructions-versus-knowledge distinction, completing the picture of which slot a need belongs in.
A team wants every Project in the company to format research findings into the same multi-step report layout. Which configuration approach fits best?
People also ask
Where do Claude Skills live?
What is the difference between a Skill and a standing instruction?
Do I need to recreate a Skill in each 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.