knowledge-work-plugins Documentation

File: README.md Copy Chapter

Knowledge Work Plugins

Plugins that turn Claude into a specialist for your role, team, and company. Built for Claude Cowork, also compatible with Claude Code.

Why Plugins Copy Chapter

Cowork lets you set the goal and Claude delivers finished, professional work. Plugins let you go further: tell Claude how you like work done, which tools and data to pull from, how to handle critical workflows, and what slash commands to expose — so your team gets better and more consistent outcomes.

Each plugin bundles the skills, connectors, slash commands, and sub-agents for a specific job function. Out of the box, they give Claude a strong starting point for helping anyone in that role. The real power comes when you customize them for your company — your tools, your terminology, your processes — so Claude works like it was built for your team.

Plugin Marketplace Copy Chapter

We're open-sourcing 11 plugins built and inspired by our own work:

Install these directly from Cowork, browse the full collection here on GitHub, or build your own.

Getting Started Copy Chapter

Cowork Copy Section

Install plugins from claude.com/plugins.

Claude Code Copy Section

# Add the marketplace first
claude plugin marketplace add anthropics/knowledge-work-plugins

# Then install a specific plugin
claude plugin install sales@knowledge-work-plugins

Once installed, plugins activate automatically. Skills fire when relevant, and slash commands are available in your session (e.g., /sales:call-prep, /data:write-query).

How Plugins Work Copy Chapter

Every plugin follows the same structure:

plugin-name/
├── .claude-plugin/plugin.json   # Manifest
├── .mcp.json                    # Tool connections
├── commands/                    # Slash commands you invoke explicitly
└── skills/                      # Domain knowledge Claude draws on automatically

• Skills encode the domain expertise, best practices, and step-by-step workflows Claude needs to give you useful help. Claude draws on them automatically when relevant.
• Commands are explicit actions you trigger (e.g., /finance:reconciliation, /product-management:write-spec).
• Connectors wire Claude to the external tools your role depends on — CRMs, project trackers, data warehouses, design tools, and more — via MCP servers.

Every component is file-based — markdown and JSON, no code, no infrastructure, no build steps.

Making Them Yours Copy Chapter

These plugins are generic starting points. They become much more useful when you customize them for how your company actually works:

• Swap connectors — Edit .mcp.json to point at your specific tool stack.
• Add company context — Drop your terminology, org structure, and processes into skill files so Claude understands your world.
• Adjust workflows — Modify skill instructions to match how your team actually does things, not how a textbook says to.
• Build new plugins — Use the cowork-plugin-management plugin or follow the structure above to create plugins for roles and workflows we haven't covered yet.

As your team builds and shares plugins, Claude becomes a cross-functional expert. The context you define gets baked into every relevant interaction, so leaders and admins can spend less time enforcing processes and more time improving them.

Contributing Copy Chapter

Plugins are just markdown files. Fork the repo, make your changes, and submit a PR.

File: legal/README.md Copy Chapter

Legal Productivity Plugin

An AI-powered productivity plugin for in-house legal teams, primarily designed for Cowork, Anthropic's agentic desktop application — though it also works in Claude Code. Automates contract review, NDA triage, compliance workflows, legal briefings, and templated responses -- all configurable to your organization's specific playbook and risk tolerances.

Disclaimer: This plugin assists with legal workflows but does not provide legal advice. Always verify conclusions with qualified legal professionals. AI-generated analysis should be reviewed by licensed attorneys before being relied upon for legal decisions. The default playbook examples in this plugin reflect U.S. legal positions and jurisdictions (Delaware, New York, California). If you operate under different legal systems (EU, UK, Netherlands, Australia, etc.), you must customize the playbook in .claude/legal.local.md to reflect your jurisdiction's specific legal requirements, standard contract terms, and compliance obligations before relying on the plugin's analysis.

Target Personas Copy Chapter

