Anthropic Learning Hub

Claude 101

5 sections · 14 lessons. Read the study guide below, then test yourself with a quiz.

0101. What Claude Is

Claude is an AI assistant built to function as a thinking partner. Rather than just answering simple questions, it handles summarization, search, creative writing, Q&A, coding, and more—while remaining reliable and predictable across all of those tasks.

Key Term

A training approach developed by Anthropic that teaches Claude to align with human values and behave transparently. It guides Claude to avoid toxic or discriminatory outputs, refuse assistance with illegal or unethical activities, and act as a helpful, honest, and harmless system.

  • Helpful: assists with a broad range of tasks and provides genuinely useful responses.
  • Harmless: avoids toxic, discriminatory, or illegal outputs and declines requests that could cause harm.
  • Honest: operates transparently and does not deceive users.

Claude is steerable and collaborative. You can direct it on personality, tone, and behavior. Users consistently report that Claude is easier to guide toward a desired output and produces fewer harmful responses than comparable tools—meaning less effort to get the result you need.

Plans and Device Access

Claude apps are available across Free, Pro, Max, Team, and Enterprise plans. Every plan type includes access to the web, desktop, and mobile apps.

Note

Conversations, projects, memory, and preferences sync automatically across all devices when you are signed in—whether you are at your desk or on the go.

Key Takeaway

Claude is a thinking partner, not just a chatbot. Built on Constitutional AI principles—helpful, harmless, and honest—it is steerable, collaborative, and available across web, desktop, and mobile on every plan type.

0202. Core Capabilities

Claude's capabilities span a wide range of tasks, going well beyond simple question-and-answer. It can both automate and augment your work—acting as a collaborator on complex, open-ended problems.

Writing, Research, and Analysis

For writing, Claude collaborates on social media posts, professional emails, and detailed reports. Because it accepts direction on tone and style, you can iterate with it until your own voice comes through clearly.

Key Term

The maximum amount of content Claude can consider in a single conversation. The standard context window handles 200K+ tokens—roughly 500 or more pages of text. On Pro, Max, Team, and Enterprise plans with supported models, this expands to up to 1 million tokens.

For research and analysis, you can upload documents and Claude will surface meaningful insights from complex material. Its large context window allows it to process extensive materials—potentially hundreds of pages—within a single conversation without losing track of earlier content.

Coding and Problem-Solving

Coding is one of Claude's strongest areas. It can write, debug, and explain code across multiple programming languages, with strong performance on real-world coding tasks.

Key Term

A reasoning mode available in Claude's recent Opus and Sonnet hybrid models. When active, Claude works through a problem step-by-step before responding, trading speed for depth. The same hybrid models also offer a near-instant response mode for faster tasks.

For complex cognitive tasks—mathematical problems, strategic analysis, research—Claude handles everything from quick lookups to deep multi-step reasoning. Extended thinking makes it well-suited for problems that require careful, structured analysis.

Learning Support

Key Term

A Claude experience that guides your reasoning process rather than simply providing answers. Instead of giving you the answer directly, it helps you work through problems yourself, building critical thinking skills.

Claude adapts to your learning style and pace. Whether you are picking up a new skill, exploring an unfamiliar domain, or working through a challenging concept, it adjusts its explanations to meet you where you are.

Tip

The use-case gallery on claude.com shows how Claude applies to specific roles and functions. Visit it for inspiration tailored to your line of work.

Key Takeaway

Claude's core strengths span writing, research, coding, complex reasoning, and learning support. Its large context window, extended thinking mode, and adaptive style make it effective for both quick tasks and deep, multi-step work.

0303. Ways to Access Claude

The same Claude intelligence is available through multiple interfaces, each suited to a different type of work. Most users interact with Claude through Claude.ai—the web, desktop, and mobile experience—which is the focus of this course.

InterfaceBest forKey actions
Claude.ai (web, desktop, mobile)Conversations, writing, research, analysis, file creationAsk questions, brainstorm ideas, create and edit documents
Claude CodeDeveloper workflows and file manipulation on the desktopEdit files, run commands, create git commits
Claude + SlackTeam collaboration inside SlackChat in AI assistant header, @mention Claude in threads, search workspace channels and files
Claude for ExcelSpreadsheet work inside Microsoft ExcelRead, analyze, modify, and create workbooks; explain formulas; navigate multi-tab files

Note

This course focuses on Claude.ai. For development workflows, the Claude Code in Action course covers using Claude in developer contexts.

Claude Code is an agentic coding tool designed for developers but usable for general file manipulation on the desktop. It goes beyond conversation—it can directly edit files, run terminal commands, and create git commits.

Tip

Although Claude Code is aimed at developers, anyone who needs to manipulate files on their desktop can benefit from it. Its ability to directly edit files and run commands makes it more powerful than a conversational interface for file-based tasks.

Claude + Slack lets you chat with Claude from any channel's AI assistant header or by @mentioning it in threads. When connected, Claude searches your workspace's channels, direct messages, and shared files to give more contextually relevant responses.

Claude for Excel adds a sidebar inside Microsoft Excel where Claude can read, analyze, modify, and create workbooks. It is best suited for model analysis, assumption updates, error debugging, template population, formula explanations, and multi-tab navigation.

Key Takeaway

Claude is accessible through Claude.ai, Claude Code, Slack, and Excel—each built for a different work context. The Claude.ai apps (web, desktop, and mobile) are the primary interface for most users and the focus of this course.

0401 The Claude.ai Interface

Claude is an AI collaborator that amplifies your capabilities across your work. You bring the context and expertise that makes the work meaningful; Claude brings AI intelligence to help you act on it.

Key Term

A prompt is the message or instruction you send to Claude. All interactions with Claude begin with a prompt, and these prompts — combined with other context — shape Claude's response.

When you open Claude.ai, the sidebar on the left gives you quick access to the main navigation. Your text input area sits at the bottom of the screen, ready for your first prompt.

  • New chat icon — starts a fresh conversation
  • Chat history — lets you return to previous conversations
  • Projects — organize conversations with persistent context and custom instructions
  • Artifacts — turn ideas into shareable apps, tools, or content

Note

Artifacts let you transform conversation outputs into standalone, shareable items — such as a working app, a formatted document, or an interactive tool — directly from the sidebar.

Your prompts can range from simple questions — like brainstorming names for a new feature — to complex requests to co-create full documents or code. No matter the goal, Claude can support you.

Key Takeaway

Claude.ai's interface centers on a single starting point: your prompt. The sidebar surfaces history, projects, and artifacts, but every session begins with a message you write.

0502 Writing Effective Prompts

The best approach when speaking to Claude is the same as speaking to a coworker — naturally, concisely, and conversationally. Prompts do not need to be formal commands; plain language works well.

The Three-Part Framework

A strong prompt covers three elements before you hit send.

ElementQuestion to ask yourselfExample
Setting the stageWhat is my role and objective? What context should Claude know?"I'm the marketing lead at an indie streaming startup preparing a Series A pitch deck."
Defining the taskWhat action do I want Claude to take — write, analyze, build?"Research current market trends, competitor positioning, and growth opportunities."
Specifying rulesWhat style, tone, or format should Claude use? Can I attach examples?"Use web research with citations. Structure it as a professional report up to 5 pages."

Tip

Speak to Claude like a capable coworker who is new to your project. Give enough context for them to act without over-explaining every detail.

Putting the Framework Together

Combining all three elements in a single prompt gives Claude everything it needs to produce a well-targeted response. The investor pitch deck example from the video demonstrates this: role and context come first, then the specific research task, then format requirements and citation rules.

Full example prompt with annotationsClick to expand

"I'm the marketing lead at an indie streaming startup, and we're preparing an investor pitch deck for Series A investors. Can you research the current state of the independent film streaming market and identify key trends, competitor positioning, and growth opportunities? Use current web research with citations and structure it as a professional report of up to 5 pages, with an executive summary, market analysis, competitive landscape, and growth opportunities." — Stage: marketing lead at an indie streaming startup preparing a Series A pitch deck — Task: research market trends, competitor positioning, and growth opportunities — Rules: web research with citations, professional report format, up to 5 pages, specific sections named

Key Term

A research-backed framework developed by Professor Rick Dakan (Ringling College of Art and Design) and Professor Joseph Feller (University College Cork) that identifies four core competencies for working with AI: Delegation, Description, Discernment, and Diligence. The three-part prompt framework above is adapted from this research.

Key Takeaway

Every effective prompt covers three things: who you are and why you need this (stage), what Claude should do (task), and how Claude should do it (rules). Missing any one of these is the most common reason a first response misses the mark.

0603 Adding Context and Tools

Uploading files and connecting external tools gives Claude access to information beyond what you type. Claude can analyze both text and visual elements — such as charts and graphics — in the files you attach.

  • PDF — documents with text and embedded images
  • DOCX — Word documents
  • CSV — tabular data
  • TXT — plain text files
  • PNG and JPEG — images, screenshots, and charts

Once a file is uploaded, it appears as an attachment in the chat and Claude automatically parses its content. You can then prompt Claude directly about anything in the file.

  1. Upload a document and ask Claude to summarize the key points
  2. Share an image and ask Claude to describe or analyze what it sees
  3. Attach a spreadsheet and ask Claude to identify trends in the data
  4. Upload code and ask Claude to explain it or find bugs

Tip

To have Claude consider specific preferences in every response, go to Settings > General > 'What personal preferences should Claude consider?' — these apply across all conversations automatically.

The Search and Tools menu extends Claude's access to real-time information. You can toggle on web search to let Claude pull current data, or connect Google Drive to access your own files. Claude selects which tools to use automatically while solving your request — you do not need to specify when.

Note

Instead of pasting raw content into a prompt, you hand Claude the source directly. The more relevant context Claude has, the more precisely it can respond.

Key Takeaway

Uploads, connectors, and the Tools menu all serve the same purpose: giving Claude the right information to respond accurately. File types, real-time data, and personal preferences can all feed into a single conversation.

0704 Choosing the Right Model

Claude offers multiple models, each optimized for different types of work. The model selector appears under your text input when you start or open a chat. Changing the model starts a new chat.

ModelBest forKey characteristic
Claude OpusMost complex tasksLargest-scale model with hybrid reasoning capabilities — suited for tasks like multi-step financial analysis
Claude SonnetEveryday use (recommended default)Balances sophisticated capabilities with cost-effectiveness; best starting point for most users

Key Term

A mode that enables deeper reasoning for complex analysis tasks. It increases response latency and is not necessary for simple questions or routine tasks. For straightforward work, leave thinking mode off and use Sonnet.

For straightforward tasks, start with Sonnet and leave thinking mode off to get the fastest output. Switch to Opus or enable thinking mode when a task genuinely requires more analytical depth.

Key Term

A Claude feature that conducts systematic, multi-angle investigations by automatically breaking down complex questions and exploring hundreds of sources. Delivers comprehensive, cited reports in 5 to 45 minutes — designed for tasks where breadth of sources and citation quality matter.

Research mode is well-suited for competitive analysis, market research, or literature reviews. You submit the question and Claude handles the investigation while you focus on other work.

Research mode vs. web search — which to useClick to expand

