Blog · Working with AI

Claude Projects vs Skills vs Connectors: Which to Use When

Callstand Team·Updated November 2, 2026·10 min read
Short answer

Use a project when one body of work needs the same files and instructions in every chat. Use a skill when you repeat a procedure, like a report format or a review checklist, and want Claude to apply it anywhere. Use a connector when Claude needs to read from or act in another app, or call an outside service. Most real setups use all three: the project holds the context, the skill holds the steps, and connectors reach the tools and data.

The three features look similar from the sidebar, and Anthropic has shipped them a year or more apart, so it's easy to pick the wrong one. Projects arrived in June 2024 (Anthropic), skills in October 2025 (Anthropic), and connectors grew from a short list into a large directory. This guide sorts out what each one does, when to reach for it, and how they fit together, using Anthropic's own help pages as the reference.

What's inside
  1. Projects vs Skills vs Connectors at a Glance
  2. What Claude Projects Do
  3. What Claude Skills Do
  4. What Claude Connectors Do
  5. Where to Find the Claude Connectors List
  6. Which to Use When: Decision Table
  7. Claude Projects vs Skills
  8. How They Work Together
  9. Connectors That Carry Expertise
  10. FAQ

Projects vs Skills vs Connectors at a Glance

ProjectsSkillsConnectors
What it holds Files, chat history and instructions for one body of work Instructions, scripts and resources for a specific task A link to an outside app or service
When it loads Always, inside that project Only when the task matches When Claude decides a tool is needed, or on demand
Where it works Chats inside the project Across Claude and Claude Code, plus the API in beta Claude web, Desktop, mobile, Claude Code, Cowork and the API
Best for A client, product or campaign with lots of reference material A repeatable format or method Live data and actions in other tools
Plans All plans; Free capped at five projects All plans; needs code execution All plans; Free capped at one custom connector
Built from Uploads and a text box A folder with a SKILL.md file A remote MCP server

Sources: What are projects, What are skills, Use connectors and the connectors directory docs, all checked November 2, 2026.

What Claude Projects Do

Anthropic describes projects as "self-contained workspaces" with their own chat histories and knowledge bases (Claude Help Center). You upload documents, add project instructions, and every chat you start inside the project sees that material.

A few details worth knowing:

The limit of a project is its boundary. The context is there because you're in the project. Open a new chat outside it and Claude doesn't know any of it.

What Claude Skills Do

Skills are "folders of instructions, scripts, and resources that Claude loads dynamically to improve performance on specialized tasks" (Claude Help Center). The key word is dynamically. Claude reads a short description of each skill, and only loads the full instructions when your request matches. Anthropic calls this progressive disclosure.

There are four kinds you'll run into:

Skills are available on Free, Pro, Max, Ultra, Team and Enterprise plans, and they need code execution switched on under Settings > Capabilities (Use skills in Claude). You don't need to code to write one. A skill is a SKILL.md file with a name and description at the top and plain instructions below (How to create custom skills). On Mac, Cowork can also record a skill while you walk through a task. Anthropic's own advice is that the best skills solve one specific, repeatable task.

Skills also follow an open standard published at agentskills.io, so the same folder can work in other tools that adopt it. The explainer on agent skills goes deeper, and the list of best Claude skills shows popular ones.

What Claude Connectors Do

"Connectors let Claude access your apps and services, retrieve your data, and take actions within connected services" (Claude Help Center). Think searching Google Drive, reading Slack threads or updating issues in Linear. Claude acts with your permissions, so it only sees what your account can see.

Under the hood, connectors are built on the Model Context Protocol (MCP). There are two kinds:

Connectors have grown faster than either of the other two features. When Anthropic donated MCP to the Linux Foundation's new Agentic AI Foundation in December 2025, it said Claude had "a directory with over 75 connectors" (Anthropic). On November 2, 2026, Anthropic's connectors page showed 1,051.

Admins have real controls. Team and Enterprise owners decide which connectors are enabled and can set each action to always allow, needs approval or blocked. If you run many connectors, Anthropic suggests switching tool access from Auto to "On demand" once you pass 10 active ones (Claude Help Center). Building your own server is developer work, covered in the guide to creating an MCP server.

Where to Find the Claude Connectors List

There are three places to look:

  1. Inside Claude: open Customize > Connectors, or click "+" in a chat, then Connectors, then Manage connectors (Claude Help Center).
  2. On the web: claude.com/connectors lists connectors and plugins by category, including productivity, sales and marketing, data and analytics, developer tools, commerce and finance.
  3. Your admin's allowlist: on Team and Enterprise, only connectors an owner has enabled will appear for you.

On November 2, 2026, the top of the web list included Google Drive, Gmail, Google Calendar, Canva, Microsoft 365, Notion, Figma, Slack, Atlassian, HubSpot, Asana and Linear, each marked as Anthropic verified (Claude connectors). Ranking in the directory is usage-based, and Anthropic notes that verification isn't a security audit (Claude docs). Treat a listing as a starting point, then check who runs the connector and what it asks permission to do.

Which to Use When: Decision Table

Match the problem you have to the feature that solves it.