• Commercial Counsel -- Contract negotiation, vendor management, deal support
• Product Counsel -- Product reviews, terms of service, privacy policies, IP matters
• Privacy / Compliance -- Data protection regulations, DPA reviews, data subject requests, regulatory monitoring
• Litigation Support -- Discovery holds, document review prep, case briefings

Installation Copy Chapter

claude plugins add knowledge-work-plugins/legal

Quick Start Copy Chapter

1. Install the plugin Copy Section

claude plugins add knowledge-work-plugins/legal

2. Configure your playbook Copy Section

Create a local settings file to define your organization's standard positions. This is where you encode your team's negotiation playbook, risk tolerances, and standard terms.

Create a legal.local.md file where Claude can find it:

• Cowork: Save it in any folder you've shared with Cowork (via the folder picker). The plugin finds it automatically.
• Claude Code: Save it in your project's .claude/ directory.

/* Detailed source-code truncated for AI context efficiency. */

3. Connect your tools Copy Section

The plugin works best when connected to your existing tools via MCP. Pre-configured servers include Slack, Box, Egnyte, Atlassian, and Microsoft 365. See CONNECTORS.md for the full list of supported categories and options.

Commands Copy Chapter

`/review-contract` -- Contract Review Against Playbook Copy Section

Review a contract against your organization's negotiation playbook. Flags deviations, generates redlines, and provides business impact analysis.

/review-contract

Accepts: file upload, URL, or pasted contract text. Will ask for context (your side, deadline, focus areas) and review clause-by-clause against your configured playbook.

`/triage-nda` -- NDA Pre-Screening Copy Section

Rapid triage of incoming NDAs against standard criteria. Categorizes as GREEN (standard approval), YELLOW (counsel review), or RED (significant issues).

/triage-nda

`/vendor-check` -- Vendor Agreement Status Copy Section

Check the status of existing agreements with a vendor across your connected systems.

/vendor-check [vendor name]

Reports on existing NDAs, MSAs, DPAs, expiration dates, and key terms.

`/brief` -- Legal Team Briefing Copy Section

Generate contextual briefings for your legal work.

/brief daily          # Morning brief of legal-relevant items
/brief topic [query]  # Research brief on a specific legal question
/brief incident       # Rapid brief on a developing situation

`/respond` -- Generate Templated Response Copy Section

Generate a response from your configured templates for common inquiry types.

/respond [inquiry-type]

Supported inquiry types include: data subject request, discovery hold, vendor question, NDA request, and custom categories you define.

Skills Copy Chapter

Example Workflows Copy Chapter

Contract Review Copy Section

1. Receive a vendor contract via email
2. Run /review-contract and upload the document
3. Provide context: "We are the customer, need to close by end of quarter, focus on data protection and liability"
4. Receive clause-by-clause analysis with GREEN/YELLOW/RED flags
5. Get specific redline language for YELLOW and RED items
6. Share the analysis with your deal team

NDA Triage Copy Section

1. Sales team sends an NDA from a new prospect
2. Run /triage-nda and paste or upload the NDA
3. Get instant classification: GREEN (route for signature), YELLOW (specific issues to review), or RED (needs full counsel review)
4. For GREEN NDAs, approve directly; for YELLOW/RED, address flagged issues

Daily Brief Copy Section

1. Start your morning with /brief daily
2. Get a summary of overnight contract requests, compliance questions, upcoming deadlines, and calendar items needing legal prep
3. Prioritize your day based on urgency and deadlines

Vendor Check Copy Section

1. Business team asks about a new engagement with an existing vendor
2. Run /vendor-check Acme Corp
3. See existing agreements, expiration dates, and key terms at a glance
4. Know immediately whether you need a new NDA or can proceed under existing terms

MCP Integration Copy Chapter

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

The plugin connects to your tools through MCP (Model Context Protocol) servers:

See CONNECTORS.md for the full list of supported integrations, including CLM, CRM, e-signature, and additional options.

Configure connections in .mcp.json. The plugin gracefully degrades when tools are unavailable -- it will note gaps and suggest manual checks.