Web search (in the Tools menu) is suitable for quick factual lookups or adding a few current data points to a response. Research mode runs a structured, multi-angle investigation across hundreds of sources and takes 5 to 45 minutes. Use Research when depth and citation quality matter more than speed.

Key Takeaway

Match the model and mode to the complexity of your task. Sonnet with thinking off handles most everyday work efficiently. Reserve Opus, thinking mode, or Research for tasks that genuinely require deeper analysis or broader source coverage.

0805 Iterating and Personalizing

Claude conversations are meant to be iterative. Chaining short prompts together — rather than writing one long request — creates a natural dialogue where you guide the output based on what Claude returns.

Refining Claude's Responses

  • Ask follow-up questions: request more detail, a different angle, or clarification on a specific point — e.g., "Can you expand on the second point?"
  • Provide feedback: tell Claude what worked and what didn't — e.g., "The tone is too formal, make it more conversational"
  • Redirect: steer Claude back if it went the wrong direction — "I was asking about X, not Y"
  • Restart: open a new chat to fully refresh context when a conversation has drifted too far off track

Tip

Click the pencil icon on any of your previous messages to edit and resubmit the prompt. This is useful when you want to refine your original request rather than add a new follow-up message.

The more frequently you interact with Claude, the better it becomes at understanding your communication style and preferences. Continued conversation — not just one-off prompts — is where Claude's full value surfaces.

Memory and Styles

Key Term

A Claude feature that automatically saves key context from your conversations — your role, preferences, past decisions, and working style — so you do not have to repeat yourself in future chats. You can review, edit, or delete stored memories at any time in Settings. Memory syncs across all devices.

For example, if you tell Claude you work in marketing at a B2B company, Memory stores that so Claude applies it in future conversations without being told again.

Key Term

A Claude feature that lets you customize how Claude communicates. Choose from presets — concise, formal, or explanatory — or create a custom style by describing exactly how you want Claude to write. The selected style applies automatically across all conversations.

Together, Memory and Styles reduce the setup work at the start of each conversation. Claude arrives with context about who you are and already knows how you prefer to receive information.

Key Takeaway

Single prompts get single answers. Iterative dialogue — built on follow-ups, feedback, and refinement — is what makes Claude a true collaborator. Memory and Styles extend that collaboration across sessions, so your preferences carry forward automatically.

0901. Common Challenges When Starting Out

When Claude's response isn't what you expected, that's a signal to refine your approach—not a reason to stop. Most issues trace back to a few predictable causes, and each has a clear fix.

ChallengeWhat's HappeningTry This
Response is too genericYour prompt lacked context about your specific situationAdd details about your audience, role, or constraints. Instead of "Write an email about the project delay," specify the client, the delay duration, prior history, and the tone you need.
Response is too long or too shortClaude guessed at the appropriate lengthBe explicit: "Give me a two-paragraph summary," "Keep this under 100 words," or "I need a comprehensive analysis—length isn't a concern."
Claude didn't follow my formatClaude understood the task but not how you want it presentedShow the format rather than describe it. Provide an example, or be explicit: "Use bullet points with bold headers for each section."
Confident-sounding information turned out to be wrongClaude occasionally generates plausible but incorrect information, especially with specific facts or niche topicsFor high-stakes work, verify key facts independently. Ask Claude to indicate its confidence level or cite sources. Enable web search to ground responses in current information.
The tone isn't rightClaude defaults to helpful and professional, which may not match your needsDescribe the tone in plain language: "Make this more conversational" or "This should sound authoritative and formal." Provide a writing sample in the style you want.

The Iteration Mindset

Your first prompt rarely produces a perfect result—and that's expected. Think of your initial prompt as the start of a conversation, not a one-shot request.

  • Treat first drafts as starting points: review what Claude produces, identify what's working and what isn't, then refine.
  • Give specific feedback: "Cut the first two paragraphs and make the conclusion more action-oriented" is more useful than "Make it shorter."
  • Know when to start fresh: if a conversation has gone off track, opening a new chat with a clearer prompt is often faster than trying to redirect it.

Tip

When iterating, change one thing at a time—tone, length, structure, or detail level—so you can identify what made the difference.

Key Takeaway

Most Claude challenges come from prompts that lack context, format guidance, or length constraints. The fix is almost always to add more specificity—and to treat each response as step one of a conversation, not a final answer.

1002. AI Fluency and the 4D Framework

Key Term

AI Fluency is the ability to collaborate effectively with AI tools—not just knowing which buttons to click, but developing the judgment to use AI well across different situations.

The 4D Framework was developed through research collaboration between Professor Rick Dakan (Ringling College of Art and Design) and Professor Joseph Feller (University College Cork). It identifies four core competencies that, when combined, help you get the most from your AI interactions.

CompetencyWhat It Means
DelegationDeciding what work should be done by humans, what by AI, and how to distribute tasks. Includes understanding your goals, AI capabilities, and making strategic choices about collaboration.
DescriptionEffectively communicating with AI. Includes clearly defining outputs, guiding AI processes, and specifying desired behaviors and interactions.
DiscernmentThoughtfully and critically evaluating AI outputs, processes, and behaviors. Includes assessing quality, accuracy, appropriateness, and identifying areas for improvement.
DiligenceUsing AI responsibly and ethically. Includes making thoughtful choices about AI systems, maintaining transparency, and taking accountability for AI-assisted work.

How the 4Ds Connect to This Course

The prompt framework from earlier lessons—setting the stage, defining the task, specifying rules—is rooted in Description. The troubleshooting techniques above draw on Discernment and Diligence. You've already been practicing these competencies throughout this course.

  • Delegation: choosing which tasks to hand off to Claude and which to keep
  • Description: writing clear prompts with context, constraints, and format expectations
  • Discernment: evaluating whether a response is accurate, complete, and appropriate
  • Diligence: verifying facts, disclosing AI's role, and staying accountable for the final output

Note

A free AI Fluency course is available that explores all four competencies in depth, with practical exercises and real-world applications.

Key Takeaway

AI Fluency is a learnable skill built on four competencies: Delegation, Description, Discernment, and Diligence. These map directly to the everyday choices you make when working with Claude—you've already been building them.

1103. Evaluating Claude for Your Workflows

Key Term

Evals (short for evaluations) are systematic ways to test how well Claude performs on specific types of tasks that matter to you. They help you build intuition for assessing Claude's outputs before relying on them for recurring work.

Your work is unique. Claude might excel at drafting marketing copy but need more guidance for technical documentation in your specific domain. Simple evals reveal where Claude adds the most value—and where you need to stay more involved.

  • Understand where Claude adds the most value in your specific workflow
  • Identify tasks where you'll need to provide more context or examples
  • Build confidence in Claude's outputs for recurring tasks before depending on them

A Simple Eval Approach

You don't need complex infrastructure to run evaluations. A practical approach uses examples you already have.

  1. Gather 5–10 examples of a task you do regularly—emails you've written, reports you've created, analyses you've completed.
  2. Write prompts that would generate similar outputs, including the context you'd naturally have when doing this work.
  3. Run your prompts and compare Claude's responses to your examples: Does Claude capture the key information? Is the tone and style appropriate? What's missing or could be improved?
  4. Adjust your prompts, add examples to show Claude what good looks like, or identify where human review is essential.

Tip

For data analysis tasks: find a dataset you've already analyzed manually, prompt Claude to perform the same analysis, then compare results. Note patterns—maybe Claude gets the right numbers but misses the overall trend. Use those observations to refine your prompts.

Key Takeaway

Running lightweight evals on tasks you already understand is the fastest way to know where to trust Claude and where to stay alert. Five to ten examples is enough to spot meaningful patterns in how Claude handles your specific work.

1204. The Delegation Diligence Loop

Key Term

The Delegation Diligence Loop is a testing process for building justified confidence in AI's analytical capabilities. It works by having AI reproduce analysis you've already completed on known data, then systematically evaluating what it gets right and wrong before applying it to new data.

The loop gives you a structured way to determine whether AI is appropriate for a specific analytical task—and exactly what context it needs to perform that task well.

  1. Identify a specific analytical task you do regularly that you want to delegate to AI.
  2. Find past data where you already completed the analysis—you need the correct answers in order to evaluate AI's results.
  3. Work with AI to reproduce your past analysis using clear description.
  4. Evaluate the results against what you know to be true. Note what AI got right and what it missed.
  5. Refine your approach based on the gaps and test again.
  6. If AI can match your known results, you have a validated approach for similar future tasks. If not after several refinements, you've learned this task shouldn't be delegated.

Rio, a program director at Valley Veterans Services, applied this loop to his quarterly analysis of program attendance and employment outcomes—work that regularly took him hours. In his first attempt, AI correctly identified the correlation between attendance and job placement but missed a critical insight around a combined housing and job placement program. Rio refined his description to request that AI consider program type, and AI caught the gap. He then tested cohort analysis by enrollment date, discovering that AI would infer enrollment dates when they weren't in the data—something he didn't want. Each gap became a documented note about what context to include in future prompts, leaving him with a validated approach and clear rules for when to apply it.

What If You're Not Comfortable with the Data?

If you're not familiar enough with a dataset to spot AI's process gaps yourself, AI can still help—this time as a thinking partner rather than a validator.

  • Bring your question or idea to AI and ask what a solution could look like, the same way you'd work with a data analyst on your team
  • Request clarifications and explanations as you go so you can follow the process and understand the final output
  • Use AI to handle tasks like writing Excel formulas or reformatting messy data
  • Keep asking questions until you understand the output well enough to take accountability for it

Warning

Validation builds confidence, but it doesn't eliminate responsibility. You're still accountable for checking that results make sense and for being transparent about AI's role in your analysis process.

Key Takeaway

The Delegation Diligence Loop turns abstract trust in AI into concrete, earned confidence. Test on data you already understand, document what works and what doesn't, and apply only what you've validated to new work—while staying accountable for the final result.

1301 The Claude Desktop App

The Claude desktop app gives you three ways to work with Claude: Chat for quick back-and-forth exchanges, Cowork for complex multi-source work, and Code for building software. Each mode surfaces controls and information tailored to the work it serves.

Key Term

The shared engine powering both Cowork and Code. It runs locally on your machine, can operate independently, spin up sub-agents, and sustain long-running tasks — making it capable of work that extends well beyond a single conversation turn.

ModeOptimized ForKey FeaturesTools & Extensions
ChatQuick exchanges: questions, brainstorming, iterative drafting, learning through dialogueQuick entry, dictation, screenshots, window sharingConnectors, Skills, Claude in Chrome
CoworkComplex or sustained work: research, analysis, file organization, finished documents and deliverablesFolder access, subagents, scheduled tasks, Dispatch, browser use, computer use, pluginsConnectors (local & remote), Skills, Claude in Chrome, Plugins, Computer Use
CodeBuilding software: writing, testing, running, and deploying codeAsk/Code/Plan modes, visual diffs, git integration, local and remote environmentsConnectors, Skills, Claude in Chrome, Plugins, Hooks

Cowork and Code share the same underlying engine. Both run Claude Code locally on your machine, both can handle larger tasks independently, and both can spin up sub-agents for sustained workflows. The difference is what they are pointed at: documents and research for Cowork, codebases for Code.

  • Connectors, Skills, and Claude in Chrome are available across all three modes
  • Plugins and Hooks are available in Cowork and Code, but not in Chat
  • Computer Use is exclusive to Cowork
  • Quick entry, dictation, and screenshots are exclusive to Chat (Mac)

