We build Cowork plugins tailored to your specific workflows. Skills, commands, connectors, agents, and hooks designed for how your team actually works.
One-time setup. Ongoing value without ongoing consulting fees.
Anthropic ships 11 official plugins covering broad roles like Sales, Marketing, and Productivity. They're solid starting points. But your business doesn't run on generic processes.
A real estate brokerage needs a plugin that follows their specific CMA template, writes in their brand voice, and pulls comps from their MLS system. A law firm needs contract review skills trained on their clause library, not generic legal templates. An accounting firm needs reconciliation workflows that match their chart of accounts, not a one-size-fits-all ledger format.
Produces output that's close but never quite right. Your team spends 20 minutes editing every deliverable to match your standards, templates, and terminology. The time savings erode fast.
Produces work that matches how your team already operates. Your CMA template. Your clause library. Your chart of accounts. Your brand voice. Output that needs minimal revision because it was built around your process from the start.
Every plugin is a folder of markdown and JSON files. No compiled code, no infrastructure to maintain, no build steps. Here's what goes inside.
Domain expertise that Claude draws on automatically when relevant. Each skill is a SKILL.md file with YAML frontmatter defining when it should activate. Your CMA formatting rules, your contract review checklist, your brand voice guidelines. Claude applies them without being asked. Full skills guide.
Explicit actions your team triggers with a slash. Type /sales:call-prep and Claude pulls the prospect's data from your CRM, checks recent email threads, and generates a briefing doc. Type /finance:reconciliation and it walks through your monthly close checklist step by step.
MCP server configurations in a single .mcp.json file. These wire Claude to your external tools: HubSpot, Salesforce, QuickBooks, Google Drive, Slack, Jira, and dozens more. Each connection uses OAuth with scoped permissions. Full connectors guide.
Specialized sub-agents for specific tasks. Claude invokes them automatically when a task matches their scope. For example, a drafting agent that writes in your firm's style, or a review agent that checks output against your quality standards before delivering it.
Event handlers that fire before or after specific actions. JSON configuration files with matchers and actions. Use PreToolUse hooks to add guardrails before Claude sends an email. Use PostToolUse hooks to log every CRM update. Use SessionStart hooks to load context at the beginning of every conversation.
Every industry has workflows that don't fit neatly into a generic template. Here's what custom plugins look like in practice.
Building a plugin that actually fits your workflows takes back-and-forth with your team. Here's how we do it.
We start with a 15-minute call to understand your workflows, the tools you use daily, and where you're losing time. This tells us whether a custom plugin is the right fit or if configuration of existing plugins would solve the problem.
We write every component: skill files with YAML frontmatter, command definitions, MCP server configs, agent specs, and hook handlers. Most plugins take 1-2 weeks to build. Everything is file-based, so you can read and understand every piece of it.
Your team runs the plugin against real work and provides feedback. We tune the skills, adjust command prompts, and refine output quality until the deliverables meet your standards.
We install the plugin, wire up all connector OAuth flows, configure permissions, and verify everything works end to end. For enterprise teams, we add the plugin to your organization marketplace with the right installation preferences.
We run a training session covering every command, when skills activate, and how to customize the plugin yourself. Your team leaves the session able to use every feature independently.
Cowork is still evolving. Anthropic ships platform updates regularly, and those updates sometimes change how plugins work. We keep your plugin compatible so your team never wakes up to a broken workflow.
You could. The plugin system is open and file-based. But there are reasons most teams hire us instead.
Configuring MCP servers, scoping permissions, and handling OAuth flows across multiple platforms takes specific knowledge. We've done it dozens of times across HubSpot, Salesforce, QuickBooks, and more.
The difference between mediocre and excellent plugin output comes down to how well the skills and global instructions are written. We've iterated on enough plugins to know what works and what doesn't.
Learning the plugin system from scratch takes weeks of experimentation. Your team has work to do. We handle the setup so you can go straight to the value.
.mcp.json file can define connections to as many MCP servers as you need. A single sales plugin could connect to HubSpot for CRM data, Gmail for email drafting, and Google Sheets for pipeline tracking. Each connection uses scoped OAuth permissions. Read the connectors guide.
Book a free 15-minute call. We'll walk through your workflows, identify which tasks fit the plugin model, and outline what a custom build would look like for your team.
Book a Free 15-Minute CallNo commitment. No sales pitch. Just a straight look at what we can build for you.