Claude Code plugin

The Kreel plugin for Claude Code, kreel-skills, packages Kreel’s ready-made prompt library as slash commands. Instead of typing or pasting a prompt, you run something like /kreel:daily-pulse and Claude Code fills in the rest.

The plugin does not connect to Kreel by itself. It wraps prompts that call Kreel’s MCP tools, so Claude Code needs an active MCP connection to Kreel before any command will produce real data.

Plugin vs. MCP connection

These are two separate things. The MCP connection is what lets Claude Code reach your Kreel data at all. The plugin is a shortcut layer on top of that connection: one keystroke instead of typing out a full prompt.

Before you start

You need:

• Claude Code installed.
• An active Kreel MCP connection in Claude Code, either the OAuth login or the API-key bridge. See Connect over MCP if you haven’t set this up yet.

Connect Kreel over MCP

If Claude Code isn’t already connected to Kreel, the fastest way is the OAuth one-liner:

claude mcp add --transport http kreel https://api.kreel.ai/mcp

This opens a Kreel login popup once. Approve it, and Kreel’s tools appear in Claude Code. No API key is needed for this path.

If you’d rather authenticate with an API key instead, for example for a shared or non-interactive environment, see Connect over MCP for the API-key bridge setup.

Install the plugin

1. In Claude Code, run:

   /plugin install /path/to/BeyondPeaksAI/plugin/kreel-skills

   pointing at a local copy of the kreel-skills plugin folder.
2. Confirm it loaded by running a command, for example /kreel:daily-pulse.

Not yet on the plugin marketplace

The Kreel plugin is not yet published to the Anthropic plugin marketplace. Until it is, installing it means pointing Claude Code at a local copy of the plugin folder, as shown above.

What it ships

The plugin ships one slash command per prompt in Kreel’s prompt library: 21 commands in total.

• 17 read-only commands spanning reporting, health checks, audits, and planning, for example /kreel:daily-pulse, /kreel:weekly-report, /kreel:meta-account-audit, and /kreel:budget-reallocation.
• One onboarding command, /kreel:onboard-brand. It interviews you, reads your connected platform data, and writes your Brand Knowledge Base profile, sections, competitors, and learnings. It confirms before every write and can be run again later to fill in gaps.
• Three draft-generation commands: /kreel:draft-google-rsa, /kreel:draft-klaviyo-campaign, and /kreel:draft-meta-ads-from-folder.

For what each command does and what arguments it takes, see the prompt library.

Draft commands never publish anything

The three draft commands only read your performance data and return copy for you to paste into Google Ads, Meta, or Klaviyo yourself. They do not create, upload, change, schedule, activate, or send anything on those platforms.

Running a command

Some commands take no arguments, some take one, and two take more than one.

/kreel:weekly-report 2026-04-14
/kreel:daily-pulse
/kreel:creative-fatigue-check
/kreel:draft-google-rsa launch our premium summer collection
/kreel:draft-meta-ads-from-folder "./new creatives" "sales conversions"
/kreel:draft-klaviyo-campaign "recent purchasers" "summer launch"

A single-argument command like draft-google-rsa takes the rest of the line as one value, so you don’t need to quote it. The two commands that take more than one argument, draft-meta-ads-from-folder and draft-klaviyo-campaign, need each argument in quotes so Claude Code doesn’t merge them into one value.

You can also skip the slash command and just describe what you want in plain language. Claude Code has the same Kreel tools available either way.

Need help?

Email support@kreel.ai.