Note

Cowork and Code are available on Pro, Max, Team, and Enterprise plans. Chat is available to all Claude users. New Cowork capabilities are added regularly.

Key Takeaway

The desktop app's three modes share a common engine but are each built around a different type of work. Picking the right mode means less friction and more capability for whatever you are trying to accomplish.

1402 Chat

Chat works the same as claude.ai but gains additional capabilities from running natively on your computer. It excels at questions, brainstorming, drafting, and iterative problem-solving — any work where you want fast back-and-forth rather than a long autonomous task.

Key Term

A native Mac feature in the Claude desktop app. Double-tapping the Option key opens Claude in a compact overlay window that stays on top as you switch between apps — letting you ask a question without leaving your current work.

  • Quick entry: Double-tap Option (Mac) to open Claude over whatever you are working on; it responds in an overlay that stays on top
  • Screenshots and window sharing: Capture a screenshot or share a window so Claude sees exactly what you are looking at — faster and more precise than describing your screen (Mac)
  • Dictation: Talk through a problem instead of typing, useful when thinking out loud or away from your keyboard (Mac)
  • Desktop connectors: Connect local tools and services so Claude can work with apps and data sitting directly on your machine

Quick entry keeps the app behind it active. Screenshot an unfamiliar dashboard, ask what the metrics mean, and read the answer without switching windows. Or open quick entry, switch to voice, talk through a presentation structure — Claude drafts the outline from what you said.

Tip

Add the Notes connector in Settings, then ask Claude to pull together everything from your notes on a specific topic, identify where things are unfinished, and check other connected tools to fill in the gaps. Claude reads the notes directly on your machine and synthesizes what is there.

Desktop connectors let Claude reach local tools and services — not just cloud APIs. This makes Chat useful for tasks that involve files, apps, or data on your computer rather than only in the cloud.

Key Takeaway

Chat is the fastest path to Claude for short, focused work. Quick entry, dictation, and screenshots eliminate the friction of context-switching, making it well suited for questions that arise while you are already deep in something else.

1503 Cowork

Cowork is designed for work that requires pulling from many sources, reasoning across all of them, and producing something finished — not a chat reply, but a deliverable. Before starting, Claude often asks a short set of questions to pin down scope, format, and constraints, then builds a reviewable plan in the sidebar.

Key Term

Background workers that Cowork spins up to handle parts of a complex task in parallel. Each subagent gets its own context for a subtask; Claude coordinates their outputs into one finished result.

  • Folder access: Point Claude to a folder; it reads what is relevant, works with it, and saves finished output back to the same place
  • Scheduled tasks: Define a recurring task (daily briefing, weekly roundup, morning inbox triage) and Claude runs it automatically each time the app is open, catching up on missed runs when you return
  • Subagents: Background workers that handle subtasks in parallel, coordinated by Claude into one deliverable
  • Dispatch: A persistent thread that lets you assign Cowork tasks from your phone via the Claude mobile app, using your desktop files and connectors while your computer is awake
  • Projects: Dedicated workspaces grouping related Cowork tasks with their own files, context, instructions, and memory — stored locally on your desktop

Browser use and computer use extend Cowork's reach beyond what you upload or share. With the Chrome connector, Claude can navigate websites, interact with pages, and pull data directly into the task — useful for competitor research or any site without an API. When no connector or Chrome integration exists, computer use lets Claude navigate your computer directly, clicking, typing, and opening apps.

Key Term

A Cowork capability that lets Claude control your computer directly when no connector or browser path is available. Claude follows a priority order — connectors first, then Chrome, then screen interaction — and shows a permission prompt before accessing each app. A blocklist lets you mark any app off-limits. Currently in research preview on Pro and Max plans, macOS only (Windows coming soon).

Plugins add capabilities Cowork does not have natively: live financial data, internal knowledge base search, or compliance-specific workflows. A protected environment limits Claude to the folders you explicitly share — it cannot read or modify anything outside them.

  • Query decisions across meeting notes, Slack, email, and slide decks in a single request
  • Research new markets without opening a browser tab — Cowork visits sites, reads reports, and delivers a structured brief with sources
  • Work through 50+ documents as if reviewing five — Claude reads every page and surfaces patterns that only emerge from reading the full set
  • Automate repetitive morning admin (messages, status updates, meeting prep) with a scheduled task set up once

Note

Cowork is available to Pro, Max, Team, and Enterprise users. Dispatch requires both the desktop and mobile Claude apps, with your computer awake and the desktop app open.

Key Takeaway

Cowork scales Claude's reach across sources, time, and tools. It is the right mode when the work involves more data than you would want to process manually, requires pulling from tools in different places, or needs to run on a schedule without your direct involvement.

1604 Code

The Code tab gives you Claude Code running directly inside the desktop app — a full development environment where Claude reads your codebase, writes and modifies files, runs terminal commands, and tracks every version with git. A built-in terminal shows commands as they run, and visual diffs show exactly what changed.

Key Term

A Code tab display showing precisely which lines changed after Claude modifies a file. In Ask mode, you review the diff and choose to accept or reject before anything is applied to your files.

Development Environments

Code lets you choose where work happens — on your local machine or in a cloud environment linked to a GitHub repository. The choice affects what Claude can access and whether sessions persist when the app closes.

EnvironmentHow It WorksBest For
LocalSelect a folder on your computer; Claude works directly with those files, can access local tools, and can run a development server you preview in your browserDay-to-day development, local tooling, browser preview of running code
Remote (Cloud)Connect a GitHub repository; Claude works in a cloud environment; sessions continue even if the app or your computer is closedLarge codebases, long refactors, keeping development off your local machine

Note

Git tracks every version of your work in Code mode, so you can always roll back to a previous state regardless of which environment you are using — local or remote.

Interaction Modes

Three interaction modes let you control how much Claude does before checking with you. You can switch between them as the work evolves — tighter control when reviewing unfamiliar code, more autonomy for routine tasks.

  • Ask: Claude proposes every change and waits for your approval — you review a visual diff and accept or reject before any file is modified
  • Code: Claude applies file changes automatically but checks with you before running any terminal commands
  • Plan: Claude outlines its full approach before touching anything; a dedicated plan viewer lets you review and revisit the strategy as work progresses

Tip

You can run multiple Code sessions across different projects simultaneously and filter them by status (Active or Archived) and environment (Local or Cloud) from the sidebar.

Note

The Code tab is available on Pro, Max, Team, and Enterprise plans.

Key Takeaway

Code brings the full power of Claude Code into one interface — git history, visual diffs, a built-in terminal, and a choice between local and cloud environments. The three interaction modes (Ask, Code, Plan) let you dial in exactly how much autonomy Claude has at each stage of the work.

1701 What Are Projects?

Key Term

A self-contained workspace in Claude with its own chat history, knowledge base, and customized instructions. Each project acts as a dedicated environment for a specific work stream.

Projects solve a common problem: having to re-upload files and re-explain context every time you start a new conversation. Instead of treating each chat as independent, a project gives Claude persistent memory of your documents, goals, and preferences across all conversations within it.

  • Store reference materials Claude should always have access to
  • Organize related chats around a specific topic or work area
  • Apply consistent behavior rules across every conversation
  • Collaborate with teammates who need access to the same shared context

When to Use a Project

Projects are most valuable for ongoing work—not one-off questions. A project makes sense when your workflow involves materials or rules you would otherwise repeat in every conversation.

  • Reference materials you use repeatedly (meeting notes, reports, historical data)
  • Consistent response requirements (always cite sources, always follow our template)
  • Team collaboration where multiple people work from the same foundation

Tip

Start with a specific use case rather than one project for everything. A focused project is easier to maintain and produces more consistent results.

Key Takeaway

A project is not just a folder—it is a persistent context layer. Every chat inside the project automatically inherits the same knowledge base and instructions, eliminating repetitive setup and keeping Claude aligned with your specific goals.

1802 Setting Up Your First Project

Creating a project takes only a few minutes and follows three sequential steps: basic setup, writing instructions, and building the knowledge base.

Step 1 — Basic Setup

  1. Hover over the left sidebar and click "Projects," or go to claude.ai/projects
  2. Click "+ New Project" in the upper right corner
  3. Give the project a descriptive name (e.g., "Q4 Marketing Campaign")
  4. Add a brief description of the project's purpose
  5. Choose visibility: private for personal use, or shared with your organization (Claude for Work users only)

Note

Claude does not read the project description directly. Its purpose is to help you and your teammates understand what the project is for.

Step 2 — Write Project Instructions

Project instructions tell Claude how to behave in every conversation within the project. Click "Instructions" to open the panel, write your instructions, then click "Save instructions."

Instruction typeExample
ContextThis project creates marketing content for a B2B software product.
ProcessFirst outline a blog structure, then write the draft.
Tone and styleUse a professional but conversational tone. Avoid jargon.
Specific requirementsAlways include a call-to-action at the end of marketing copy.
Automated workflowWhen I upload a meeting transcript, create a structured summary using this template.

Tip

Think of instructions as programming Claude's behavior for this project. The more specific you are, the more consistent Claude's responses will be.

Step 3 — Build the Knowledge Base

The knowledge base holds documents that Claude references across all chats in the project. Find the files menu on the right side of the project's main page and click "+" to add content.

  • Supported file types: PDF, DOCX, CSV, TXT, HTML, and more
  • Google Drive connection to link documents directly
  • Reference documents such as brand guidelines, style guides, and templates
  • Background materials such as research reports and requirements docs
  • Examples of work you want Claude to emulate

Tip

Name files descriptively. Claude uses filenames when retrieving information, so "Q4-2024-Brand-Guidelines.pdf" is more useful than "document1.pdf." You can also mention a specific filename in your message to focus Claude's search on that document.

Note

Context is not shared across separate chats within a project unless the information is added to the project knowledge base. Uploading a file during a conversation keeps it local to that chat only.

Key Takeaway

Three steps—name and describe, write instructions, upload documents—give Claude everything it needs to behave consistently and intelligently across every conversation in the project.

1903 How Projects Scale: RAG Mode

Key Term

A technique where Claude automatically searches and retrieves only the most relevant parts of your uploaded documents to answer a question, instead of loading all content into memory at once.

When the combined size of your project's knowledge base approaches the context window limit, Claude automatically switches to RAG mode. This happens without any action on your part—you will see a visual indicator that the project is RAG-enabled, but the experience remains the same.

  • Expands project capacity by up to 10x
  • Claude intelligently retrieves only the most relevant sections for each query
  • You can still upload documents, chat, and receive context-aware responses
  • No manual configuration required

Note

RAG mode is triggered automatically when the knowledge base is large. Smaller projects that fit within the context window do not use RAG and load all content directly.

If you upload content that you need for a single conversation without adding it to the knowledge base permanently, simply upload it during the conversation. It stays separate from the project knowledge and does not affect the knowledge base size.

Key Takeaway

Projects handle large content volumes automatically. RAG mode lets Claude intelligently search your knowledge base instead of loading everything at once, so you can keep adding documents without worrying about hitting limits.

