Stop Prompting Claude. Start Staffing It.

Here is what almost everyone does with Claude. They open a chat. They paste a task. They get an answer. They close the tab. Next time they start from zero and re-explain the whole situation again, what the company does, who the customer is, what good output even looks like. That isn't an assistant. That's one freelancer with amnesia. Useful, occasionally impressive, and permanently small.

There is a completely different way to run this, and the gap between the two has nothing to do with the model. Anthropic quietly open-sourced a repo that turns Claude into a set of specialized office roles, a sales rep, a marketer, a financial analyst, a legal reviewer, a data analyst, each one pre-loaded with the workflows, the domain knowledge, and the tool connections that role actually needs. You stop prompting from scratch. You start hiring a department.

What the repo actually is

It's called knowledge-work-plugins, and it's a free, open-source marketplace of role-based plugins for Claude. Each plugin turns Claude into one narrow specialist, and inside every one there are three things doing the work.

• Skills, the domain knowledge and best practices for that role. Claude pulls them automatically when they're relevant. You don't invoke them, you don't even think about them, they're just the part where the worker already knows how the job is done.
• Commands, ready-made workflows you trigger with a slash, like /sales:call-prep or /data:write-query. These are the repeatable jobs that role does every day, packaged so you don't rebuild them each time.
• Connections, the tools that role plugs into. The sales plugin reaches for your CRM. The finance plugin reaches for your data warehouse. The marketing plugin reaches for your analytics and your design tool.

The detail that should make you sit up: this is the same foundation Anthropic built Claude for Legal and Claude for Financial Services on top of. You're getting the base layer those paid products are made from, in the open, for free. The expensive version is the same skills with a support contract wrapped around them.

The roles you can hire

The repo ships with a full org chart, and each role is one command to install. You don't take all of them. You build the team your work actually needs.

• Productivity, tasks, calendars, daily routine, personal context. Plugs into Slack, Notion, Asana, Linear, Jira, ClickUp, Microsoft 365.
• Sales, account research, call prep, pipeline, cold outreach, competitive analysis. Plugs into HubSpot, Close, Clay, ZoomInfo, Fireflies.
• Marketing, content, campaigns, brand voice, competitor sweeps, channel reporting, SEO audits. Plugs into Canva, Figma, HubSpot, Klaviyo, Ahrefs, SimilarWeb.
• Customer support, ticket triage, reply templates, escalations, turning solved tickets into help-center articles. Plugs into Intercom, HubSpot, Guru.
• Product management, specs, roadmaps, user research synthesis, stakeholder updates. Plugs into Linear, Figma, Amplitude, Pendo.
• Finance, journal entries, reconciliations, statements, variance analysis, month-end close, audit support. Plugs into Snowflake, Databricks, BigQuery.
• Legal, contract review, NDA triage, risk assessment, templated responses. Plugs into Box, Egnyte, Microsoft 365.
• Data, queries, SQL, stats, dashboards, sanity-checking results before you publish them. Plugs into Snowflake, Databricks, BigQuery, Hex.
• Enterprise search, one search across your email, chat, docs, and internal wikis.

Step 1: Get the desktop app

These plugins are built for Cowork, Anthropic's agentic desktop app, though they also run in Claude Code. Download Claude Desktop from claude.com/download and open the Cowork tab. This is the moment Claude stops being a chat window and starts touching real files, real tools, and real workflows. Everything below assumes you're working in there.

Step 2: Add the marketplace

Cowork has a terminal. Point Claude at the full catalog of roles with one command, which you only ever run once:

claude plugin marketplace add anthropics/knowledge-work-plugins

Step 3: Hire your first worker

Install the role you need most. Say it's a sales rep:

claude plugin install sales@knowledge-work-plugins

Swap sales for any role, marketing, finance, legal, data, product-management, customer-support, productivity. The plugin activates the moment it's installed. Start with one. Get a feel for how it changes the work before you build out the whole floor.

Step 4: Put it to work standalone

Here's the part people miss: every plugin works on day one without connecting a single outside tool. You just hand it the raw material. Trigger a workflow with a slash command, /sales:call-prep takes a company name and hands back a full pre-call brief, /data:write-query takes a plain-English question and hands back the SQL, /marketing:seo-audit takes a page and hands back keyword gaps and fixes. Paste your notes, upload a CSV, describe the situation. The skills behind the plugin already know how that role does the job, so you skip the entire part where you explain what good looks like. That's the part that used to eat the whole session.

Step 5: Connect its tools

This is where the worker goes from competent to genuinely useful. Each plugin has tool connections built in. Connect the sales plugin to your CRM and it stops asking you to paste pipeline data and starts pulling it. Connect finance to your data warehouse and it reconciles against the real numbers, not the ones you typed in. Connect marketing to your analytics and the reports build themselves. In Cowork, open Connectors and authorize the tools that role uses. The standalone version is the intern who needs everything handed to them; the connected version is the senior hire who already has the logins.

Step 6: Build the rest of the team

Now repeat Step 3 for every role your work actually requires. And here's the part that turns a clever trick into an operating model: once they're installed, they work together in the same session. Your data worker pulls the numbers, your finance worker reconciles them, your marketing worker turns the result into a report, in one place, in one pass. One operator, a full cross-functional team, no payroll, no scheduling, no handoff lost in a Slack thread. This is the same instinct I keep coming back to, designing each agent like a narrow employee with a clear job, rather than expecting one genius generalist to do everything.

Step 7: Make them yours

The default plugins are a strong starting point and a generic one. The real edge is customizing them for how you actually work. The repo ships a meta-tool, the cowork-plugin-management plugin, built for exactly this: tell it your tools, your terminology, your process, and it reshapes a plugin to fit. And because plugins are just markdown files, you can edit them directly, fork the repo, and keep your own private versions. This is the same move as writing the context once so the system prompts itself, the difference between Claude that knows how a generic sales rep works and Claude that knows how your company sells.

What you have after seven steps

Before this, Claude is a chatbot you ask questions, one at a time, starting over every session. After this, Claude is a building full of specialists. A sales rep who preps every call. A marketer who runs the campaign. A data analyst who writes the queries. A finance lead who closes the month. All pulling from your real tools, all working in one place, all running off a free open-source repo. Same subscription. Completely different operation.

I've written before that when building gets cheap the scarce skill moves to shaping the problem, and this is the same lesson wearing office clothes. The capability was sitting there the whole time. What separates the people getting leverage from the people still pasting tasks into a chat box isn't access to a better model, it's that one group did the setup and the other didn't. Most people will read all seven steps and install nothing. If that's not going to be you, the next move is simple, run the first command. And if you want help turning this into how your company actually operates rather than a weekend experiment, that's the work I do. Let's talk →