Customization Copy Chapter

Playbook Configuration Copy Section

Your playbook is the heart of the contract review system. Define your positions in legal.local.md:

• Standard positions: Your preferred contract terms
• Acceptable ranges: What you can agree to without escalation
• Escalation triggers: Terms that require senior review or outside counsel

Response Templates Copy Section

Define templates for common inquiries. Templates support variable substitution and include built-in escalation triggers for situations that should not use a templated response.

Risk Framework Copy Section

Customize the risk assessment matrix to match your organization's risk appetite and classification scheme.

File Structure Copy Chapter

legal/
├── .claude-plugin/plugin.json
├── .mcp.json
├── README.md
├── commands/
│   ├── review-contract.md
│   ├── triage-nda.md
│   ├── vendor-check.md
│   ├── brief.md
│   └── respond.md
└── skills/
    ├── contract-review/SKILL.md
    ├── nda-triage/SKILL.md
    ├── compliance/SKILL.md
    ├── canned-responses/SKILL.md
    ├── legal-risk-assessment/SKILL.md
    └── meeting-briefing/SKILL.md

File: human-resources/README.md Copy Chapter

HR Plugin

A people operations plugin primarily designed for Cowork, Anthropic's agentic desktop application — though it also works in Claude Code. Helps with recruiting, onboarding, performance management, policy guidance, and compensation analysis. Works with any HR team — standalone with your input, supercharged when you connect your HRIS, ATS, and other tools.

Installation Copy Chapter

claude plugins add knowledge-work-plugins/human-resources

Commands Copy Chapter

Explicit workflows you invoke with a slash command:

All commands work standalone (provide context and details) and get supercharged with MCP connectors.

Skills Copy Chapter

Domain knowledge Claude uses automatically when relevant:

Example Workflows Copy Chapter

Drafting an Offer Copy Section

/draft-offer

Tell me the role, level, location, and comp details. Get a complete offer letter draft with terms, equity breakdown, and benefits summary.

Onboarding a New Hire Copy Section

/onboarding

Provide the new hire's name, role, team, and start date. Get a comprehensive onboarding checklist, first-week calendar, tool access list, and buddy assignment template.

Preparing for Performance Reviews Copy Section

/performance-review

Get templates for self-assessments, manager reviews, and calibration. I'll help structure feedback that's specific, actionable, and fair.

Understanding Benefits Copy Section

Just ask naturally:

What's our parental leave policy?

The employee-handbook skill triggers automatically and searches your connected knowledge base for the answer.

Compensation Benchmarking Copy Section

/comp-analysis

Upload comp data or describe your bands. Get market comparisons, band placement analysis, and recommendations for adjustments.

Standalone + Supercharged Copy Chapter

Every command and skill works without any integrations:

MCP Integrations Copy Chapter

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Connect your tools for a richer experience:

See CONNECTORS.md for the full list of supported integrations.

Settings Copy Chapter

Create a settings.local.json file to personalize:

• Cowork: Save it in any folder you've shared with Cowork (via the folder picker). The plugin finds it automatically.
• Claude Code: Save it at human-resources/.claude/settings.local.json.

{
  "company": "Your Company",
  "headquarters": "City, State",
  "employeeCount": 500,
  "benefits": {
    "healthInsurance": "Provider Name",
    "pto": "Unlimited / X days",
    "parentalLeave": "X weeks"
  },
  "compensation": {
    "currency": "USD",
    "equityType": "RSU / Options",
    "vestingSchedule": "4 years, 1 year cliff"
  }
}

The plugin will ask you for this information interactively if it's not configured.

File: finance/README.md Copy Chapter

Finance & Accounting Plugin

A finance and accounting plugin primarily designed for Cowork, Anthropic's agentic desktop application — though it also works in Claude Code. Supports month-end close, journal entry preparation, account reconciliation, financial statement generation, variance analysis, and SOX audit support.