2004 Collaboration and Permissions

For users on Claude for Work (Team and Enterprise) plans, projects can be shared with other members of the organization. This turns a personal workspace into a team resource where everyone benefits from the same context, instructions, and knowledge base.

Permission Levels

RoleWhat they can do
Can viewSee project contents, access knowledge, and chat — cannot make changes (read-only with discussion rights)
Can editModify instructions, update knowledge, manage members, and contribute to the project
Owner (creator)Full control including who sees the project; can share with specific people or the entire organization

Note

Team members receive an email notification when a project is shared with them. Shared projects appear in their "Shared with me" tab.

Sharing a Project

  1. Open the project you want to share
  2. Click "Share project" to the right of the project name
  3. Add members by name or email, or paste a list of email addresses for bulk sharing
  4. Alternatively, share with "Everyone at [your organization]" to make it discoverable in the Team tab

Multiple members can contribute documents, create chats, and work together within the same project environment. Owners can modify permissions or remove access at any time.

Key Takeaway

Permission levels let you balance openness and control: give teammates read-only access to protect instructions and knowledge, or grant edit rights to true collaborators. A single project can serve as a shared source of truth for an entire team.

2105 Example Projects and Best Practices

Projects work across a wide range of professional and personal contexts. The following examples show the kind of materials and use patterns that benefit most from a project structure.

Project typeWhat to uploadHow Claude helps
Q4 product launchProduct specs, competitive analysis, messaging notesDraft inquiries and documents with full product context
Research supportCompetitive review, user research data, customer feedbackSynthesize sources and draft reports consistently
Client account hubBrand guidelines, past deliverables, communication historyMatch client tone and reference specific context in proposals
Event planning workspaceVenue contracts, speaker bios, attendee dataGenerate run-of-show documents and communications
Job description generatorPast job descriptions, team charters, headcount request docsDraft descriptions reflecting actual team work and culture

Best Practices

  • Start focused — one specific use case per project, then expand as needed
  • Keep the knowledge base current — outdated documents lead to outdated responses
  • Write specific instructions — vague instructions produce inconsistent results
  • Name documents descriptively so Claude can find and relate the right files
  • Reference documents by name in your messages to help Claude focus its search

Warning

Context is not shared across separate chats unless it is in the knowledge base. If you need information available in every conversation, upload it to the project files — do not rely on it being present because you used it in a previous chat.

Additional project management optionsClick to expand

From the project menu (to the right of the project title) you can: star a project for quicker access from the sidebar, edit project details such as the name and description, archive a project to hide it without deleting it, or delete a project permanently. Chats within a project can also be made public so teammates can view and build on your work.

Key Takeaway

The most effective projects combine a focused scope, descriptive file names, specific instructions, and a regularly updated knowledge base. These habits ensure Claude always has accurate, relevant context and produces consistent results every time.

2201 What Artifacts Are

Key Term

A standalone, interactive output that Claude creates in a dedicated window alongside your conversation — rendered and ready to use rather than embedded in the chat.

When Claude generates a long document or complex code, that content is easy to lose in the scroll of a conversation. Artifacts fix this by placing the output in a separate pane where you can preview it, interact with it, and act on it directly.

Claude applies four criteria to decide whether content becomes an artifact:

  • Significant and self-contained — typically over 15 lines
  • Likely to be edited, iterated on, or reused
  • Complex enough to stand on its own without the surrounding conversation
  • Something you will want to reference or use later

When an artifact appears, it opens in a window to the right of your chat. From there you can toggle between a rendered preview and the underlying source, copy the content to your clipboard, or download the file to your computer.

Tip

If Claude responds in the chat instead of creating an artifact for something substantial, say "Create this as an artifact" or "Show me this in an artifact" to trigger the dedicated window.

Note

Your chat history stays private regardless of what you do with an artifact. Publishing or sharing an artifact never exposes the conversation behind it.

Key Takeaway

Artifacts are rendered, self-contained outputs that Claude creates automatically when content is substantial, reusable, and complex enough to stand alone. You can always request one explicitly if Claude defaults to a chat reply instead.

2302 Artifact Types

Claude can create six categories of artifacts. Each suits a different kind of deliverable — the right choice depends on what you need to do with the output.

TypeFormats / TechnologiesBest For
DocumentsMarkdown, plain text, Word, PDF, PowerPoint, ExcelReports, meeting notes, project plans, blog posts
Code snippetsPython, JavaScript, C++, and moreReusable scripts, functions, or configuration files
HTML pagesHTML + CSS + JavaScript (single file)Landing pages, forms, interactive demos, prototypes
SVG imagesScalable Vector GraphicsLogos, icons, illustrations rendered directly in the window
Mermaid diagramsMermaid syntaxFlowcharts, sequence diagrams, Gantt charts, org charts
React componentsReact with live logicCalculators, dashboards, games, data visualizations

Key Term

An interactive UI element built with the React framework. Unlike a static mockup, a React component artifact includes actual logic and responds to user input — a calculator that computes, a dashboard that filters data in real time.

Key Term

A diagram defined in plain text using Mermaid syntax. Claude converts your description of relationships or processes into rendered flowcharts, sequence diagrams, Gantt charts, and org charts.

SVG images render directly in the artifact window, so you see the finished graphic immediately rather than raw markup. HTML artifacts combine HTML, CSS, and JavaScript into a single file — useful for self-contained prototypes you can open in any browser without a server.

Note

Claude may generate visual diagrams such as flowcharts as HTML (using Imagine) in addition to code-based Mermaid artifacts. The format depends on how Claude interprets your request.

Document artifacts support export formats including Word, PDF, PowerPoint, and Excel — making them suitable for content that needs to move outside Claude into other tools or workflows.

Key Takeaway

Choosing the right artifact type shapes the usefulness of the output. Use documents for exportable text, code snippets for scripts, HTML for browser-ready prototypes, SVG for graphics, Mermaid for diagrams, and React for interactive logic-driven tools.

2403 Creating and Refining Artifacts

Creating an artifact starts with describing what you want. Claude determines from your request whether the output qualifies as an artifact. The more precise your description, the more useful the result.

  • "Create a flowchart showing our customer onboarding process"
  • "Build an interactive dashboard that lets me input monthly expenses and see a breakdown"
  • "Design a landing page for a productivity app with a hero section and feature list"
  • "Write a project brief template I can reuse for new initiatives"

Tip

"Build a budget tracker" is a starting point, but "Build a monthly budget tracker where I can input expenses by category, see a pie chart breakdown, and get a warning when I'm over budget" produces a far more useful artifact.

Describing the end user changes the output meaningfully. "This flowchart is for new employees" leads to different design choices than "This flowchart is for the engineering team." Give Claude that context before it generates.

Iterating on an Artifact

Once an artifact exists, you refine it through the conversation. Each follow-up request can target one specific change — add a feature, adjust a layout, fix a calculation — without rebuilding from scratch.

Tip

Ask Claude to add one feature or make one change at a time. This makes it easier to identify what is working and to catch issues early before they compound into larger problems.

  1. Start with a clear, specific initial request
  2. Review the artifact in the preview pane
  3. Request one targeted change per follow-up message
  4. Toggle to the code view to understand what was generated
  5. Download or copy the artifact when it meets your needs

Key Takeaway

Artifact quality improves with specificity and iteration. Name what you want, describe who will use it, and refine one change at a time. Claude regenerates within the artifact window without altering your chat.

2504 Sharing and Publishing Artifacts

Three sharing paths are available after creating something useful. Which one to use depends on your Claude plan and your intended audience.

Copy and Download

Copy and download buttons sit in the lower right corner of the artifact window. Use them to grab the content for use outside Claude — pasting into a document, committing to a repository, attaching to an email, or opening in a browser.

  • Copy: puts the raw content into your clipboard
  • Download: saves the artifact as a file to your computer
  • View code: shows exactly what Claude generated under the hood

Note

Copy and download are available to all users on any plan. Recipients need no Claude account to use content shared this way.

Share Within Your Organization

Team and Enterprise users on Claude for Work can share artifacts internally with colleagues. The shared artifact stays within the organization — recipients must belong to the same Claude for Work account to access it.

Key Term

The Team and Enterprise tiers of Claude designed for organizational use, with features including internal artifact sharing, access controls, and team authentication.

Note

Internal sharing requires team authentication. Anyone outside the organization cannot access an internally shared artifact, even with the link.

Publish Publicly

Free, Pro, and Max users can publish an artifact to make it accessible to anyone with the link. Click "Share" or "Publish" in the upper right corner of the artifact. To remove access, return to that artifact and remove public access — unpublishing is available at any time.

  • Only the selected version becomes public — your chat remains private
  • Viewers do not need a Claude account to see or interact with the artifact
  • Others can "remix" the artifact — opening it in their own Claude session to modify and build on it
  • Published artifacts are not indexed by search engines and will not appear in Google results

Warning

A published artifact is publicly accessible to anyone who has the link, with or without a Claude account. Do not publish content that contains sensitive or confidential information.

Key Takeaway

Three sharing options cover different audiences: copy or download for personal use, internal sharing for team collaboration on Claude for Work, and public publishing for open access. Publishing never exposes your chat, but the artifact itself is visible to anyone with the link.

2601 What Skills Are

Key Term

Folders of instructions, scripts, and resources that Claude loads dynamically to improve performance on specialized tasks. They function as expertise packages that teach Claude how to complete specific tasks in a repeatable, consistent way.

Skills run behind the scenes when you ask Claude to create Excel spreadsheets, PowerPoint presentations, Word documents, or PDFs. Beyond document creation, Skills can encode entire repeatable workflows—a quarterly variance analysis, a brand voice review process, or a compliance checklist—so Claude follows the same rigorous steps every time.

Note

Skills are currently a feature preview for Pro, Max, Team, and Enterprise plans. Free plan users can read along to understand the concept but cannot use Skills hands-on.

The core value of Skills is consistency. When a workflow is captured in a Skill, Claude executes the same methodology each time it is invoked—reducing variation and eliminating the need to re-explain your process in every conversation.

  • Excel spreadsheets with formulas and structured data
  • PowerPoint presentations built from source material
  • Word documents with consistent formatting and structure
  • PDF reports that summarize and organize data
  • Custom repeatable workflows specific to your organization

When Claude uses a Skill, it is mentioned in Claude's chain of thought as it works through your request. The final output is a downloadable file you can save to your computer or directly to Google Drive.

Key Takeaway

Skills are reusable expertise packages that let Claude execute specialized tasks and repeatable workflows consistently—without you having to re-explain the process each time.

2702 Types of Skills

There are two categories of Skills: those built and maintained by Anthropic, and those you or your organization create for your own workflows.

Anthropic Skills

Anthropic Skills are created and maintained by Anthropic. They provide enhanced document creation capabilities for Excel, Word, PowerPoint, and PDF files. These Skills are available to all paid users.

  • Excel spreadsheets (.xlsx) with formulas and formatting
  • PowerPoint presentations (.pptx)
  • Word documents (.docx)
  • PDF files (.pdf)

Tip

You do not need to do anything special to use Anthropic's built-in Skills. Claude detects when your request is relevant and invokes the appropriate Skill automatically.

