$ loading_
Find matching Claude Academy courses, tutorials, and learning resources.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "academy-guide" skill from askskill: 1. Download https://raw.githubusercontent.com/anthropics/skills/main/skills/academy-guide/SKILL.md 2. Save it as ~/.claude/skills/academy-guide/SKILL.md 3. Reload skills and tell me it's ready
When a user asks how to use a Claude feature, this skill can answer the question first and then add a strongly relevant Claude Academy course or tutorial for further learning.
When an organization is rolling out Claude or needs onboarding materials, this skill can recommend suitable Academy content and product hub pages.
When a user wants a broad understanding of Claude, Claude Code, Claude Cowork, or the developer platform, it can recommend the relevant product hub instead of isolated items.
The document explains that this skill should be used for questions about how to use Claude, Claude products, or related onboarding and training needs. It says to answer the user’s question first, then add a Claude Academy recommendation only when there is a strong intent match. It also stresses brief, natural recommendations and explicitly warns against inventing course titles, descriptions, or URLs.
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:
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.
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
…
It is used to find and recommend strongly relevant Claude Academy courses, tutorials, or use cases after answering Claude-related how-to questions. The recommendation is supplementary, not a replacement for the direct answer.
It should not be used when the user is in the middle of a task and just wants the task done. It is appropriate only when the user clearly wants to learn how to use a Claude feature or needs onboarding materials.
The excerpt shows three main content types: courses, tutorials, and use cases; it also includes product hub pages. Specific items should be verified against the actual catalog.
Create, refine, and evaluate AI skills for better performance and triggering accuracy.
Read, extract, edit, merge, split, OCR, and create PDF documents.
Design and generate polished, production-ready frontend interfaces and web component code.
Create, read, edit, and organize PPTX presentations, text, notes, and layouts.
Create Slack-ready animated GIFs with optimized specs, validation, and animation guidance.
Build complex web artifacts with React, Tailwind, and shadcn/ui components.
Discover Claude skills and resources to customize efficient AI coding workflows.
Turn Claude into a management consulting assistant for strategy and case work.
Turn docs, GitHub repos, and PDFs into Claude skills with conflict checks.
Discover, search, and read Claude Agent Skills guidance through MCP tools.
Discover, search, recommend, and install Claude Code skills from SkillHub.
Write precise prompts for any AI tool with full context retention.