A plugin = an AI employee with skills, commands, and access built in.

Claude Code plugins

A skill is a single muscle. A plugin is a whole specialist: a marketer, a salesperson, a designer. Anthropic has built its own marketplace, and almost nobody is talking about it yet.

The AI employee store

Finance. Sales. Marketing. One prompt.

Claude Code ships with a built-in plugin store, already stocked with ready-made specialists from Anthropic. A marketer. A salesperson. A designer. No setting things up from scratch: install it, call it, it works.

`` $ claude > /plugin marketplace browse → Opens the list of plugins available in your Claude Code ``

Where to find it

The store is already built into Claude Code.

01 · Open Claude Code

In your terminal, run claude inside your project folder.

02 · Open the marketplace

Run this inside the session:

`` /plugin marketplace browse ``

You'll see the list of available marketplaces. Anthropic's is connected by default.

03 · Install the plugin you need

For example, Anthropic's marketing plugin:

`` /plugin install marketing ``

Done. All of the plugin's commands, /marketing:campaign-plan, /marketing:performance-report, and so on, are available right away.

Don't have Claude Code?

Start with installing Claude Code in 5 minutes. Plugins only work there: the browser version of Claude doesn't have this feature yet.

What it is

Not a single file. An entire department behind one button.

A plugin is a set of related tools built around a specific role. Inside Anthropic's marketing plugin you'll find skills for every job a marketer does: campaign planning, metrics reporting, competitive analysis, email campaigns, SEO audits. All under one brand, all working together.

Every plugin can bundle skills, slash commands, subagents, MCP servers, and hooks. It's not a single .md file but a whole folder with a configured workflow. Install it once and your project gains a new role.

`` # Inside Anthropic's marketing plugin marketing/ ├── skills/ │ ├── campaign-plan.md ← /marketing:campaign-plan │ ├── performance-report.md ← /marketing:performance-report │ ├── competitive-brief.md ← /marketing:competitive-brief │ ├── email-sequence.md ← /marketing:email-sequence │ ├── seo-audit.md ← /marketing:seo-audit │ ├── brand-review.md ← /marketing:brand-review │ └── draft-content.md ← /marketing:draft-content ├── agents/ │ └── content-writer.md ← subagent for long-form writing └── plugin.json ← plugin manifest ``

Why you need them

So you don't have to hire a team.

01 · Speed: no writing prompts from scratch

Every plugin is a set of templates from domain experts, packaged into commands. No need to remember how a marketer plans a campaign: type /marketing:campaign-plan and you get a ready-made brief with metrics.

02 · Cohesion: one department, one context

Commands inside a plugin are aware of each other. A report from /marketing:performance-report can go straight into /marketing:campaign-plan with no data lost along the way.

03 · Standards: Anthropic-grade quality

Plugins in the official marketplace are built by the people who made the model itself. This isn't some random YouTube guide; it's production-grade prompting for Claude 4.7.

04 · Extensibility: you can build your own

If the marketplace doesn't have what you need, build your own plugin, drop it into a GitHub repo with a plugin.json, and any Claude Code can install it. That's how we build plugins for the Russian market.

The Anthropic marketplace

Who's already working in the store.

Anthropic · /marketing · Marketing

Campaign plans, reporting, competitors, email

7 skills covering the full marketing cycle, from competitor research to email sequences and post-campaign reporting. Works well in any niche: EdTech, SaaS, e-commerce.

What's inside: campaign-plan, performance-report, competitive-brief, email-sequence, seo-audit, brand-review, draft-content

Example call: /marketing:performance-report

Anthropic · /sales · Sales

Pipeline, forecasting, meeting briefs, follow-ups

The full sales cycle: daily briefing, call prep, account research, pipeline review, revenue forecasting, post-call follow-up. Hooks into your CRM.

What's inside: daily-briefing, call-prep, account-research, pipeline-review, forecast, call-summary, draft-outreach, competitive-intelligence, create-an-asset

Example call: /sales:pipeline-review

Anthropic · /design · Design