Important: This plugin assists with finance and accounting workflows but does not provide financial, tax, or audit advice. All outputs should be reviewed by qualified financial professionals before use in financial reporting, regulatory filings, or audit documentation.

Installation Copy Chapter

claude plugins add knowledge-work-plugins/finance

Commands Copy Chapter

Skills Copy Chapter

Example Workflows Copy Chapter

Month-End Close Copy Section

1. Run /journal-entry ap-accrual 2024-12 to generate AP accrual entries
2. Run /journal-entry prepaid 2024-12 to amortize prepaid expenses
3. Run /journal-entry fixed-assets 2024-12 to book depreciation
4. Run /reconciliation cash 2024-12 to reconcile bank accounts
5. Run /reconciliation accounts-receivable 2024-12 to reconcile AR subledger
6. Run /income-statement monthly 2024-12 to generate the P&L with flux analysis

Variance Analysis Copy Section

1. Run /variance-analysis revenue 2024-Q4 vs 2024-Q3 to analyze revenue variances
2. Run /variance-analysis opex 2024-12 vs budget to investigate operating expense variances
3. Review the waterfall analysis and provide context on unexplained variances

SOX Testing Copy Section

1. Run /sox-testing revenue-recognition 2024-Q4 to generate revenue control testing workpapers
2. Run /sox-testing procure-to-pay 2024-Q4 to test procurement controls
3. Review sample selections and document test results

MCP Integration Copy Chapter

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

This plugin works best when connected to your financial data sources via MCP servers. Add the relevant servers to your .mcp.json:

ERP / Accounting System Copy Section

Connect your ERP (e.g., NetSuite, SAP) MCP server to pull trial balances, subledger data, and journal entries automatically.

Data Warehouse Copy Section

Connect your data warehouse (e.g., Snowflake, BigQuery) MCP server to query financial data, run variance analysis, and pull historical comparisons.

Spreadsheets Copy Section

Connect spreadsheet tools (e.g., Google Sheets, Excel) for workpaper generation, reconciliation templates, and financial model updates.

Analytics / BI Copy Section

Connect your BI platform (e.g., Tableau, Looker) to pull dashboards, KPIs, and trend data for variance explanations.

Note: Connect your ERP and data warehouse MCP servers to pull financial data automatically. Without these, you can paste data or upload files for analysis.

Configuration Copy Chapter

Add your data source MCP servers to the mcpServers section of .mcp.json in this plugin directory. The recommendedCategories field lists the types of integrations that enhance this plugin's capabilities:

• erp-accounting — ERP or accounting system for GL, subledger, and JE data
• data-warehouse — Data warehouse for financial queries and historical data
• spreadsheets — Spreadsheet tools for workpaper generation
• analytics-bi — BI tools for dashboards and KPI data
• documents — Document storage for policies, memos, and support
• email — Email for sending reports and requesting approvals
• chat — Team communication for close status updates and questions

File: enterprise-search/README.md Copy Chapter

Enterprise Search

An enterprise search plugin primarily designed for Cowork, Anthropic's agentic desktop application — though it also works in Claude Code. Search across all your company's tools in one place — email, chat, documents, and wikis — without switching between apps.

How It Works Copy Chapter

One query searches all your connected tools simultaneously. Claude decomposes your question, runs targeted searches across every source, and synthesizes the results into a single coherent answer with source attribution.

You: "What did we decide about the API redesign?"
              ↓ Claude searches
~~chat: #engineering thread from Tuesday with the decision
~~email: Follow-up email from Sarah with the spec
~~cloud storage: Updated API design doc (modified yesterday)
              ↓ Claude synthesizes
"The team decided on Tuesday to go with REST over GraphQL.
 Sarah sent the updated spec Thursday. The design doc
 reflects the final approach."

No tab switching. No remembering which tool has what. Ask the question, get the answer.

What It Searches Copy Chapter

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Connect any combination of sources. The more you connect, the more complete your answers.