Custom Skills

Key Term

Skills created by you or your organization to encode specialized workflows, domain-specific tasks, brand guidelines, or internal methodologies that Anthropic's built-in Skills do not cover.

Custom Skills let you teach Claude your specific ways of working. Once created, they are private to your individual account and automatically invoked whenever you work on relevant tasks.

  • Applying company brand guidelines to presentations
  • Structuring meeting notes in a specific internal format
  • Executing your organization's data analysis workflows
  • Running compliance checklists with consistent steps
  • Drafting documents that follow internal style guides
CategoryCreated byAvailable toInvocation
Anthropic SkillsAnthropicAll paid usersAutomatic
Custom SkillsYou or your organizationYour account onlyAutomatic when relevant

Key Takeaway

Anthropic Skills handle common document creation tasks automatically for all paid users. Custom Skills extend this to your organization's unique workflows and are private to your account.

2803 Enabling and Managing Skills

Note

Skills require the Code execution and file creation capability to be enabled. Skills run inside Claude's secure sandboxed computing environment and cannot function without it.

Enabling Skills takes just a few steps in your account settings. The process is the same for Pro and Max plans; Team and Enterprise plans have additional organization-level controls.

  1. Navigate to Settings > Capabilities
  2. Ensure Code execution and file creation is toggled on
  3. Scroll to the Skills section
  4. Toggle individual Skills on or off as needed

Note

On Enterprise plans, organization Owners must first enable both Code execution and Skills in Admin settings before individual members can access them. On Team plans, the feature preview is enabled by default at the organization level.

Once enabled, all available Skills—both Anthropic's built-in ones and any custom Skills you have uploaded—appear listed in your settings. You can toggle each one individually to control which Skills are active.

Tip

The Customize tab in the left sidebar shows all Skills available to you. From there you can view, edit, or manage both built-in and custom Skills.

To work with existing files using Skills, you will also need to allow limited network access when prompted. This enables Claude to access your uploaded files within its contained environment and produce updated output versions.

Key Takeaway

Skills are activated through Settings > Capabilities and require Code execution to be enabled first. Enterprise admins control organization-level access before members can enable Skills individually.

2904 Using Skills in Practice

The primary design goal of Skills is transparency—you should not need to think about them. Claude selects and applies the appropriate Skill based on the nature of your request.

  • "Create an Excel spreadsheet tracking monthly expenses with formulas for totals"
  • "Turn this meeting notes document into a PowerPoint presentation"
  • "Generate a PDF report summarizing this data"
  • "Build a financial model in Excel with scenario analysis"

Each of these prompts automatically triggers the relevant Skill. You can see which Skill is being used by watching Claude's chain of thought as it works through your request.

Working with Existing Files

Skills also enable Claude to work with files you upload. Provide an .xlsx, .pptx, .docx, or .pdf file, and Claude will create an updated version—performing analyses, adding slides, or suggesting edits—without modifying your original file.

Note

In Chat, Claude creates a new version of the document rather than editing the original in place. When done, you can download the result or open it directly in Google Drive.

Warning

Because Skills can include executable code, only install custom Skills from trusted sources. If a Skill comes from an external source you did not create, review its contents before use to understand what it does.

Anthropic's built-in Skills are tested and maintained by Anthropic. Custom Skills you create are private to your individual account and are not shared with other users.

Key Takeaway

Claude selects and runs Skills automatically based on your request. You can also upload existing files for Skills to process—Claude returns a new version you can download or save to Drive, without altering your original.

3005 Creating Custom Skills

The most accessible way to create a custom Skill is through conversation with Claude. No coding or manual file creation is required—Claude handles the technical structure for you.

The Creation Process

  1. Start a new chat and tell Claude what you want to create — for example, "I want to create a skill for writing quarterly business reviews"
  2. Answer Claude's interview questions about your workflow, desired outputs, and example use cases
  3. Upload reference materials such as templates, style guides, brand assets, or past work you are proud of
  4. Save the Skill file Claude generates — it immediately appears in your Skills list and is ready to use

Tip

Skills improve over time. Ask Claude to edit a Skill and it updates the files for you—no need to rebuild from scratch.

The interview step is where most of the value is created. Claude asks targeted questions: what should this Skill do, what makes good output for this type of work, and when would you use it. Providing concrete reference materials—templates, examples of past work, style guides—gives Claude specific anchors for the Skill's behavior.

Managing Your Skills

Once saved, your custom Skill appears alongside Anthropic's built-in Skills. Claude automatically invokes it whenever you work on a relevant task—no manual triggering needed.

Note

The Customize tab in the left sidebar shows all Skills available to you. You can view Skills, edit them manually, or edit them by chatting with Claude directly from this tab.

Because Skills are invoked automatically, the more precisely you define the Skill's scope during creation, the more reliably Claude will apply it at the right moments.

Key Takeaway

Creating a custom Skill requires only a conversation with Claude—describe your workflow, answer its questions, provide reference materials, and save the generated file. Skills improve with iteration and are managed from the Customize tab.

3106 Skills vs. Projects

Both Skills and Projects give Claude additional context, but they serve fundamentally different roles: projects store knowledge, skills perform tasks.

Key Term

Knowledge hubs that hold reference materials—project specs, meeting notes, research documents—which Claude draws on across every conversation within that project.

ProjectsSkills
PurposeStore knowledge Claude referencesDefine processes Claude executes
Best forLong-term context, reference materials, team collaborationRepeatable workflows, multi-step tasks, consistent methodology
ExampleCustomer hub, research buddy, feedback generatorBrand guidelines, blog drafting, PDF creation
PersistenceKnowledge available across all chats in the projectInstructions applied when the Skill is invoked

The two features complement each other. A Skill can reference knowledge stored in a Project—for example, a "customer call prep" Skill might pull from customer profiles uploaded to a Project's knowledge base. The Project provides the what (information); the Skill provides the how (process).

Tip

Use a Project when you need Claude to remember reference material across conversations. Use a Skill when you need Claude to follow a specific process or methodology consistently.

  • Projects: passive reference, always available within the project context
  • Skills: active procedures, triggered when the task matches the Skill's purpose
  • Combined: a Skill draws on Project knowledge to execute a task with full context

A customer support team might use a Project to store product documentation and FAQs, while a Skill encodes the step-by-step process for drafting responses that meet their quality standards. Each tool does what the other cannot.

Key Takeaway

Projects and Skills are complementary tools—Projects hold the information Claude needs to know, Skills define the steps Claude should follow. Used together, they give Claude both knowledge and process for your most important work.

3201. What Connectors Are

Connectors give Claude access to the tools, files, and data you already use at work. Instead of copying and pasting information into each conversation, Claude can read from and act within your connected applications directly.

Key Term

A connector is an integration that links Claude to an external application or service, allowing Claude to read information and perform actions within that tool on your behalf.

Depending on the connector and the permissions you grant, Claude can search your files, retrieve documents, analyze data, create content, update records, and execute tasks—all from within a single conversation.

Key Term

MCP is the open standard that powers connectors. Think of it like USB-C for AI: a universal interface that lets Claude connect to many different applications through one consistent protocol. Because MCP is open, any developer can build a connector for any tool.

There are two categories of connectors. Web connectors link Claude to cloud services accessed through the browser. Desktop extensions run locally through the Claude Desktop app and provide access to native applications and your local file system.

TypeWhere it runsExamples
Web connectorBrowser / claude.aiGoogle Drive, Notion, Slack, Asana, Linear, Stripe
Desktop extensionClaude Desktop app (macOS / Windows)Local file access, browser control, Figma

Web connectors are the easier starting point because they work in any browser and require no additional software. Desktop extensions expand Claude's reach to local applications but require installing the Claude Desktop app first.

Key Takeaway

Connectors turn Claude into a collaborator that works with your actual data. MCP is the universal standard that makes this possible, and it comes in two forms: web connectors for cloud services and desktop extensions for local tools.

3302. Finding and Setting Up Connectors

Anthropic maintains a directory of recommended connectors organized into two tabs: Web (cloud services) and Desktop extensions (local tools). You can access it directly at claude.ai/directory, or by clicking the + button in the lower left of the chat window and selecting Connectors.

Note

The Web tab lists services such as Gmail, Notion, Slack, Asana, Linear, and Stripe. The Desktop extensions tab lists tools that run on your computer through the Claude Desktop app.

Setting Up a Web Connector

Setting up a web connector takes only a few minutes and follows the same pattern regardless of which service you choose.

  1. Navigate to the connectors directory, or open + > Connectors in any chat
  2. Select the connector you want and click Connect
  3. Sign in with your existing credentials on the service's login page
  4. Review the permissions Claude is requesting and authorize access
  5. Return to Claude and test with a simple request, such as "Can you access my [tool name]?"

Tip

After authorizing a connector, send Claude a simple access request before relying on it for real work. This confirms the connection is active and helps you understand what Claude can see.

Installing Desktop Extensions

Desktop extensions require the Claude Desktop app, which runs on macOS and Windows. They let Claude interact with local applications, your file system, and native features that are not accessible through the browser.

  1. Download and install the Claude Desktop app
  2. Open the app and navigate to Settings > Extensions
  3. Browse available extensions and click Install
  4. Follow any additional setup steps specific to that extension

Note

Desktop extensions include local file access for reading and organizing documents, browser control for automated web tasks, and native application integration such as Figma for design work.

Key Takeaway

The connectors directory is the starting point for both types. Web connectors need only a browser and a login; desktop extensions require the Claude Desktop app and are installed through Settings > Extensions.

3403. Using Connectors in Your Work

Once a connector is active, Claude draws on it automatically when your request requires information from that source. You don't need to name the connector in every message—just ask as you would ask a colleague who has access to the same tools.

Project Management

With a project management connector such as Asana, Linear, or Jira, Claude can query task status, create new items, and summarize project progress without you switching applications.

  • "What are my highest priority tasks due this week?"
  • "Create a new task for reviewing the Q4 budget proposal"
  • "Summarize the status of our product launch project"

Tip

You can connect multiple tools at once. For example, ask Claude to cross-reference a Slack conversation with an Asana task board to produce a single status update—no app switching required.

Communication and Documentation

Communication connectors such as Slack and Gmail let Claude search past conversations and draft replies. Documentation connectors such as Notion, Google Drive, and Confluence let Claude retrieve and summarize internal knowledge.

  • "Find the email thread where we discussed the vendor contract"
  • "Draft a reply to the latest message in the #marketing channel"
  • "Search our documentation for our brand voice guidelines"
  • "Summarize the meeting notes from last week's product review"
CategoryConnected toolsWhat Claude can do
Project managementAsana, Linear, JiraQuery tasks, create items, summarize project status
CommunicationSlack, GmailSearch threads, draft replies, retrieve team decisions
DocumentationNotion, Google Drive, ConfluenceSearch docs, summarize meeting notes, retrieve guidelines
Business toolsStripe, PayPal, SalesforceShow revenue trends, check deal status, list transactions

Key Takeaway

Connected tools replace copy-paste workflows with direct queries. The highest-value requests are those that pull from two or more sources—something no single application can do on its own.

3504. Security and Permissions

When you connect Claude to an external service, you grant it access to read—and in some cases modify—data within that service. Understanding how permissions work helps you make informed decisions about what to connect.