UX copy, research, accessibility, design critique

Not about drawing, but about design thinking: mockup critiques, interface copy, accessibility audits, developer handoff specs, user research synthesis.

What's inside: design-critique, ux-copy, user-research, accessibility-review, design-handoff, research-synthesis, design-system

Example call: /design:design-critique

Anthropic · /agent-sdk-dev · Agent SDK Dev

Build Claude agents in Python or TypeScript

A skeleton for a new SDK app in one command, plus a verifier that checks your code follows SDK best practices. For anyone building on the Anthropic API.

What's inside: new-sdk-app, agent-sdk-verifier-py, agent-sdk-verifier-ts

Example call: /agent-sdk-dev:new-sdk-app

Anthropic · /pr-review-toolkit · PR Review Toolkit

Code review by 5 specialized agents

Not one generic reviewer but five different ones: code-reviewer (business logic), comment-analyzer (code comments), type-design-analyzer (types), silent-failure-hunter (silent errors), pr-test-analyzer (test coverage).

What's inside: review-pr, code-reviewer, code-simplifier, comment-analyzer, type-design-analyzer, silent-failure-hunter, pr-test-analyzer

Example call: /pr-review-toolkit:review-pr

Anthropic · /feature-dev · Feature Dev

The full feature cycle: research → plan → code → review

Launches three specialized agents: code-explorer (studies the existing code), code-architect (designs the architecture), code-reviewer (checks the result). Each runs in its own context, so nobody's attention gets diluted.

What's inside: feature-dev, code-architect, code-explorer, code-reviewer

Example call: /feature-dev

That's not the whole list: the marketplace also has hookify, commit-commands, claude-md-management, anthropic-skills (PDF, PPTX, DOCX, XLSX), and more. See the full list via /plugin marketplace browse inside Claude Code.

Our custom plugins

What we're building for the Russian market.

Anthropic's store has nothing built for the Russian market: VK, Telegram, Russian CRMs, our social networks, our funnels. So we build our own plugins and use them every day.

AGINE · custom · /smm · SMM Content Factory

Content for 9 platforms in 2 hours a day

Trend research via ScrapeCreators, reference deconstruction, safe remixing, AI art direction, image generation, publishing through n8n. A full production stack for a solo team.

What's inside: smm, trend-researcher, content-writer, art-director, publisher

Example call: /smm

AGINE · custom · /sales-assistant · Sales Assistant

An autonomous salesperson in Telegram + Instagram

Monitors every chat, qualifies leads, sends pitches, issues payment details when a lead is ready, keeps a CRM in leads.md. Runs in the background in 30-minute cycles.

What's inside: sales-assistant, lead-qualifier, payment-handler, crm-updater

Example call: /sales-assistant

AGINE · custom · /threads · Threads Automation

Scrapes trends, posts, comments, likes

The full SMM cycle for Threads: scraping the top posts for a keyword, a light remix that swaps the CTA for our Telegram, auto-publishing, replying to comments, plus 10 comments + 10 likes on other people's posts, all in our voice.

What's inside: threads, threads-parser, comment-replier, engagement-bot

Example call: /threads

AGINE · custom · /agine-architect · Architect (operations)

A CTO/COO role for our own business

Reads the MASTER audit, the backlog, and the latest session log. Breaks the work into a sprint, dispatches specialists (backend/frontend/devops/qa) in parallel, synthesizes the diffs, and runs everything through review. Production-grade management for our platform.

What's inside: agine-architect, backend-specialist, frontend-specialist, devops-specialist, qa-specialist, reviewer

Example call: /agine-architect

How to build your own plugin

A GitHub repo + a manifest. That's it.

01 · Create a GitHub repo

Any name, public or private (if it's private, users will need a token).

02 · Add the plugin structure

The skills/, commands/, and agents/ folders, plus a plugin.json file describing the plugin.

03 · Add the repo as a marketplace

In Claude Code: /plugin marketplace add github.com/your/repo. From there it's a normal install via /plugin install.

Frequently asked

How is a plugin different from a skill or MCP?