Each source is an MCP connection. Add more sources in your MCP settings to expand what Claude can search.

Commands Copy Chapter

Search Copy Section

/enterprise-search:search what's the status of Project Aurora?
/enterprise-search:search from:sarah about:budget after:2025-01-01
/enterprise-search:search decisions made in #product this week

Supports filters: from:, in:, after:, before:, type: — applied intelligently across each source's native query syntax.

Digest Copy Section

/enterprise-search:digest --daily      # What happened today across all sources
/enterprise-search:digest --weekly     # Weekly rollup grouped by project/topic

Highlights action items, decisions, and mentions of you. Groups activity by topic so you can skim what matters.

Skills Copy Chapter

Three skills power the search experience:

Search Strategy — Query decomposition and source-specific translation. Breaks your natural language question into targeted searches per source, handles ambiguity, and falls back gracefully when sources are unavailable.

Source Management — Knows which MCP sources are available, guides you to connect new ones, manages source priority, and handles rate limits.

Knowledge Synthesis — Combines results from multiple sources into coherent answers. Deduplicates cross-source information, attributes sources, scores confidence based on freshness and authority, and summarizes large result sets.

Example Workflows Copy Chapter

Finding a decision Copy Section

You: /enterprise-search:search when did we decide to switch to Postgres?

Claude searches:
  ~~chat → #engineering, #infrastructure for "postgres" "switch" "decision"
  ~~email → threads with "postgres" in subject
  ~~cloud storage → docs mentioning database migration

Result: "The decision was made March 3 in #infrastructure (link).
         Sarah's email on March 4 confirmed the timeline.
         The migration plan doc was updated March 5."

Catching up after time off Copy Section

You: /enterprise-search:digest --weekly

Claude scans:
  ~~chat → channels you're in, DMs, mentions
  ~~email → inbox activity
  ~~cloud storage → docs shared with you or modified

Result: Grouped summary by project with action items
        flagged and decisions highlighted.

Finding an expert Copy Section

You: /enterprise-search:search who knows about our Kubernetes setup?

Claude searches:
  ~~chat → messages about Kubernetes, k8s, clusters
  ~~cloud storage → docs authored about infrastructure
  Wiki → runbooks and architecture docs

Result: "Based on message history and doc authorship,
         Alex and Priya are your go-to people for k8s.
         Here's the main runbook (link)."

Getting Started Copy Chapter

# 1. Install
claude plugins add knowledge-work-plugins/enterprise-search

# 2. Search across everything
/enterprise-search:search [your question here]

# 3. Get a digest
/enterprise-search:digest --daily

The more sources you connect via MCP, the more complete your search results. Start with ~~chat, ~~email, and ~~cloud storage, then add your wiki, project management tool, and CRM as needed.

Philosophy Copy Chapter

Knowledge workers spend hours every week hunting for information scattered across tools. The answer exists somewhere — in a Slack thread, an email chain, a doc, a wiki page — but finding it means searching each tool individually, cross-referencing results, and hoping you checked the right place.

Enterprise Search treats all your tools as one searchable knowledge base. One query, all sources, synthesized results. Your company's knowledge shouldn't be locked in silos. Search everything at once.

File: engineering/skills/documentation/SKILL.md Copy Chapter

name: documentation Copy Chapter

Technical Documentation

Write clear, maintainable technical documentation for different audiences and purposes.

Document Types Copy Chapter

README Copy Section

• What this is and why it exists
• Quick start (< 5 minutes to first success)
• Configuration and usage
• Contributing guide

API Documentation Copy Section

• Endpoint reference with request/response examples
• Authentication and error codes
• Rate limits and pagination
• SDK examples

Runbook Copy Section

• When to use this runbook
• Prerequisites and access needed
• Step-by-step procedure
• Rollback steps
• Escalation path

Architecture Doc Copy Section

• Context and goals
• High-level design with diagrams
• Key decisions and trade-offs
• Data flow and integration points

Onboarding Guide Copy Section

