Claude Cowork Skills and Connectors.
Cowork connects Claude to the tools your team actually uses. Here is the full breakdown of every connector, how the protocol works, and how to chain them into workflows that retire entire swivel-chair processes.
Claude is smart. That is table stakes.
What most people have not realized yet is that Claude can now reach out and touch your tools. It can read your Slack channels, create Linear issues, inspect Figma designs, query your database, and deploy your code. All from a single desktop interface.
This is not a vision of the future. It is shipping now in Claude Cowork, and the connector ecosystem is already deep enough to replace entire swivel-chair workflows.
A sandboxed VM, plus hands on your tools.
Cowork is a feature of the Claude desktop app that gives Claude a lightweight Linux VM on your computer. Inside that sandbox, Claude can execute code, create files, and, critically, connect to external services through connectors.
Think of it as giving Claude hands. Instead of just thinking and talking, Claude can now do things: send a Slack message, create a Linear ticket, deploy a Vercel project, query a Supabase database. Each connector gives Claude a new set of capabilities, and you can chain them together into multi-step workflows.
The key insight: Cowork is not just Claude with plugins. It is Claude with agency, autonomously chaining tools to accomplish complex work across your entire stack.
Every connector speaks the Model Context Protocol.
MCP is the open standard Anthropic created for connecting AI models to external tools and data sources. It defines a standard way for Claude to discover what tools are available, understand what they do, and call them with the right parameters.
Each connector is an MCP server that exposes a set of tools. The protocol handles authentication, parameter validation, and response formatting. You connect the service, and Claude gets a new set of capabilities. No code required on your end.
- 01You ask Claude to do something, for example post a summary in #engineering.
- 02Claude identifies which connector and tool to use, here Slack with send_message.
- 03Claude constructs the API call with the right parameters.
- 04The MCP server authenticates and executes the call.
- 05Claude reads the result and continues the task.
Eight connectors, one operating surface.
Here is a detailed breakdown of every major connector available in Cowork today, what it does, and the capabilities it exposes.
Slack
Full read and write access to your workspace. Claude can search messages, read channels and threads, send and schedule messages, create and update canvases, and look up user profiles.
Linear
Deep project management integration. Claude can create, read, and update issues, manage milestones, work with cycles, search documentation, handle labels, and manage projects, essentially acting as a project manager that never sleeps.
Figma
Bridge between design and development. Claude can inspect design files, extract metadata and screenshots, understand component structures, read design tokens and variables, and even generate code-to-component mappings.
Vercel
Full deployment lifecycle management. Claude can deploy projects, monitor deployments, read build and runtime logs, manage projects, check domain availability, and interact with toolbar threads for feedback.
Supabase
Direct database and backend control. Claude can execute SQL, manage migrations, create and merge branches, deploy edge functions, list tables and extensions, and generate TypeScript types from your schema.
HubSpot
CRM access for sales and marketing workflows. Claude can search and retrieve CRM objects, look up properties, search owners, and pull user details, turning conversational queries into CRM operations.
Google Drive
File access across your Google Drive. Claude can search for files and fetch their contents, making it easy to reference documents, pull data from spreadsheets, and work with your team's shared knowledge base.
Fireflies
Meeting intelligence at your fingertips. Claude can access transcripts and summaries, search across meetings, manage meeting access, and pull contact information. Perfect for post-meeting action items.
Bonus: Cowork also ships browser automation and a Webflow connector that handles site management, CMS, page editing, components, and styles. The ecosystem is growing fast.
Skills are playbooks the model already knows.
Beyond connectors, Cowork supports custom skills, specialized instruction sets that tell Claude how to handle specific types of tasks. Skills are like playbooks: they define step-by-step processes Claude should follow.
Cowork ships with several built-in skills for document creation, and you can create your own. Skills can be triggered manually via slash commands or automatically when Claude detects a matching task.
Creates professionally formatted Word documents.
Triggers on: Word doc, .docx, report, memo
Builds Excel files with formulas, formatting, and charts.
Triggers on: Spreadsheet, Excel, .xlsx, data table
Generates slide decks with layouts and speaker notes.
Triggers on: Presentation, deck, slides, .pptx
Reads, creates, merges, splits, and fills PDF documents.
Triggers on: PDF, .pdf, form, extract, merge
Creates tasks that run on demand or on a schedule.
Triggers on: Schedule, recurring, automate on interval
Plugins are complete toolkits, not just wrappers.
Plugins are installable bundles that package together MCP connectors, skills, and tools into a single unit. They are how the Cowork ecosystem scales. Instead of configuring each connector individually, you install a plugin that bundles everything you need for a specific workflow.
You can create custom plugins using the built-in plugin creator skill, customize existing plugins for your organization, or browse the plugin marketplace for pre-built solutions.
Connectors are individual tools. Skills are playbooks. Plugins are complete toolkits that bundle both together for specific use cases.
Not hypothetical. You can build them today.
These are workflows you can compose right now by combining connectors. Each one retires a recurring swivel-chair task that someone on your team is doing by hand this week.
Sprint standup autopilot
“Pull yesterday's Linear activity for the team, summarize what shipped, what is in progress, and what is blocked, then post it to #engineering in Slack.”
Design-to-ticket pipeline
“Look at the new Figma designs for the settings page, break them into implementation tasks with acceptance criteria, and create Linear issues for each one.”
Meeting action-item tracker
“Pull the transcript from today's product sync, extract every action item with owners and deadlines, create Linear issues for engineering tasks, and DM each owner in Slack with their assignments.”
Deploy monitor and alert
“Check the latest Vercel deployment. If the build failed, pull the logs, identify the error, create a Linear bug ticket with the stack trace, and alert the team in Slack.”
CRM-to-report pipeline
“Pull all deals closed this quarter from HubSpot, cross-reference with the revenue targets in Google Drive, generate a quarterly report as a polished PPTX, and share the summary in #sales on Slack.”
Connect two tools. Then the others get obvious.
Setting up Cowork connectors is straightforward. Open the Claude desktop app, navigate to Cowork mode, and you will see available connectors in the settings. Each one walks you through OAuth authentication. Click connect, authorize, and you are live.
Start with the tools your team uses most. If you live in Slack and Linear, connect those first. Once you see Claude pulling real data from your actual workspace and taking real actions, the possibilities become obvious.
The teams getting the most value from Cowork are not the ones with the most connectors. They are the ones who have identified their highest-friction workflows and automated them. Find the workflow where your team spends the most time copying information between tools, and start there.
Cowork runs in a sandboxed environment and always asks for confirmation before taking actions like sending messages or creating issues. Claude proposes, you approve.
The future of work is not AI replacing tools. It is AI connecting them. Cowork turns Claude from a chatbot into an operating system for your entire workflow.
YNDR · AI Operations Company
If your team should be shipping Cowork workflows,
not just reading about them.
YNDR helps teams design and implement Claude-powered workflows, from Cowork connector setup to custom skills and full agentic pipelines. Same operator advises and builds.