RSS
Tools

Anthropic's public GitHub libraries of plugins and skills

Anthropic keeps three public GitHub repos for extending Claude: its own Claude Code plugins, role-based plugins built for Cowork, and the Agent Skills behind Claude's document features. What is in each, how to install them and what changed.

photo of half-flipped laptop
Photo by Michał Kubalczyk on Unsplash

Updated November 20, 2026: Expanded with install commands, scopes, what each repo contains and the new submission process.

Anthropic publishes three public GitHub repositories that are worth bookmarking if you use Claude Code or Claude Cowork: anthropics/claude-plugins-official, anthropics/knowledge-work-plugins and anthropics/skills. Together they hold ready-made plugins, role-specific bundles and the reference skills Anthropic uses in its own products. GitHub lists the first two under Apache 2.0; the skills repo has no repo-wide licence field, though it says many of its skills are Apache 2.0. Reading them is one of the quickest ways to learn how plugins and skills are put together. Details below are as of November 20, 2026; all three repos were updated between November 16 and 20.

claude-plugins-official: Anthropic's own Claude Code plugins

This repo is the home of the claude-plugins-official marketplace. Its plugins folder holds plugins Anthropic develops itself, including commit-commands, code-review, pr-review-toolkit, feature-dev, frontend-design, hookify, plugin-dev, skill-creator, security-guidance and a set of language-server plugins for Python, TypeScript, Go, Rust, Swift, Kotlin and others. An external_plugins folder keeps third-party plugins added before submissions moved to claude.ai/directory/manage, plus Anthropic's channel plugins for Discord, fakechat, iMessage and Telegram.

As of November 20, the README says all plugins are submitted at claude.ai/directory/manage and served across Claude products from there, pull requests to the repo are not monitored, and the marketplace file is being reduced over time to Anthropic's own plugins.

Claude Code adds this marketplace for you the first time you start an interactive terminal session, so installing is one command:

/plugin install commit-commands@claude-plugins-official

In a session, that opens the plugin's details in the /plugin panel so you can review it and pick a scope first. For plugins in the official marketplace the panel shows two context-cost estimates: Every turn, what the plugin adds to each message, and When invoked, what its skills and agents add once loaded. Those estimates appear only when you open a plugin by naming its marketplace, as above, or from the Marketplaces tab, not from the Discover list you get by running /plugin with no name. After install, the summary tells you whether the plugin is active now, needs a reload (Claude Code runs /reload-plugins for you) or has a bundled MCP server that needs setup. claude plugin list in your shell shows each plugin's version, scope and status.

knowledge-work-plugins: plugins for specific jobs

This repo holds plugins built for Claude Cowork that also work in Claude Code. Each one bundles skills, connectors (MCP servers), slash commands and sub-agents for a job function. The README's table lists 11, including productivity, sales, customer-support, product-management, marketing, legal, finance, data, enterprise-search and bio-research, plus cowork-plugin-management for building your own. The repo also has seven more top-level folders not in that table: design, engineering, human-resources, operations, small-business, partner-built and pdf-viewer. Cowork users install from claude.com/plugins.

From Claude Code, add the marketplace and then install a plugin:

claude plugin marketplace add anthropics/knowledge-work-plugins
claude plugin install sales@knowledge-work-plugins

Commands are namespaced by plugin, such as /sales:call-prep or /data:write-query. Everything is markdown and JSON, so the README encourages you to swap connectors in .mcp.json and drop your own terminology and processes into the skill files.

skills: the reference Agent Skills

The skills repo contains example skills across creative, technical and enterprise tasks, the Agent Skills specification, and a template. It also includes the docx, pdf, pptx and xlsx skills that power Claude's own document creation. Anthropic says many of the skills are Apache 2.0, including the document ones, so check the licence of each skill before reusing it. It labels the repo as demonstration material, says Claude's actual behaviour may differ from what the skills show, and advises testing a skill in your own environment before relying on it for critical work. You don't need Claude Code for these: the README says the example skills are already available on paid Claude.ai plans, and the Claude API accepts both Anthropic's pre-built skills and custom uploads. In Claude Code:

/plugin marketplace add anthropics/skills
/plugin install document-skills@anthropic-agent-skills
/plugin install example-skills@anthropic-agent-skills

Once installed, you just mention the skill, for example asking Claude Code to use the PDF skill to extract form fields from a file. A skill is a folder with a SKILL.md file whose frontmatter needs only two fields, name and description, followed by the instructions Claude should follow.

Choosing where a plugin applies

When you install, Claude Code asks for a scope:

  • User scope: on for you in every project, recorded in ~/.claude/settings.json.
  • Project scope: on for everyone in the repository, recorded in .claude/settings.json, which you commit. Committing turns the plugin on for collaborators but does not download it; each one runs claude plugin install <name>@<marketplace> --scope project once per clone.
  • Local scope: on for you in this repository only, recorded in .claude/settings.local.json.

If the same plugin is set at several scopes, local overrides project and project overrides user. Some plugins are set by their author to start turned off; they stay off until you run claude plugin enable <name> or switch them on in the Installed tab.

Two limits are worth knowing. Cloud sessions, including claude.ai/code, have no plugin browser and load neither the plugins installed on your own machine nor the ones your repository's .claude/settings.json turns on. And plugins can run hooks and MCP servers: Anthropic warns that it does not control what MCP servers, files or other software any plugin includes, and cannot verify that a plugin will work as intended or won't change. Read the details pane and the plugin's homepage before installing.

Our take

In our view the skills repo is the most useful of the three to study: the document skills are the ones behind Claude's own file features, so they are a working reference for production-style skills, with the demonstration caveat above. The knowledge-work plugins are best treated as templates: their value comes after you replace the generic connectors and processes with your team's own.

Source: anthropics/claude-plugins-official (GitHub), anthropics/knowledge-work-plugins (GitHub), anthropics/skills (GitHub), Install and manage plugins (Claude Code Docs)

This story first appeared in the claudefox daily briefing for November 10, 2026.