• Environment setup
• Key systems and how they connect
• Common tasks with walkthroughs
• Who to ask for what

Principles Copy Chapter

1. Write for the reader — Who is reading this and what do they need?
2. Start with the most useful information — Don't bury the lede
3. Show, don't tell — Code examples, commands, screenshots
4. Keep it current — Outdated docs are worse than no docs
5. Link, don't duplicate — Reference other docs instead of copying

File: engineering/README.md Copy Chapter

Engineering Plugin

A software engineering plugin primarily designed for Cowork, Anthropic's agentic desktop application — though it also works in Claude Code. Helps with standups, code review, architecture decisions, incident response, debugging, and technical documentation. Works with any engineering team — standalone with your input, supercharged when you connect your source control, project tracker, and monitoring tools.

Installation Copy Chapter

claude plugins add knowledge-work-plugins/engineering

Commands Copy Chapter

Explicit workflows you invoke with a slash command:

All commands work standalone (paste code, describe your system, upload files) and get supercharged with MCP connectors.

Skills Copy Chapter

Domain knowledge Claude uses automatically when relevant:

Example Workflows Copy Chapter

Morning Standup Copy Section

/standup

If your tools are connected, I'll pull your recent commits, PR activity, and ticket updates. Otherwise, tell me what you worked on and I'll format it.

Code Review Copy Section

/review https://github.com/org/repo/pull/123

Share a PR link, paste a diff, or point to files. Get a structured review covering security, performance, correctness, and style.

Debugging an Issue Copy Section

/debug Users are getting 500 errors on the checkout page

Walk through a structured debugging process: reproduce, isolate, diagnose, fix. I'll help you think through it systematically.

Architecture Decision Copy Section

/architecture Should we use a message queue or direct API calls between services?

Get a structured ADR with options analysis, trade-offs, and a recommendation.

Incident Response Copy Section

/incident The payments service is returning 503s

Start an incident workflow: triage severity, draft communications, track timeline, and generate a postmortem when resolved.

Pre-Deploy Check Copy Section

/deploy-checklist auth-service v2.3.0

Get a customized deployment checklist based on your service and what's changing.

Standalone + Supercharged Copy Chapter

Every command and skill works without any integrations:

MCP Integrations Copy Chapter

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Connect your tools for a richer experience:

See CONNECTORS.md for the full list of supported integrations.

Settings Copy Chapter

Create a local settings file at engineering/.claude/settings.local.json to personalize:

{
  "name": "Your Name",
  "title": "Software Engineer",
  "team": "Your Team",
  "company": "Your Company",
  "techStack": ["Python", "TypeScript", "PostgreSQL", "AWS"],
  "defaultBranch": "main",
  "deployProcess": "canary"
}

The plugin will ask you for this information interactively if it's not configured.

File: design/README.md Copy Chapter

Design Plugin

A design productivity plugin primarily designed for Cowork, Anthropic's agentic desktop application — though it also works in Claude Code. Helps with design critique, system management, UX writing, accessibility, research synthesis, and developer handoff. Works with any design team — standalone with your input, supercharged when you connect Figma and other tools.

Installation Copy Chapter

claude plugins add knowledge-work-plugins/design

Commands Copy Chapter

Explicit workflows you invoke with a slash command:

All commands work standalone (describe your design or paste screenshots) and get supercharged with MCP connectors.

Skills Copy Chapter

Domain knowledge Claude uses automatically when relevant:

Example Workflows Copy Chapter

Getting Design Feedback Copy Section

/critique

Share a Figma link, screenshot, or describe your design. Get structured feedback on usability, visual hierarchy, consistency, and accessibility.

Auditing Your Design System Copy Section

/design-system audit

I'll review your component library for consistency, completeness, and naming conventions. Get a report with specific improvement recommendations.

Writing UX Copy Copy Section

/ux-copy error messages for payment flow

Get context-appropriate copy with tone guidance, alternatives, and localization notes.

Developer Handoff Copy Section