Warning

Connecting a tool means Claude can act within it. Review the specific permissions each connector requests before authorizing access, and only connect services where you are comfortable with those permissions.

How Permissions Work

Connector permissions are scoped to what the connector needs. You can toggle individual permissions on and off within each application's settings menu. Claude can only access data you have access to—connecting your work email does not expose your CEO's inbox, only your own.

  • Scoped access: each connector requests only the permissions it needs, not blanket access
  • Your data only: Claude sees what you see—nothing from other users' accounts
  • Revocable at any time: disconnect through Claude's settings or through the third-party service's own security settings

Tip

Removing a connector immediately stops Claude from accessing that service. You can do this either from Claude's settings or from the connected service's own security or account settings.

Custom Connectors and Trusted Sources

Beyond Anthropic's directory, you can find or build custom connectors—the MCP standard is open, so anyone can create one. Apply the same caution you would with Skills: only install connectors from sources you trust.

Warning

A custom connector can request broad permissions. Before installing one outside the official directory, verify who built it and what access it requires.

  • Check the connector's publisher before installing
  • Review permissions before authorizing—only approve what the connector genuinely needs
  • Remove connectors you no longer use to reduce your permission surface

Key Takeaway

Connector permissions are scoped, bounded to your own data, and fully revocable. Treat them like app permissions on a phone: review what each one requests, grant only what you need, and remove access when it is no longer required.

3601 What Enterprise Search Is

Key Term

A dedicated feature that adds an "Ask {Your Org Name}" option to your Claude sidebar. It connects to your organization's tools and data sources to find and synthesize knowledge across the company.

Enterprise Search works like a pre-built Project for your entire organization. Your company's knowledge base is already loaded, so you can ask questions immediately without setting up connectors yourself each time.

Note

Enterprise Search is available on Team and Enterprise plans only, and must be enabled by a workspace admin. Users on Free, Pro, or Max plans do not have access to this feature.

Unlike regular chats with connectors enabled, Enterprise Search is specifically designed for information gathering. It uses custom instructions configured by the Anthropic team, making it optimized for organizational knowledge retrieval rather than general conversation.

Tip

Regular Claude chats can use connectors too, but Enterprise Search is purpose-built for synthesizing information across an entire organization — not just one-off lookups.

When you submit a question, Claude searches across all connected tools simultaneously — SharePoint documents, Slack conversations, Gmail threads, Google Drive files — and returns a single unified response with citations so you can trace every fact back to its source.

Key Takeaway

Enterprise Search is a pre-configured, organization-wide knowledge layer inside Claude. It searches multiple tools at once, synthesizes results, and always cites sources — making it faster than asking colleagues or hunting through systems manually.

3702 Questions Enterprise Search Can Answer

Enterprise Search is most valuable for questions that span multiple systems or require pulling together information from across the organization. Five distinct use-case patterns cover the majority of practical needs.

Use CaseExample Questions
Getting up to speed"What happened yesterday while I was out?" / "What are the current blockers on the Platform project?"
Policy and process"What is our remote work policy?" / "How do I submit an expense report?"
Research and analysis"What are the main reasons customers cite for choosing competitors?" / "Summarize discussions about the Q4 product roadmap"
Onboarding new team members"How does our authentication system work?" / "Who should I talk to about the billing system?"
Performance and project tracking"What were the key decisions from last week's leadership meetings?" / "Summarize team contributions to the Infrastructure initiative"

Tip

Questions that span multiple sources — like "summarize what happened across the business last week" — benefit most from Enterprise Search because Claude reads all connected tools at once rather than one at a time.

Onboarding is a particularly strong use case. New team members can ask how systems work, who owns what area, and what tools the team uses — questions that normally require interrupting experienced colleagues.

Note

Every Enterprise Search response includes source citations. You can follow these links to read the original document, message, or file for full context.

Key Takeaway

Enterprise Search handles five broad question categories: catching up, policy lookups, research and competitive analysis, onboarding, and project tracking. Any question that would normally require checking multiple systems is a good candidate.

Setup follows a two-step sequence: an admin (Owner) configures the organization-level integration first, then individual users authenticate their own accounts to start searching.

Admin Configuration

The Enterprise Search project is enabled by default for all Team and Enterprise organizations, but an Owner must complete initial setup before anyone can use it.

  1. Click "Ask Your Org" in the left sidebar
  2. Click "Set up for your org" to begin (or "Disable" to turn the feature off)
  3. Connect a Documents connector (Google Drive or SharePoint) and a Chat connector (Slack or Microsoft Teams) — both are required; Email is optional
  4. Click "+ Add more" to add any additional tools the team needs
  5. Customize the project name — it appears as "Ask [Name]" in everyone's sidebar
  6. Add a description, then click "Finish set up"

Warning

Admins must connect at least one Documents source and one Chat source. Email is recommended but optional. The project does not become available to team members until setup is complete.

User Authentication

Once an admin completes setup, the "Ask {Org Name}" project appears starred in every team member's sidebar. Users then connect their personal accounts to the services they want to search.

  1. Click the project in your sidebar
  2. Follow the guided onboarding flow to connect to recommended services
  3. Authenticate with each service you want to search (Slack, Google, Microsoft 365, etc.)
  4. Start asking questions about your organization's knowledge

Tip

You can always add more connectors after initial setup by clicking "Connect" in the project's Instructions section. The more connectors you enable, the more comprehensive your search results will be.

Key Takeaway

Setup is a two-phase process: Owners configure the organization once, then individual users authenticate their own accounts. Admins must connect at least one Documents and one Chat source before team members can use the feature.

3904 Security and Permissions

A common concern when connecting organizational data to an AI tool is whether sensitive information might become visible to people who shouldn't see it. Enterprise Search addresses this through permission inheritance.

Key Term

Enterprise Search only surfaces content that the requesting user already has permission to access in the original connected tool. If you cannot see a file in SharePoint directly, Enterprise Search will not return it either.

  • Search results reflect your existing access rights in each connected tool — no new permissions are granted
  • Your conversations with Enterprise Search remain private
  • Connected data is not indexed or stored separately by Claude

Note

Claude does not build its own copy of your organizational data. It queries the connected tools at search time using your credentials, so data governance stays with the original systems.

This design means that access control stays where it was originally set — in SharePoint, Google Drive, Slack, or whichever system owns the data. Enterprise Search queries those systems on your behalf rather than ingesting and re-storing the content.

Key Takeaway

Enterprise Search enforces the same permissions as the underlying tools — users see only what they already have access to. Conversations are private, and data is queried live rather than copied into a separate index.

4001 What Is Research?

Key Term

An advanced Claude feature that transforms it from a conversational assistant into a systematic investigator. Instead of answering from existing knowledge, Research runs many searches that build on each other, then synthesizes findings from across the web and connected integrations into a comprehensive report with citations.

Standard Claude responses draw on what the model already knows. Research changes this by actively gathering new information—autonomously deciding what to search next based on what it finds, pursuing leads, and filling gaps without you needing to direct each step.

Think of it as a skilled research assistant who can spend hours gathering information, cross-referencing sources, and compiling a comprehensive report—except the work completes in minutes rather than hours.

Note

Most Research reports finish in 5 to 15 minutes. Complex investigations may take up to 45 minutes—work that would typically require hours of manual research.

  • Conducts multiple searches that build on each other
  • Autonomously decides what to investigate next based on prior findings
  • Explores different angles of your question automatically
  • Synthesizes findings from the web and any connected integrations
  • Delivers a well-organized report with verifiable citations

Research is particularly valuable when a thorough understanding requires pulling together information from multiple sources, comparing different perspectives, and synthesizing findings into actionable insights. It is not designed for quick factual lookups.

Note

When Research is enabled, extended thinking activates automatically. This powerful combination lets Claude plan its approach thoughtfully, break complex requests into manageable pieces, and then gather comprehensive information across many sources.

Key Takeaway

Research turns Claude into an autonomous investigator that plans, searches repeatedly, and synthesizes across multiple sources—delivering in minutes what manual research would take hours to produce.

4102 When to Use Research

Choosing the right Claude capability for your task saves time and produces better results. Research is powerful but intentionally slower than a quick web search—use it when thoroughness and citations matter more than speed.

CapabilityBest forNot ideal for
ResearchComprehensive multi-source reports, competitive analysis, synthesizing documents and web findingsQuick facts or single-source answers
Web searchSpecific facts, current prices, simple lookups requiring one or two sourcesDeep analysis or multi-angle investigations
Extended thinkingComplex reasoning, math, code debugging, logical analysis—no external data neededTasks requiring real-time or external information
Enterprise searchQuestions about internal company knowledge: policies, processes, past decisionsPublic web information or personal integrations

Tasks where Research excels

Research produces the most value for tasks where thoroughness, multiple perspectives, and verifiable citations matter more than how fast you get an answer.

  • Market analysis and competitive research
  • Planning complex projects like team offsites or product launches
  • Synthesizing information from email, calendar, and documents
  • Creating technical documentation that draws from multiple sources
  • Preparing briefings that require current, verified information

Tip

Research is especially well-suited for evaluating competitors or vendor options—tasks that require comparing many sources and summarizing findings into a single actionable report.

When to choose a lighter tool

If you need today's stock price, a company's address, or any answer that requires only one or two sources, use web search instead. Research would spend time gathering information you simply do not need.

Extended thinking is the better choice when you are working on math problems, debugging code, or logical analysis—tasks where the answer comes from reasoning through a problem rather than gathering external information.

Note

Enterprise search answers questions specific to your company (policies, processes, past decisions). Research focuses on the public web and personal integrations. They serve different knowledge scopes and can complement each other.

Key Takeaway

Research is the right tool when you need a thorough, multi-source investigation with citations. For quick facts, choose web search; for pure reasoning tasks, choose extended thinking; for internal company knowledge, choose enterprise search.

4203 How Research Works

Key Term

A process where an AI operates autonomously—making decisions and taking sequential actions without human direction at each step. Research is agentic: Claude decides what to search next based on what it has already found, pursuing leads and filling gaps on its own.

When you enable Research, Claude follows a structured four-step cycle. Each step builds on the previous one, moving from planning through searching to synthesis and final citation.

Planning and searching

Step 1: Claude activates extended thinking to break down your request, identify what information it needs, and plan how to investigate different angles of your question before any searches begin.

Step 2: Rather than running a single search, Claude conducts many searches that build on each other. It determines what to investigate next based on what it finds, pursuing promising leads and filling in gaps as it goes.

Warning

Web search must be enabled for Research to function. You can turn it on from the same + menu used to activate Research. Without it, Research cannot run.

Synthesizing and citing

Step 3: After gathering information from multiple sources—including the web and any connected integrations like Gmail, Google Calendar, or Google Drive—Claude compiles everything into a comprehensive, well-organized report.

Step 4: Every claim in a Research report links back to its source. This makes it straightforward to verify information and dig deeper into specific findings when needed.

Tip

Citations are included in every Research report so you can check sources yourself quickly. Treat the report as a strong starting point, and follow citations to verify the facts that matter most to your decision.

Key Takeaway

Research is a four-step agentic cycle—plan, search repeatedly, synthesize from all sources, then cite every claim. Extended thinking and multi-step searching are what separate it from a simple web query.

