Minimum Requirements to Run Knowledge-Work Plugins with Claude: Complete Setup Guide

To run the Knowledge-Work Plugins with Claude, you need a paid Anthropic subscription (Cowork or Claude Code), the Claude CLI installed locally, and internet connectivity to download the plugin files from the marketplace.

The Knowledge-Work Plugins from the anthropics/knowledge-work-plugins repository are pure-metadata packages consisting of Markdown skill files, JSON manifests, and optional MCP connector definitions. Because they contain no executable code, the minimum requirements to run these plugins with Claude are significantly lighter than traditional software dependencies. This guide breaks down the exact prerequisites and installation steps based on the official source code.

What Are the Knowledge-Work Plugins?

The Knowledge-Work Plugins are pure-metadata packages—they contain no executable code that runs on your local machine. Instead, they consist of:

• Markdown skill files that define capabilities and instructions
• JSON manifests (.claude-plugin/plugin.json) that register the plugin with Claude
• Optional MCP connector definitions (.mcp.json) for external tool integration

This architecture means you do not need Python, Node.js, Docker, or any runtime environment installed to use the core functionality.

Core Requirements to Run Plugins with Claude

Claude Access (Cowork or Claude Code)

You need an active Anthropic subscription that includes the plugin engine, specifically either Cowork or Claude Code access. The plugins run inside Claude's environment; without an active Claude session, the slash commands and skills cannot be invoked. This requirement is documented in the repository's README.md under the "Why Plugins" section.

Claude CLI

The claude command-line tool is required to fetch and register plugins. The CLI provides three critical commands for plugin management:

• claude plugin marketplace add – Registers the plugin source
• claude plugin install – Downloads and installs specific plugins
• claude plugin validate – Verifies plugin structure and manifest integrity

Without the CLI, you cannot pull the plugin files from the remote marketplace into your local Claude environment.

Internet Connectivity

Since the plugins are stored remotely in the marketplace index, active internet connectivity is required to download the plugin files on demand. The CLI pulls these files during installation and when updating to new versions.

Optional Requirements for Enhanced Functionality

While the core plugins run with the three requirements above, some features need additional setup.

MCP Connectors

Many plugins include .mcp.json files that define Model Context Protocol (MCP) server connections. These connectors let Claude interact with external SaaS tools like QuickBooks, HubSpot, or Slack. According to the plugin manifest examples in the repository, these connectors are optional for basic skills but required for data-driven commands.

External Tool Authentication

When using MCP connectors, you must provide API keys, OAuth tokens, or other credentials stored in the MCP server configuration. Each plugin's documentation includes a "What you'll need to connect" section specifying the required authentication for tools like QuickBooks or PayPal.

Installing Knowledge-Work Plugins

With the minimum requirements met, installation requires only two commands. First, add the Knowledge-Work Plugins marketplace to your CLI environment:

claude plugin marketplace add anthropics/knowledge-work-plugins

Then install a specific plugin, such as the Small-Business plugin:

claude plugin install small-business@knowledge-work-plugins

To verify the plugin structure is valid (useful when developing custom plugins), run:

claude plugin validate small-business/.claude-plugin/plugin.json

After installation, Claude automatically exposes the plugin's slash commands. You can immediately use commands like /plan-payroll for cash-flow forecasting or /smb-onboard for guided onboarding, even without any connectors configured.

Key Files in the Repository

Understanding the file structure helps clarify why the requirements are minimal:

Path	Purpose
README.md	High-level overview and installation instructions
.claude-plugin/plugin.json	Manifest telling Claude the plugin name, entry points, and description
.mcp.json	Defines MCP server connections for external tools (optional)
*/skills/SKILL.md	Human-readable skill definitions consumed by Claude
commands/	Slash-command definitions mapping natural language to skill pipelines

These files live under the repository root. For example, the Small-Business plugin manifest is located at small-business/.claude-plugin/plugin.json, while its skill catalog resides in small-business/skills/.

Summary

• Minimum requirements: Claude subscription (Cowork/Code), Claude CLI, and internet access
• No runtime dependencies: Plugins are pure metadata—no Python, Node.js, or Docker required
• Optional enhancements: MCP connectors (.mcp.json) and external API credentials enable advanced integrations
• Quick start: Two CLI commands (marketplace add and plugin install) get you running
• Core functionality works immediately: Slash commands like /smb-onboard function without external tool connections

Frequently Asked Questions

Do I need to install Python or Node.js to run these plugins?

No. The Knowledge-Work Plugins contain no executable code. They are pure-metadata packages consisting of Markdown and JSON files that Claude interprets directly. You only need the Claude CLI to fetch and register these files.

Can I use the plugins without connecting external tools like QuickBooks?

Yes. The core skills and slash commands function without any MCP connectors configured. However, commands that need to read or write data from external systems (like generating reports from QuickBooks) will prompt you to set up the relevant connector and authentication.

Where are the plugin files stored after installation?

The Claude CLI downloads the plugin files from the marketplace index and registers them in your local Claude environment. The exact local path depends on your Claude CLI configuration, but the files originate from the repository paths like small-business/.claude-plugin/plugin.json and small-business/skills/.

How do I validate that a plugin is correctly installed?

Use the claude plugin validate command followed by the path to the plugin manifest. For example: claude plugin validate small-business/.claude-plugin/plugin.json. This verifies the JSON structure and ensures Claude can properly load the skill definitions.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}