If you need Claude to...UseWhy
Remember a client's brief, brand guide and past drafts in every chat about that clientProjectThe files and instructions load in every chat inside it
Write every weekly report in the same structure, no matter which chat you're inSkillIt loads only when the task matches, anywhere in Claude
Pull this week's numbers from a spreadsheet or CRMConnectorThe data lives in another app
Post a summary to Slack or create a task in AsanaConnectorIt's an action in another tool
Fill in an Excel, Word, PowerPoint or PDF file properlySkill (Anthropic's built-in)Anthropic ships skills for these formats
Share a working setup with your teamProject on Team/Enterprise, or an organization skillProjects share with view/edit rights; admins can provision skills
Apply a specialist's judgment you don't have in-houseConnector to an expert serviceThe knowledge lives outside your account and stays current
Keep one campaign's notes separate from everything elseProjectIts boundary is the point

A quick test helps when you're unsure. If the answer to "where does this live?" is "in these documents," start with a project. If it's "in how we do it," write a skill. If it's "in another app" or "with someone else," add a connector.

Claude Projects vs Skills

This is the pair people mix up most, because both can hold instructions. Anthropic draws the line clearly: "Projects provide static background knowledge that's always loaded when you start chats within them. Skills provide specialized procedures that activate dynamically when needed and work everywhere across Claude" (Claude Help Center).

In practice:

Custom instructions sit apart from both. Anthropic describes them as preferences that apply broadly to every conversation, while skills are task-specific and load only when relevant (Claude Help Center).

How They Work Together

Anthropic's own framing for skills and connectors is that they're complements: "MCP connections give Claude access to tools, while skills teach Claude how to use those tools effectively" (Claude Help Center).

Here's how the three can stack for a monthly marketing report:

  1. Project: "Acme account," with the brand guide, last quarter's reports and the client's goals.
  2. Skill: "Monthly report," with your section order, chart rules and the tone you use with this kind of client.
  3. Connectors: your analytics data source to pull numbers, Google Drive to save the draft, and Slack to send the summary.

You open a chat in the project and ask for this month's report. Claude has the account context, applies your report method, fetches the data and files the result. Each feature does one job, and none of them has to be stretched to cover the others.

Connectors That Carry Expertise

Most connectors carry data or actions. A newer kind carries know-how: the connector doesn't open a file or post a message, it answers with a method someone has already worked out. That fills a gap the other two features leave. A skill only knows what you wrote into it. A project only knows what you uploaded. Neither helps when the expertise belongs to someone else, or when your own playbook should be kept current in one place instead of copied into every account.

That's what Callstand does. A Callstand stores how you like work done, like your steps, examples and standards, and connects to Claude, ChatGPT and any MCP app. You can also connect a teammate's or an expert's Callstand next to yours. Claude can call it three ways: Plan it returns a prioritized plan, Make it returns the finished piece, and Check it tells you what to fix. Answers come back without revealing the underlying notes, and it says when it doesn't know.

Setup is one link in Claude or ChatGPT; in Claude Code, Cursor or Codex you add the link plus an API key. Pricing, as listed on the same page on November 2, 2026, is $0.50 per call on prepaid credits with no subscription, starting at $5, and calibration with 60 test cases and 10 side-by-side tests costs nothing (Callstand). One limit to know: Callstand's page notes that ChatGPT Plus and Pro are restricted to read-only custom apps.

If your team keeps pasting the same instructions into chats, the post on prompt debt explains why that adds up, and the Callstand guides have more setup walkthroughs.

Frequently asked questions

What is the difference between Claude projects and skills?

A project is a workspace with its own chats, files and instructions, and that context is always loaded inside it. A skill is a packaged procedure Claude loads only when a task calls for it, and it works across Claude, not just in one workspace. Anthropic puts it this way: projects provide "static background knowledge," skills provide "specialized procedures that activate dynamically" (Claude Help Center).

Are Claude connectors the same as MCP servers?

Mostly, yes. Connectors are how Claude uses MCP servers. Directory connectors are reviewed listings, and custom connectors are remote MCP servers you add by URL. Custom connectors work on every plan, with Free limited to one (Claude Help Center).

Where can I find a list of Claude connectors?

In the app, open Customize > Connectors or the "+" menu and choose Connectors. On the web, Anthropic's connectors page listed 1,051 connectors on November 2, 2026, with Google Drive, Gmail, Notion, Figma, Slack and HubSpot among the top results.

Do Claude skills work on the free plan?

Yes. Anthropic lists skills for Free, Pro, Max, Ultra, Team and Enterprise users, but they need code execution turned on under Settings > Capabilities (Claude Help Center; Use skills in Claude).

Can I use connectors inside a Claude project?

Yes, with one catch on Team and Enterprise: Anthropic says connectors are only available in private projects there (Claude Help Center). Connected tools then work alongside the project's files and instructions.

How many connectors should I turn on at once?

Only the ones the work needs. Anthropic suggests switching tool access to "On demand" if you have 10 or more connectors active, so conversations keep more room (Claude Help Center).

Is a connector safe to add?

It is as safe as the company behind it. Anthropic says to "only connect to servers from trusted organizations" for custom connectors (Claude Help Center), and notes that directory verification "isn't a security audit" (Claude docs).