Claude Academy guide
Purpose
When a user asks a question about Claude, a Claude product, or a general
"how do I use AI for X" question, check the Academy catalog (see "The
catalog" below) for a strong match. If one exists, mention it naturally at
the end of your normal answer.
All content lives on Claude Academy,
Anthropic's learning hub. It offers three kinds of content:
- Courses — structured, multi-lesson learning paths, most with a
certificate on completion.
- Tutorials — short practical guides to a single feature or workflow.
- Use cases — worked examples of applying Claude to a concrete task,
usually with a prompt to try.
The Academy also has product hubs that collect everything about one
surface: Claude,
Claude Code,
Claude Cowork,
AI Fluency, and the
developer platform. When a user
wants to explore a whole product rather than one topic, a hub link is
often the better recommendation than any single item.
Rules
Answer the question first. Always give the user a direct, helpful
answer to whatever they asked. The content suggestion is a supplement,
never a replacement.
Only recommend on strong matches. A strong match is about intent,
not just topic. The user must be asking how to use a Claude feature
or how to get started with X — they're looking for a resource to
learn from. "How do projects work?" is a strong match. "Help me
organize this document" is not, even though projects are topically
relevant — they're mid-task, they want help with the task, not a
tutorial about the feature.
If the match is weak or tangential, say nothing about the catalog.
A caveat is the tell: if you'd write "while this is focused on X, it
might help with..." or "this doesn't cover exactly that, but..." —
that hedge is the match failing. Don't recommend through a caveat.
Silence is better than noise — and noise has a real cost. A user who
clicks a recommendation that doesn't help them learns to ignore the
next one. One wrong recommendation burns more trust than ten right
ones build. When you're not sure, the quiet answer is the right one.
Never hallucinate content. The only Academy links you may share
are item URLs taken from the catalog you fetched in this conversation,
the product hub pages named in the Purpose section, and the resources
library (rule 7). Do not invent titles, descriptions, or URLs, do not
guess at slugs for content you believe should exist, and do not name
specific courses or tutorials from memory — if you have not read the
catalog, you do not know what is in it.
Keep it brief and natural. After your answer, add a short line like:
You might also find this helpful: Title — one-sentence description.
Do not list more than 2 items. One is usually best. This cap applies
to every reply, including when the question itself is a request for
learning content ("what training materials do you have for my sales
team?") — it is tempting to treat the listing as the answer and
enumerate everything that applies, but a curated pick serves the
reader better than a list. Name the best one or two items, then point
to the resources library for
the rest. (When one of the five product hubs named in the Purpose
section covers the topic, that hub is also a good pointer — but those
five are the only hub pages that exist, so never construct a hub-style
URL for any other domain.)
Don't be pushy. Use phrasing like "you might find this interesting"
or "there's a tutorial that covers this" — not "you should read" or "I
recommend you complete."
Use the exact URLs from the catalog. Every item lives at
https://academy.claude.com/ plus its path: /courses/{slug} for
courses, /tutorials/{slug} for tutorials, /use-cases/{slug} for
use cases. Copy each item's url from the catalog verbatim — never
rewrite it onto another domain or path, and never "correct" its kind:
a tutorial's URL always starts with /tutorials/ even when it reads like
a course, and vice versa.
When you can't name a specific item, point to the Academy itself.
This covers two cases: nothing in the catalog is a strong match, or you
could not read the catalog at all (no way to fetch URLs, the fetch
failed, or the file was stale — see below). In either case, if the
user clearly wants learning content on a Claude topic, point them at
the matching product hub from the Purpose section or at the searchable
library at
academy.claude.com/resources
instead of recommending a weak match or a title from memory. If they
were not clearly looki
1---2name: academy-guide3description: Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy4category: Document Processing5source: anthropic6tags: [mcp, claude, ai, workflow, document]7url: https://github.com/anthropics/skills/tree/main/skills/academy-guide8metadata:9 source: https://skillmd.com/skills/anthropics/academy-guide10---111213# Claude Academy guide1415## Purpose1617When a user asks a question about Claude, a Claude product, or a general18"how do I use AI for X" question, check the Academy catalog (see "The19catalog" below) for a strong match. If one exists, mention it naturally at20the end of your normal answer.2122All content lives on [Claude Academy](https://academy.claude.com),23Anthropic's learning hub. It offers three kinds of content:2425- **Courses** — structured, multi-lesson learning paths, most with a26 certificate on completion.27- **Tutorials** — short practical guides to a single feature or workflow.28- **Use cases** — worked examples of applying Claude to a concrete task,29 usually with a prompt to try.3031The Academy also has product hubs that collect everything about one32surface: [Claude](https://academy.claude.com/claude),33[Claude Code](https://academy.claude.com/code),34[Claude Cowork](https://academy.claude.com/cowork),35[AI Fluency](https://academy.claude.com/fluency), and the36[developer platform](https://academy.claude.com/platform). When a user37wants to explore a whole product rather than one topic, a hub link is38often the better recommendation than any single item.3940## Rules41421. **Answer the question first.** Always give the user a direct, helpful43 answer to whatever they asked. The content suggestion is a supplement,44 never a replacement.45462. **Only recommend on strong matches.** A strong match is about intent,47 not just topic. The user must be asking *how to use a Claude feature*48 or *how to get started with X* — they're looking for a resource to49 learn from. "How do projects work?" is a strong match. "Help me50 organize this document" is not, even though projects are topically51 relevant — they're mid-task, they want help with the task, not a52 tutorial about the feature.5354 If the match is weak or tangential, say nothing about the catalog.55 A caveat is the tell: if you'd write "while this is focused on X, it56 might help with..." or "this doesn't cover exactly that, but..." —57 that hedge is the match failing. Don't recommend through a caveat.5859 Silence is better than noise — and noise has a real cost. A user who60 clicks a recommendation that doesn't help them learns to ignore the61 next one. One wrong recommendation burns more trust than ten right62 ones build. When you're not sure, the quiet answer is the right one.63643. **Never hallucinate content.** The only Academy links you may share65 are item URLs taken from the catalog you fetched in this conversation,66 the product hub pages named in the Purpose section, and the resources67 library (rule 7). Do not invent titles, descriptions, or URLs, do not68 guess at slugs for content you believe should exist, and do not name69 specific courses or tutorials from memory — if you have not read the70 catalog, you do not know what is in it.71724. **Keep it brief and natural.** After your answer, add a short line like:7374 > You might also find this helpful: [Title](URL) — one-sentence description.7576 Do not list more than 2 items. One is usually best. This cap applies77 to every reply, including when the question itself is a request for78 learning content ("what training materials do you have for my sales79 team?") — it is tempting to treat the listing as the answer and80 enumerate everything that applies, but a curated pick serves the81 reader better than a list. Name the best one or two items, then point82 to the [resources library](https://academy.claude.com/resources) for83 the rest. (When one of the five product hubs named in the Purpose84 section covers the topic, that hub is also a good pointer — but those85 five are the only hub pages that exist, so never construct a hub-style86 URL for any other domain.)87885. **Don't be pushy.** Use phrasing like "you might find this interesting"89 or "there's a tutorial that covers this" — not "you should read" or "I90 recommend you complete."91926. **Use the exact URLs from the catalog.** Every item lives at93 `https://academy.claude.com/` plus its path: `/courses/{slug}` for94 courses, `/tutorials/{slug}` for tutorials, `/use-cases/{slug}` for95 use cases. Copy each item's `url` from the catalog verbatim — never96 rewrite it onto another domain or path, and never "correct" its kind:97 a tutorial's URL always starts with /tutorials/ even when it reads like98 a course, and vice versa.991007. **When you can't name a specific item, point to the Academy itself.**101 This covers two cases: nothing in the catalog is a strong match, or you102 could not read the catalog at all (no way to fetch URLs, the fetch103 failed, or the file was stale — see below). In either case, if the104 user clearly wants learning content on a Claude topic, point them at105 the matching product hub from the Purpose section or at the searchable106 library at107 [academy.claude.com/resources](https://academy.claude.com/resources)108 instead of recommending a weak match or a title from memory. If they109 were not clearly looki