/handoff

Share a Figma link and get a complete spec: measurements, design tokens, component states, interaction notes, and edge cases.

Accessibility Check Copy Section

/accessibility

Share a design or URL. Get a WCAG 2.1 AA compliance report with specific issues, severity, and remediation steps.

Synthesizing Research Copy Section

/research-synthesis

Upload interview transcripts, survey results, or usability test notes. Get themes, insights, and prioritized recommendations.

Standalone + Supercharged Copy Chapter

Every command and skill works without any integrations:

MCP Integrations Copy Chapter

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Connect your tools for a richer experience:

See CONNECTORS.md for the full list of supported integrations.

File: data/README.md Copy Chapter

Data Analyst Plugin

A data analyst plugin primarily designed for Cowork, Anthropic's agentic desktop application — though it also works in Claude Code. SQL queries, data exploration, visualization, dashboards, and insight generation. Works with any data warehouse, any SQL dialect, and any analytics stack.

Installation Copy Chapter

claude plugins add knowledge-work-plugins/data

What It Does Copy Chapter

This plugin transforms Claude into a data analyst collaborator. It helps you explore datasets, write optimized SQL, build visualizations, create interactive dashboards, and validate analyses before sharing with stakeholders.

With a Data Warehouse Connection Copy Section

Connect your data warehouse MCP server (e.g., Snowflake, Databricks, BigQuery, or any SQL-compatible database) for the best experience. Claude will:

• Query your data warehouse directly
• Explore schemas and table metadata
• Run analyses end-to-end without copy-pasting
• Iterate on queries based on results

Without a Data Warehouse Connection Copy Section

Without a data warehouse connection, paste SQL results or upload CSV/Excel files for analysis and visualization. Claude can also write SQL queries for you to run manually, and then analyze the results you provide.

Commands Copy Chapter

Skills Copy Chapter

Example Workflows Copy Chapter

Ad-Hoc Analysis Copy Section

You: /analyze What was our monthly revenue trend for the past 12 months, broken down by product line?

Claude: [Writes SQL query] → [Executes against data warehouse] → [Generates trend chart]
       → [Identifies key patterns: "Product line A grew 23% YoY while B was flat"]
       → [Validates results with sanity checks]

Data Exploration Copy Section

You: /explore-data users table

Claude: [Profiles table: 2.3M rows, 47 columns]
       → [Reports: created_at has 0.2% nulls, email has 99.8% cardinality]
       → [Flags: status column has unexpected value "UNKNOWN" in 340 rows]
       → [Suggests: "High-value dimensions to explore: plan_type, signup_source, country"]

Query Writing Copy Section

You: /write-query I need a cohort retention analysis -- users grouped by signup month,
     showing what % are still active 1, 3, 6, and 12 months later. We use Snowflake.

Claude: [Writes optimized Snowflake SQL with CTEs]
       → [Adds comments explaining each step]
       → [Includes performance notes about partition pruning]

Dashboard Building Copy Section

You: /build-dashboard Create a sales dashboard with monthly revenue, top products,
     and regional breakdown. Here's the data: [pastes CSV]

Claude: [Generates self-contained HTML file]
       → [Includes interactive Chart.js visualizations]
       → [Adds dropdown filters for region and time period]
       → [Opens in browser for review]

Pre-Share Validation Copy Section

You: /validate [shares analysis document]

