academy-guide
> 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 (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.
Why we recommend it: Adjacent to Claude Code via learning resources but does not perform Claude Code workflow tasks.
Inspect before use
Read the source instructions and check the requirements before you install this skill.
SKILL.md
The saved excerpt is a snapshot from when this skill was listed. The external source remains the complete and most current version.
--- name: academy-guide description: > 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 (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. license: Complete terms in LICENSE.txt --- # 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](https://academy.claude.com), 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](https://academy.claude.com/claude), [Claude Code](https://academy.claude.com/code), [Claude Cowork](https://academy.claude.com/cowork), [AI Fluency](https://academy.claude.com/fluency), and the [developer platform](https://academy.claude.com/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 1. **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. 2. **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. 3. **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. 4. **Keep it brief and natural.** After yourRead the full source on GitHub (opens external page)