4304 Writing Effective Research Prompts

Because Research can take between 5 and 45 minutes depending on complexity, a well-crafted prompt pays dividends. Vague prompts produce broad reports; specific prompts produce focused, actionable ones.

  1. Be specific about your goals—state what decision or outcome the research supports
  2. Specify the sections or structure you want—Claude organizes findings around the structure you provide
  3. Include relevant constraints such as budget ranges, timelines, or geographic requirements
  4. Ask Claude to help refine your prompt before enabling Research if you are unsure how to frame your question

Tip

Before activating Research, ask Claude to help you write a better Research prompt. This costs almost no time and can significantly improve the quality of the final report.

Weak promptStrong prompt
Tell me about the EV marketAnalyze the electric vehicle battery market—identify key players, technology trends, and supply chain challenges that might affect investment decisions.
Find venue options for our offsiteCompare venue options for a team offsite including: location and accessibility, meeting space and amenities, catering options, and pricing considerations.

The strong prompts share a pattern: they name a specific outcome (investment decisions, venue selection), list the dimensions to cover, and include implicit constraints that help Claude focus on relevant options rather than casting too wide a net.

Note

Click the + button at the bottom left of your chat interface, then select Research from the menu. It appears highlighted once active. Enter your prompt and submit—progress indicators will appear as Claude works in the background.

Example: structuring a competitive analysis promptClick to expand

Instead of 'Research our competitors,' try: 'Analyze the top five competitors in the B2B project management software space. For each: describe their core product positioning, pricing model, key customer segments, and recent product announcements. Conclude with a comparison table highlighting differentiation opportunities for us.' This gives Claude a clear framework to organize its findings around.

Key Takeaway

The quality of your Research prompt directly shapes the usefulness of the report. Name your goal, list the sections you want, and add any constraints—this upfront investment multiplies when Research runs for up to 45 minutes.

4405 Research with Connected Integrations

When Google Workspace or other integrations are connected, Research gains access to your own context—emails, calendar events, and documents—alongside public web sources. This lets Claude bridge internal and external knowledge in a single report.

  • Summarize email and Slack discussions about a project, then research industry best practices for similar initiatives
  • Review calendar commitments for an upcoming week and research each company you are meeting with
  • Find internal documents about your pricing strategy and compare them to how competitors are positioning themselves publicly

Tip

Direct Claude explicitly by saying 'Pull relevant context from my Google Drive' or 'Include insights from my recent emails on this topic' directly in your prompt. Without this guidance, Claude decides on its own which sources to use.

You can also turn off web search entirely to limit Research to your connected tools only. This is useful for internal-only questions—for example, finding what your team discussed about a product launch across Slack messages and shared documents.

ModeSources usedBest for
Research (web on)Web + connected integrationsCombining public information with personal or company context
Research (web off)Connected integrations onlyInternal-only questions across your emails, documents, and calendar

Note

Connected integrations are configured through the same + menu used to enable Research. Google Workspace (Gmail, Google Calendar, Google Drive) is the primary integration example covered in this course.

Disabling web search and querying only internal tools turns Research into a personal knowledge management layer—useful for onboarding, tracking project history, and reviewing decisions made across scattered documents.

Key Takeaway

Connected integrations extend Research beyond the public web into your own context. Combine both for the richest reports, or disable web search to focus exclusively on your internal knowledge base.

4501. Claude Across Professional Roles

Claude applies to virtually every professional role. The use cases here are organized by job function, so you can quickly identify which ones match your daily work and start applying them right away.

Key Term

A curated collection of step-by-step guides published by Anthropic, showing how to apply Claude to specific professional tasks across roles and industries. Each use case in this lesson links to a detailed guide in the gallery.

The gallery continues to grow, making it a useful resource to revisit as your role or responsibilities change over time.

General Professional Use Cases

Three use cases apply regardless of industry or title — useful for almost any professional who manages projects, communicates with stakeholders, or works with customer feedback.

  • Generate project status reports — keep stakeholders informed with clear, consistent updates
  • Analyze patterns in user feedback — extract insights from customer comments and survey responses
  • Package your brand guidelines in a skill — create a reusable Claude skill that applies your brand standards automatically

Tip

Packaging brand guidelines as a Claude skill means you define your standards once and apply them across every conversation, without re-pasting style rules each time you start a new task.

Use CaseInput You ProvideWhat Claude Produces
Project status reportsPipeline data, recent milestones, blockersStakeholder-ready written update
User feedback analysisCustomer comments, survey responsesIdentified patterns and actionable insights
Brand guidelines skillExisting brand documentation and rulesReusable skill for consistent on-brand output

Key Takeaway

A small set of general-purpose tasks — reporting, analysis, and reusable skills — can improve your work immediately, regardless of your specific role or industry.

4602. Sales, Marketing, and Finance

Sales

Sales professionals can use Claude to accelerate deal preparation, build competitive intelligence resources, and produce clear pipeline reports.

  • Build a battle card library — create competitive intelligence resources that help your team win deals
  • Prepare for sales deals — research prospects and organize talking points before important meetings
  • Create sales reports — turn pipeline data into clear, actionable reports

Key Term

A quick-reference document that helps salespeople counter competitor objections and highlight their own product's strengths during a deal. Claude can help build and maintain a library of these across multiple competitors.

Marketing

Marketers can use Claude to analyze performance data and repurpose content efficiently across different channels and audiences.

Two high-impact starting points: analyzing campaign performance to extract strategy-informing insights from metrics, and adapting content across platforms to repurpose existing material for different channels without starting from scratch.

Note

Rather than rewriting content from scratch for each channel, Claude can adapt tone, length, and format while preserving the core message — saving significant time when the same content must reach multiple audiences.

Finance

Finance professionals can use Claude to build analytical models, draft complex documents, and make sense of spreadsheets they did not create.

  • Build financial models — create and refine financial projections with Claude's assistance
  • Draft investment memos — structure and write investment analyses more efficiently
  • Understand and extend an inherited spreadsheet — decode complex logic and safely add new functionality

Tip

When you receive a complex spreadsheet without documentation, Claude can help reverse-engineer the logic, identify cell dependencies, and extend it with new formulas — without breaking existing calculations.

Key Takeaway

Across sales, marketing, and finance, Claude's consistent value is compressing the gap between raw data and polished, decision-ready output — whether that is a battle card, a repurposed campaign asset, or a financial projection.

HR

HR teams can use Claude to create onboarding materials that are comprehensive and tailored to specific roles, rather than relying on generic company-wide templates.

Tip

A new hire onboarding guide built with Claude can be customized by department, seniority level, or location — helping new employees become productive faster because the content reflects their actual responsibilities.

Creating role-specific guides at scale is time-consuming when done manually. Claude can draft and adapt these materials quickly, letting HR professionals focus on reviewing and refining rather than writing from scratch.

Legal

Legal professionals work with large volumes of documents and tight timelines. Claude can organize case materials and surface patterns that would otherwise require hours of manual review.

Note

Tracking discovery timelines and analyzing patterns means organizing case timelines and identifying key connections across large sets of legal documents — a task where Claude can significantly reduce manual effort.

By handling organizational and pattern-finding work, Claude allows legal teams to direct their expertise toward judgment and strategy rather than document sorting.

Research

Researchers can use Claude to plan systematic literature reviews and to verify statistical calculations against raw data before publishing or presenting findings.

Tip

Having Claude verify statistical calculations against raw data adds an independent check before results are shared. This can surface errors in formulas or data interpretation that are easy to miss when you are close to your own work.

These role-specific examples are a starting point. The Use Case Gallery contains the full collection with step-by-step instructions, organized to help you find scenarios that fit your specific work context.

Key Takeaway

Whether structuring onboarding, managing legal discovery, or verifying research data, Claude handles organizational and analytical groundwork so professionals can concentrate on the higher-order judgment that requires their specific expertise.

4801. Claude Beyond Claude.ai

Claude.ai is one interface to Claude, but the underlying intelligence is available in several specialized tools built for the environments where you already work. The goal of each tool is the same: instead of moving your work into Claude, Claude moves into your work.

  • Claude Code — software development in your terminal or IDE
  • Claude in Slack — team collaboration within your workspace
  • Claude for Excel — spreadsheet analysis via an in-app sidebar
  • Claude for PowerPoint — slide editing via an in-app sidebar
  • Claude for Chrome — browser assistance via a Chrome extension

Key Term

A tool where Claude can take actions autonomously — executing commands, modifying files, or interacting with interfaces — rather than generating text for you to copy manually.

ToolBest forWhere it runs
Claude.aiGeneral tasks, research, writing, analysis, file creationWeb, desktop, and mobile apps
Claude CodeSoftware development, codebase navigation, git workflowsTerminal, IDE, or browser
Claude CoworkComplex multi-step tasks: research briefs, document creation, data analysisDesktop (and mobile via Dispatch)
Claude / Claude Code in SlackTeam collaboration, meeting prep, quick answers in contextSlack workspace
Claude for ExcelSpreadsheet analysis, financial modeling, formula debuggingMicrosoft Excel sidebar
Claude for PowerPointSlide creation, presentation editing, formatting and designMicrosoft PowerPoint sidebar
Claude for ChromeWeb research, email management, browser automationChrome browser sidebar

Note

Pick the tool that matches where your work lives. If you are in a spreadsheet, use Claude for Excel. If you are writing code in a terminal, use Claude Code. The capability set is similar — the environment differs.

Claude Code is the most autonomous of these tools, capable of running terminal commands and managing entire development workflows. The sidebar tools (Excel, PowerPoint, Chrome) give Claude visibility into your current context and apply changes directly within the application.

Key Takeaway

Claude is not limited to claude.ai. Five specialized tools extend Claude into your terminal, Slack workspace, Excel, PowerPoint, and browser — each designed so you stay in your working environment while Claude operates within it.

4902. Claude Code

Key Term

An agentic coding tool that understands your codebase, executes commands, and handles entire development workflows through natural language. It runs in your terminal, IDE, or browser.

Claude Code integrates with your existing development environment. You do not switch to a separate interface — it works alongside your terminal and IDE so your current tools remain in place.

Core capabilities

  • Build features: describe what you need in plain English and Claude writes the code, runs tests, and creates commits
  • Debug: paste an error message and Claude analyzes your codebase to identify and fix the problem
  • Navigate unfamiliar codebases: ask questions about how different parts connect and work together
  • Automate repetitive tasks: fix lint errors, resolve merge conflicts, write release notes

Claude Code also works inside Slack. When a bug report or feature discussion appears in a channel, tagging @Claude can start a Claude Code session that uses the surrounding conversation as context.

Tip

Claude Code is the right choice when you prefer staying in your terminal and existing IDE rather than switching to a separate chat interface for coding tasks.

The full development loop — describing a feature, having Claude write and test it, then commit the result — happens without leaving your terminal.

Key Takeaway

Claude Code handles entire development workflows from natural language, from writing and testing to committing — without requiring you to leave your terminal or IDE.

5003. Claude in Slack