Claude: [Reviews methodology] → [Checks for survivorship bias in churn analysis]
       → [Verifies aggregation logic] → [Flags: "Denominator excludes trial users
          which could overstate conversion rate by ~5pp"]
       → [Confidence: "Ready to share with noted caveat"]

Connecting Your Data Stack Copy Chapter

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

This plugin works best when connected to your data infrastructure. Add MCP servers for:

• Data Warehouse: Snowflake, Databricks, BigQuery, Definite, or any SQL-compatible database
• Analytics/BI: Amplitude, Looker, Tableau, or similar
• Notebooks: Jupyter, Hex, or similar
• Spreadsheets: Google Sheets, Excel
• Data Orchestration: Airflow, dbt, Dagster, Prefect
• Data Ingestion: Fivetran, Airbyte, Stitch

Configure MCP servers in your .mcp.json or Claude Code settings to enable direct data access.

File: customer-support/README.md Copy Chapter

Customer Support Plugin

A customer support plugin primarily designed for Cowork, Anthropic's agentic desktop application — though it also works in Claude Code. Provides ticket triage, escalation management, response drafting, customer research, and knowledge base authoring for support teams.

Installation Copy Chapter

claude plugins add knowledge-work-plugins/customer-support

What It Does Copy Chapter

This plugin turns Claude into a customer support co-pilot. It helps you:

• Triage incoming tickets with structured categorization, priority assessment, and routing recommendations
• Research customer questions by synthesizing information from multiple sources with confidence scoring
• Draft professional responses tailored to the situation, urgency, and communication channel
• Package escalations with full context, reproduction steps, and business impact for engineering or product
• Write KB articles from resolved issues to reduce future ticket volume

Commands Copy Chapter

Skills Copy Chapter

Data Sources Copy Chapter

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Connect your support platform, knowledge base, and communication tools for the best experience. Without them, provide customer context manually.

Included MCP connections:

• Chat (Slack) for internal discussions and customer channel context
• Support platform (Intercom) for ticket history and customer conversations
• CRM (HubSpot) for account details and contact information
• Knowledge base (Guru, Notion) for internal documentation and runbooks
• Project tracker (Atlassian) for bug reports and feature requests
• Email and cloud storage (Microsoft 365) for customer correspondence

Additional options:

• See CONNECTORS.md for alternative tools in each category

Example Workflows Copy Chapter

Triaging an Incoming Ticket Copy Section

You: /triage Customer says their dashboard has been showing a blank
     page since this morning — they're on the Enterprise plan

Claude: Analyzing the issue...

## Triage: Dashboard blank page — Enterprise customer

**Category:** Bug
**Priority:** P2 — High (core feature broken, enterprise customer)
**Product area:** Dashboard / Frontend

### Routing Recommendation
Route to: Tier 2 Support (investigate browser/account specifics,
then escalate to Engineering if reproducible)

### Suggested Initial Response
[Draft acknowledging the issue, asking clarifying questions
about browser and any recent changes, offering status page link]

Researching a Customer Question Copy Section

You: /research Does our platform support SSO with Okta?

Claude: Let me check across available sources...

[Searches docs, knowledge base, previous conversations,
 and web sources — synthesizes answer with confidence
 level and source attribution]

Packaging an Escalation Copy Section

You: /escalate API returning 500 errors intermittently — 3
     Enterprise customers reported this week

Claude: I'll gather context and build the escalation brief...

[Pulls ticket history, identifies affected accounts,
 structures reproduction steps, assesses business impact,
 and generates a structured escalation for engineering]

Drafting a Response Copy Section

You: /draft-response Customer escalation — their integration
     has been down for 2 days and they're frustrated

Claude: [Generates empathetic, professional response acknowledging
 the frustration, taking ownership, providing a clear action
 plan with timeline, and offering a call]

Writing a KB Article Copy Section

You: /kb-article How to configure webhook notifications —
     just resolved this for the third customer this month

Claude: [Generates a structured how-to article with prerequisites,
 step-by-step instructions, verification steps, and common
 issues — optimized for search]

Configuration Copy Chapter

The plugin works out of the box with the included MCP connections. For the richest experience, connect additional data sources through your Claude settings:

1. Support platform: Add your ticketing system for ticket history and customer context
2. Knowledge base: Add your wiki for internal documentation and existing KB articles
3. Project tracker: Add your issue tracker for bug reports and feature requests
4. CRM: Add your CRM for account details and contact information

Without these connections, the plugin will ask you to provide context manually and offer frameworks and templates you can fill in with your own data.