growthbook — плагин для Claude Code: фича-флаги и A/B-тесты
Управляет фича-флагами, экспериментами и метриками GrowthBook прямо из редактора. Агент создаёт флаги, настраивает таргетинг, запускает тесты и читает результаты через REST API платформы.
MIT ★ 29 обновлён 2026-10-22
/plugin install growthbook@claude-plugins-official
/plugin marketplace add anthropics/claude-plugins-officialЧто делает growthbook
Четыре скилла: feature-flags, experiments, analytics и gb-setup. Первый ведёт флаг от создания до архивации — черновики, ревью, публикация, правила таргетинга с условиями, расписания рампа, мониторинг прогрессивного раската, prerequisites и эксперименты-рефы. Второй проектирует и запускает A/B-тесты, анализирует снапшоты, останавливает с выбором победителя. Третий строит графики и дашборды из ваших метрик и таблиц фактов. Внутри 27 воркфлоу-файлов; каждый скилл читает индекс, затем загружает только нужный сценарий.
Плагин вызывает GrowthBook REST API напрямую через встроенный хелпер, MCP-сервер не нужен. Токен Personal Access привязывается к вашему пользователю в GrowthBook, поэтому флаги и эксперименты автоматически получают вас как owner. Скилл gb-setup проверяет ключ, для self-hosted установок спрашивает API и app origins, пишет ~/.config/growthbook/.env с chmod 600.
Node 18+ обязателен. После установки перезапустите агент, если скиллы не появились сразу.
Какие задачи решает
- создать фича-флаг с правилами таргетинга и условиями
- настроить мониторинг прогрессивного раската с автооткатом
- запустить A/B-тест и прочитать результаты со снапшота
- построить дашборд из метрик и таблиц фактов в GrowthBook
- проверить зависимости флага: prerequisites, эксперименты, holdouts
Примеры запросов агенту
- /growthbook:feature-flags — покажи все флаги проекта
checkout - /growthbook:experiments — запусти тест по гипотезе: новая кнопка CTA повысит конверсию на 5%
- /growthbook:analytics — построй график метрики
revenue_per_userза последний месяц
Как установить growthbook
Через маркетплейс плагинов
/plugin install growthbook@claude-plugins-official/plugin marketplace add anthropics/claude-plugins-officialПо шагам, с командами для каждой платформы: Плагины Claude Code: маркетплейсы, установка и как собрать свой
Вопросы о growthbook
Как установить growthbook в Claude Code?
Сначала /plugin marketplace add growthbook/skills, затем /plugin install growthbook@growthbook-skills. После установки запустите /growthbook:gb-setup, чтобы настроить API-ключ.
Что делает плагин growthbook?
Управляет фича-флагами и экспериментами GrowthBook через REST API. Агент создаёт флаги, настраивает таргетинг, запускает A/B-тесты, читает метрики и строит дашборды.
Где взять API-ключ для growthbook?
Personal Access Token выдаётся в app.growthbook.io/account/personal-access-tokens. Токен привязывается к вашему пользователю, флаги и эксперименты автоматически получают вас как owner.
Исходный текст
SKILL.md · MIT
# GrowthBook Agent Skills
[GrowthBook](https://www.growthbook.io) is an open source Feature Flagging and Experimentation platform.
Agent skills for GrowthBook — feature flagging and experimentation playbooks for Claude Code, Cursor, and other agent tools that follow the [Agent Skills](https://agentskills.io) standard.
The skills call the [GrowthBook REST API](https://docs.growthbook.io/api) directly through a small bundled helper. No MCP server required.
## What's included
Four skills, one per domain. Each one is a router: it loads a short index, then reads only the workflow that matches what you asked for. The 27 workflows live as reference files inside their skill and stay out of context until they're needed.
### `feature-flags`
The full flag lifecycle. Flag changes go through a draft revision before going live, so the draft → review → publish workflows sit alongside the ones that make the change.
| Workflow | What it does |
| --- | --- |
| `flag-create` | Create a new feature flag — collision check, value type, environments, defaultValue. Ships disabled everywhere. |
| `flag-search` | Search, list, and audit flags by project, tag, owner, environment state, or staleness. Read-only. |
| `flag-graph` | Trace a flag's dependency graph: prerequisites, dependents, linked experiments and holdouts. Read-only. |
| `flag-toggle` | Enable or disable a flag in a specific environment (the kill switch). Review-gated. |
| `flag-targeting` | Add, edit, or remove force / rollout rules — with conditions, saved groups, and rule-level prerequisites. Full operator reference for MongoDB-style conditions. |
| `flag-rules` | List rules, delete a rule, reorder, or route to the right rule workflow. |
| `flag-experiment` | Add an experiment-ref rule to a flag to run an A/B test through it. |
| `flag-schedule` | Time-gate a rule: set a start and/or end datetime for automatic activation. |
| `flag-ramp` | Multi-step ramp schedule: progressively increase coverage over time with per-step intervals or manual approval gates. Includes live ramp management (advance, pause, rollback, approve-step). |
| `flag-monitoring` | Monitored progressive rollout ("safe rollout"): ramp schedule with guardrail metric monitoring and optional auto-rollback. |
| `flag-prerequisites` | Gate an entire flag on another boolean flag being on. |
| `flag-default-value` | Change the fallback value served when no rules match. |
| `flag-metadata` | Update a flag's description, owner, project, tags, custom fields, or JSON schema. |
| `flag-revisions` | List and inspect open drafts, check who owns them, see approval status, create or discard drafts. The "what's in flight?" workflow. |
| `flag-review` | Request an approval review on a draft, or submit one (approve / request-changes / comment). |
| `flag-publish` | Publish a draft live, resolve merge conflicts (rebase), discard, or revert to a prior revision. |
| `flag-cleanup` | Archive or delete a stale flag, walking through code-site inlining first. Two-step safety gate (archive → verify → delete). |
### `experiments`
| Workflow | What it does |
| --- | --- |
| `experiment-brainstorm` | Propose new experiment ideas grounded in your team's past stopped-experiment history. |
| `experiment-design` | Walk through hypothesis, variations, primary metric, guardrails, and sample size to produce a launchable spec. Reads only. |
| `experiment-launch` | End-to-end launch: create the experiment, prep or reuse the feature flag, wire the experiment-ref rule, and call `/start`. Handles approval and pre-launch checklist failure paths. |
| `experiment-analyze` | Trigger a fresh snapshot, poll until ready, then interpret results (SRM check, lifts, CIs, guardrails). |
| `experiment-stop` | Stop a running experiment, optionally declaring a winner and enabling a temporary rollout. Full post-stop flag disposition guidance. |
| `learnings` | Search, read, and record Learnings — durable conclusions drawn across multiple experiments. Check before designing a test; record after one generalizes. |
### `analytics`
Turn the metrics and fact tables you already use for experimentation into ad-hoc charts and saved dashboards with GrowthBook's [Product Analytics](https://docs.growthbook.io/app/product-analytics) Explorer.
| Workflow | What it does |
| --- | --- |
| `metric-search` | Search, list, and audit fact metrics and fact tables — definitions, columns, and what's chartable. Read-only. |
| `metric-create` | Create a fact metric, and the fact table underneath it when one doesn't exist yet. Covers all seven metric types; analysis settings inherit the org defaults. |
| `analytics-explore` | Build and run a chart: a metric over time, a fact-table aggregation, or a raw warehouse table. Returns the numbers plus a deep link to the rendered chart. |
| `dashboard-create` | Build a dashboard from a goal or a set of metrics. Chart blocks carry a config and the create call runs every one of them, so it's one write for the whole page. |
| `dashboard-edit` | Change a dashboard that exists: add or remove a chart, swap a metric, change the timeframe, rename or re-scope it. Reads the dashboard, then writes the full block list back. |
### `gb-setup`
Walks you through your API key and, for self-hosted installations, the API and app origins. Validates against the live API and writes `~/.config/growthbook/.env` with `chmod 600`. Re-run anytime to update.
## Install
### 1. Install the plugin
**Claude Code:**
```text
/plugin marketplace add growthbook/skills
/plugin install growthbook@growthbook-skills
```
**Cursor, Codex, Warp, Zed, and other [agentskills.io](https://agentskills.io)-compatible agents:**
```bash
npx skills add growthbook/skills
```
This installs the skills at project scope. Restart your agent if the skills don't appear immediately. Node 18+ is required (which is what most agents already run on).
### 2. Configure credentials
The quickest path is to run the setup skill:
```text
/growthbook:gb-setup
```
It walks you through your API key and (for self-hosted) your API and app origins — then validates against the live API and writes `~/.config/growthbook/.env` with `chmod 600`. Every other skill reads that file automatically.
**Prefer shell-rc?** You can export the variables instead. The skills read environment variables first; the file is only consulted when an env var is unset.
```bash
export GB_API_KEY=<your-key> # required: PAT or Secret Key
export GB_API_URL=https://api.your-host # self-hosted only
export GB_APP_URL=https://growthbook.your-host # self-hosted only; trusted UI origin
```
Get a Personal Access Token from [`app.growthbook.io/account/personal-access-tokens`](https://app.growthbook.io/account/personal-access-tokens). The token is tied to your GrowthBook user, so flags and experiments the write skills create are attributed to you automatically — no separate owner setting needed.
### 3. Verify
```text
/growthbook:feature-flags
```
Ask it to list your flags. If anything's wrong with the config, the error points back at `/growthbook:gb-setup`.
## How to invoke
Skills can activate automatically or through the client's explicit skill-invocation UI:
- **Automatically** when the agent detects an intent matching the skill's description ("create a feature flag for the new pricing page" → `feature-flags`, which then reads its `flag-create` workflow; "what should we test next" → `experiments` → `experiment-brainstorm`).
- **Claude Code plugin:** type `/growthbook:feature-flags`, `/growthbook:experiments`, `/growthbook:analytics`, or `/growthbook:gb-setup`. These domain slash commands remain registered; reference workflows are not separate commands.
- **Other Agent Skills clients:** explicitly select or invoke `feature-flags`, `experiments`, `analytics`, or `gb-setup` using that client's skill UI or syntax.
You don't invoke workflows directly — the domain skill picks one from your request. Workflows hand off to each other, so multi-step jobs compose cleanly:
- **Experiment-first:** `learnings` (what do we already know?) → `experiment-design` → `experiment-launch` → `experiment-analyze` → `experiment-stop` → `flag-cleanup`, recording back to `learnings` when a result generalizes
- **Flag-first:** `flag-create` → `flag-toggle` → `flag-targeting` → `flag-ramp` / `flag-monitoring` → `flag-cleanup`
- **Experiment on an existing flag:** `flag-experiment` → `experiment-launch` (reuses the existing flag) → `experiment-stop` → `flag-cleanup`
- **Analytics:** `metric-search` → `analytics-explore` → `experiment-design` (when a chart surfaces something worth testing)
- **Metric setup:** `metric-search` (does it exist?) → `metric-create` → `analytics-explore` (sanity-check the numbers) → `experiment-design`
- **Dashboards:** `metric-search` → `analytics-explore` (check one chart reads right) → `dashboard-create` → `dashboard-edit` (as the questions change)
## What these skills do not do
- **No datasource creation.** Connect datasources in the GrowthBook UI and reference them by ID; `metric-create` covers fact tables and fact metrics, but not the warehouse connection underneath them.
- **No metric analysis tuning.** `metric-create` defines what a metric measures; conversion windows, capping, priors, and risk thresholds inherit the org defaults and are tuned in the GrowthBook UI.
- **No experiment dashboards.** `dashboard-create` and `dashboard-edit` cover general Analytics dashboards. A dashboard attached to an experiment is edited on that experiment's page, and the per-experiment result blocks only render there.
- **No SDK code generation.** Follow GrowthBook's SDK docs; these skills manage flags and experiments via the REST API, not the SDK.
- **No bandit workflows yet.** GrowthBook's REST API supports multi-armed bandit experiments and separate Enterprise beta Contextual Bandits, but these skills currently target standard A/B tests. They identify either bandit type and halt rather than apply fixed-allocation experiment guidance to an adaptive experiment.
- **No silent retries or rate-limit backoff in the helper.** GrowthBook is rate-limited at 60 rpm. The skills that fan out cap their call counts; multi-tenant orgs hitting concurrent requests may still see `429`s, which `gb-call` surfaces explicitly rather than retrying.
## How it works
The plugin bundles a small Node helper (`scripts/gb-call`) that handles auth, API base URL, trusted app-origin resolution, and error reporting. Each of the four skill directories also contains a `scripts/gb-call` symlink so agents installed via `npx skills install` (Cursor, Codex, etc.) can resolve it relative to the skill directory. Skills call it via Bash:
```bash
gb-call GET /api/v2/features
echo '<payload>' | gb-call POST /api/v2/features -
gb-call app-origin
```
`gb-call` is shorthand in workflow examples. The domain router resolves it to `${CLAUDE_PLUGIN_ROOT}/scripts/gb-call` for the Claude Code plugin or `scripts/gb-call` relative to a standalone skill install; it does not need to be globally available on `PATH`. External agents call `app-origin` once per conversation when they first need a UI link and reuse that trusted origin across workflows.
See [`scripts/README.md`](scripts/README.md) for the full usage reference.
## Repository layout
```
.claude-plugin/
marketplace.json
plugin.json
scripts/
gb-call # Node REST helper (zero deps, Node 18+)
README.md # gb-call usage, config sources, error catalog
skills/
<domain>/
SKILL.md # router: description, workflow index, shared conventions
scripts/gb-call # symlink → ../../../scripts/gb-call (for npx-installed agents)
references/<workflow>.md # one workflow: steps, guardrails, endpoints, handoffs
feature-flags/
SKILL.md
references/
flag-create.md flag-search.md flag-graph.md
flag-toggle.md flag-targeting.md flag-rules.md flag-experiment.md
flag-schedule.md flag-ramp.md flag-monitoring.md flag-prerequisites.md
flag-default-value.md flag-metadata.md
flag-revisions.md flag-review.md flag-publish.md
flag-cleanup.md
experiments/
SKILL.md
references/
experiment-brainstorm.md experiment-design.md experiment-launch.md
experiment-analyze.md experiment-stop.md learnings.md
analytics/
SKILL.md
references/
metric-search.md metric-create.md analytics-explore.md
dashboard-create.md dashboard-edit.md
gb-setup/
SKILL.md # one-time onboarding; no references/
CLAUDE.md # authoring conventions for contributors
.gitignore
README.md
LICENSE
CHANGELOG.md
```
## Security & secrets
- **Where the key lives.** `gb-setup` writes `~/.config/growthbook/.env` inside a `0700` directory at file mode `0600` — owner-read/write only. Environment variables take precedence over the file, so CI and one-off overrides keep working.
- **Pasting a key into chat.** The value you give `gb-setup` lands in your local transcript and is sent to your configured model provider as part of the conversation; it cannot be retroactively masked. Generate a fresh PAT for the plugin rather than reusing your personal admin token — that way you can revoke it independently if anything goes wrong.
- **Revoking a leaked key.** Visit [`app.growthbook.io/account/personal-access-tokens`](https://app.growthbook.io/account/personal-access-tokens) (or your self-hosted equivalent) and revoke. Then re-run `/growthbook:gb-setup` with the replacement.
- **What the helper rejects.** `gb-call` refuses values containing whitespace or control characters (CRLF in `GB_API_KEY` would inject headers) and rejects malformed `GB_APP_URL` origins. `gb-setup` refuses `http://` URLs and URLs with a path, query, hash, or credentials.
## Contributing
Issues and PRs welcome at [github.com/growthbook/skills](https://github.com/growthbook/skills). For larger proposals (new skills, changes to skill scope), open an issue first.
Before changing a skill: read [`CLAUDE.md`](CLAUDE.md). It documents the skill structure, the `allowed-tools` security model, the "verify every payload shape against the GrowthBook back-end source before shipping" rule, and a doc cross-reference map for finding the canonical answer on any GrowthBook concept.
## License
MIT — see [LICENSE](LICENSE).
© GrowthBook · MIT · growthbook/skills