Claude integrates directly into Slack as a participant in channels and threads. It can also bring Slack content — conversations and shared documents — into your Claude sessions.

  • Draft responses to messages, summarize long threads, or clarify complex discussions without leaving Slack
  • Prepare for meetings by pulling together relevant conversations and shared documents from your workspace
  • Help new team members understand ongoing projects by reviewing channel history
  • Answer questions about industry trends, technical concepts, or company information mid-conversation
  • Hand off coding tasks from a bug report: tag @Claude and it starts a Claude Code session using surrounding context

Note

A new team member can ask Claude to explain what a channel is working on. Claude reads the channel history and provides a summary of ongoing projects, decisions, and open questions.

The Slack and Claude Code bridge is especially useful for development teams. Instead of copying a bug report into a separate tool, you tag Claude in the thread and it can open a coding session with the issue already in context.

Tip

Use Claude in Slack when the information you need or the output you are producing is tightly tied to ongoing team conversations — so context flows directly into Claude's responses.

Claude in Slack reduces tool switching. You stay in the workspace your team already uses, and Claude participates in conversations where the work is already happening.

Key Takeaway

Claude in Slack keeps team collaboration and AI assistance in the same place, so conversation context feeds Claude's responses without manual copying or switching to a separate tool.

5104. Claude for Excel

Key Term

A Microsoft Excel sidebar that lets you analyze, understand, and modify spreadsheets through conversation. Claude reads the workbook's structure and formulas, then takes direct action within the workbook.

When you open Claude for Excel, it explores the full workbook — not just listing tabs but explaining the data flow. For a multi-tab headcount planning model, it will trace how an Assumptions tab feeds into Headcount, which feeds into Compensation, rolling up into a Summary tab.

Exploring and debugging workbooks

When you inherit a workbook you did not build, Claude can describe it the way its original author would. During an initial walkthrough, it also proactively flags errors — in a demo, it identified a cascading #REF error in cell E15 of the Headcount tab before being asked to look for issues.

Tip

When fixing a broken reference, Claude explains the cause and proposes a solution. You can accept its recommendation, specify a value, or tell it to use its best judgment — it then applies the fix and the correction cascades through all dependent cells automatically.

  • Identify #REF!, #VALUE!, and circular reference errors and trace them to their source
  • Explain what the broken formula was trying to calculate
  • Apply the fix directly — dependent cells update automatically through existing formula relationships

Scenarios, visualizations, and new formulas

For scenario modeling, you describe the change in plain language. Asking Claude to update attrition from 10% to 15% causes it to make the edit and then walk you through what changed across all dependent tabs — headcount projections, compensation costs, and summary figures — because the existing formula relationships do the recalculation.

Note

When Claude adds a new column — such as a fully loaded cost calculation — it writes formulas that reference the relevant tabs rather than copying static numbers. The result is maintainable and stays connected to the rest of the model.

  • Create pivot tables from headcount data by describing the breakdown you need
  • Generate bar charts or stacked bar charts without navigating Excel menus
  • Add calculated columns that reference other sheets, preserving all formula dependencies

Key Takeaway

Claude for Excel operates inside your formula structure. Every change — error fixes, scenario updates, new columns, visualizations — produces formula-based results that stay maintainable, not static overrides.

5205. Claude for PowerPoint

Claude for PowerPoint runs as a sidebar in Microsoft PowerPoint. It drafts, edits, and restructures presentations through conversation while preserving your existing template and brand styling.

Tip

Give Claude an outline, document, or set of notes and it produces a first-draft slide deck — slide by slide — without you building each one by hand.

  • Rewrite or tighten slide copy: shorten bullets, add speaker notes, or adjust tone for a specific audience
  • Restructure an existing deck: reorder sections, split dense slides, or merge overlapping ones
  • Apply consistent formatting across all slides — titles, bullet styles, and layouts — without editing each slide manually
  • Get layout or chart-type suggestions for individual slides based on the point being made

Note

Claude for PowerPoint applies changes within your existing template. It does not override your brand styles or formatting choices when editing content.

All edits appear directly in your open presentation. There is no export or import step — Claude's changes are visible immediately in the deck you are working on.

The tool is especially useful for the later stages of deck creation: tightening copy, making formatting consistent, and adjusting structure once a first draft already exists.

Tip

Use Claude for PowerPoint when you need to move from notes or an outline to a structured deck, or when an existing draft needs copy editing and formatting consistency applied across all slides at once.

Key Takeaway

Claude for PowerPoint converts source material into slide decks and applies structural or formatting changes at scale — inside your presentation, preserving your template throughout.

5306. Claude for Chrome

Key Term

A Chrome browser extension that adds Claude as a sidebar. It can observe what you are viewing and take actions directly within the browser window, maintaining context as you move between tabs.

Unlike opening Claude.ai in a separate tab, Claude for Chrome retains context as you move between tabs and tasks. This makes it useful for workflows that span multiple web tools — CRMs, dashboards, and internal applications that do not have their own Claude integrations.

  • Summarize articles, research papers, or web pages while browsing
  • Draft email responses or help manage your inbox
  • Automate repetitive form filling
  • Test website features or navigate multi-step workflows without manually clicking through each step

Warning

Claude for Chrome is currently in research preview. Anthropic recommends using it for low-risk tasks on trusted websites. The extension asks for permission before taking high-risk actions such as purchasing or sharing personal data. Financial services and adult content sites are blocked by default.

The cross-tab context retention is what distinguishes Claude for Chrome from a standalone chat window. Claude can pull information from multiple open tabs and apply it to what you are currently working on.

Tip

Claude for Chrome is particularly useful for workflows involving internal tools, CRMs, or dashboards that lack native Claude integrations — because it can observe and act in any website you open in Chrome.

As a research preview, the extension's behavior and available actions may change over time. Using it on well-known, trusted websites minimizes the risk of unexpected actions.

Key Takeaway

Claude for Chrome brings AI assistance into any website, maintaining context across tabs — most useful for research workflows, repetitive browser tasks, and tools that do not have a native Claude integration.

5401. What You've Covered in Claude 101

Claude 101 has taken you from first conversation to a working understanding of Claude's full capability set—prompting, organizing work, extending Claude to external tools, and applying it across professional roles.

Getting Started and Getting Better Results

  • Claude is an AI assistant built to be helpful, harmless, and honest—a thinking partner for complex work, not just a chatbot.
  • You can access Claude through web, desktop, and mobile apps, with conversations syncing across devices.
  • Effective prompts set the stage (context), define the task (action), and specify rules (format and style).
  • Treat first responses as starting points and refine through conversation—iteration is the core skill.

Key Term

A framework of four competencies for effective AI collaboration: Delegation (deciding what to hand off), Description (providing clear context), Discernment (evaluating outputs critically), and Diligence (verifying and refining results).

Common challenges—generic responses, wrong tone, missing context—are correctable by adding specificity. The four AI Fluency competencies give you a mental model for diagnosing and fixing these issues.

Organizing Work and Expanding Claude's Reach

  • Projects create dedicated workspaces with persistent knowledge, custom instructions, and team collaboration.
  • Artifacts are standalone outputs—documents, code, diagrams, interactive tools—created alongside your conversation.
  • Skills are instruction packages that teach Claude specialized workflows, including built-in and custom options.

Connectors link Claude to external tools—Google Workspace, Slack, Notion, and more—so it works with your actual organizational data rather than generic knowledge. Enterprise Search provides a dedicated project for searching across your organization's knowledge sources, while Research mode conducts systematic, multi-source investigations automatically.

  • Claude applies across professional roles: sales, marketing, finance, HR, legal, and research.
  • Beyond claude.ai, Claude is available through Claude Code, Slack, Excel, and Chrome.
  • Research mode handles multi-source investigations that would take hours to complete manually.

Key Takeaway

You now have a complete map of Claude's capabilities—from basic prompting to enterprise-scale workflows. Each layer builds on the previous: better prompts lead to better outputs, organized projects multiply that quality over time, and connectors extend it to the tools you already use.

5502. Resources for Continued Growth

Anthropic provides a set of free courses and documentation that extend what you've built here. These resources cover AI concepts, product-specific workflows, and reference material for daily use.

Learning and Reference Resources

  • AI Fluency courses — free courses on effective AI collaboration.
  • AI Capabilities and Limitations — free introductory course on what AI can and can't do.
  • Use Case Gallery — step-by-step guides and prompts for specific workflows.
  • Anthropic Help Center — detailed documentation and troubleshooting.
  • Prompting documentation — comprehensive guide to getting the best results from Claude.

Tip

The Use Case Gallery is the fastest path to ready-made workflows for your specific role. Browse by category, pick a template, and adapt the prompt to your context.

Product-Specific Courses

  • Claude Code in Action — free course on using Claude for software development workflows.
  • Introduction to Claude Cowork — free course on Claude's desktop companion for multi-step work.
  • Connector Directory — browse and connect your tools to Claude.

Each product course goes deeper into a single surface—useful once you know which part of Claude's ecosystem fits your daily work best.

Key Takeaway

The available learning resources are free and practical. Start with the Use Case Gallery for immediate workflow ideas, then move to product-specific courses when you want to go deeper on Claude Code or Cowork.

5603. Putting Knowledge Into Practice

The skills from this course sharpen with use. The gap between understanding Claude and using it well closes through repeated, real-work application—not through more reading.

Tip

Pick one recurring task from your work this week and try it with Claude. Drafting an email, summarizing meeting notes, or analyzing a spreadsheet are good starting points. See what happens, then iterate.

Start simple and build from there. You don't need Projects, Connectors, or Research mode on day one. A well-crafted prompt on a single real task will already reveal what Claude can do.

  1. Choose a single recurring task from your actual workload.
  2. Write a prompt using the context-action-format structure from the course.
  3. Review Claude's response critically—use your domain expertise to evaluate it.
  4. Refine through conversation until the output meets your standard.
  5. Note what worked and apply that pattern to future tasks.

Claude is designed to be a collaborator, not a replacement. The best results come when you bring your expertise, context, and judgment to the conversation—Claude handles the generative heavy lifting; you supply the standards.

Note

Anthropic wants to hear how this course has helped and what could be improved. A feedback link is available on the course completion page.

Key Takeaway

The foundation is in place. Real proficiency comes from doing—pick one task, try it today, and build the habit of reaching for Claude when complex work arrives. Your expertise and Claude's generative capability are strongest in combination.

5701 Certificate of Completion

The final step in Claude 101 is a completion quiz. Passing it earns your Claude 101 Certificate of Completion.

Note

The Claude 101 Certificate of Completion Quiz contains 13 questions. Click Start on the certificate page to begin.

The quiz draws on material from all four main sections of the course.

  1. Meet Claude — what Claude is, your first conversation, getting better results, and the desktop app
  2. Organizing your work and knowledge — projects, artifacts, and skills
  3. Expanding Claude's reach — tool connections, enterprise search, and research mode
  4. Putting it all together — use-cases by role and other ways to work with Claude

Tip

Review any lessons you feel uncertain about before starting the quiz. The course navigation remains accessible from the quiz page.

After completing the quiz, your certificate reflects mastery of the full Claude 101 curriculum, from basic conversations to advanced research and enterprise features.

Key Takeaway

Completing the 13-question Claude 101 Certificate of Completion Quiz is the final requirement to earn your course certificate. It covers every section of the course.

Course outline