Confidence
Access Confidence feature flags, experiments, and migration tools directly from Claude Code.
Skills (15)
Claude uses these on its own when your request matches.
- analyze-projectAnalyze a user's project and propose a meaningful feature flag change using Confidence. Use when the user says /analyze-project, asks what to flag, wants flag suggestions, or asks "what should I feature-flag in my project?
- explore-metricExplore and preview metrics for any event or fact table. Generates a pre-filled Metric Explorer URL with fact table, entity, exposure table, metric kind, and aggregation — so the user can click through to the UI, hit Calculate, and create the metric. Use when the user asks to…
- instrument-eventsAnalyze a project's codebase, identify what events to track alongside the metrics they'd power, create event definitions in Confidence with entity references (so fact tables are auto-created), add SDK track() calls, and verify the pipeline. Use when the user asks to instrument…
- migrate-eppoMigrate feature flags from Eppo to Confidence SDK. Use when the user says /migrate-eppo, asks to migrate Eppo flags, or transform SDK code to Confidence.
- migrate-optimizelyMigrate Optimizely to Confidence — users/groups/roles/policies, Flag clients from env SDK keys, flag definitions, and OpenFeature code. Bare /migrate-optimizely (no args) starts plan access. Use when the user says /migrate-optimizely, /migrate-optimizely-plan-access,…
- migrate-posthogMigrate feature flags from PostHog to Confidence SDK. Use when the user says /migrate-posthog, asks to migrate PostHog flags, or transform SDK code to Confidence.
- migrate-statsigMigrate feature flags from Statsig to Confidence SDK. Use when the user says /migrate-statsig, asks to migrate Statsig gates/configs/experiments, or transform SDK code to Confidence.
- onboard-confidence-dry-runDry-run the Confidence onboarding flow to test UX without real API calls. Use when the user says "dry run", "test onboarding", "demo onboarding", or wants to preview the onboarding experience.
- onboard-confidenceCreate Confidence accounts and onboard users. Use when the user asks to create an account, invite users, onboard to Confidence, or check account status.
- setup-session-recordingSet up Confidence Session Recording in a browser-based project. Use when the user asks to add session recording, session replay, set up session recordings, or integrate Confidence recordings into their app.
- setup-warehouse-bigquerySet up BigQuery as a data warehouse for Confidence. Use when the user chose BigQuery for warehouse setup.
- setup-warehouse-databricksSet up Databricks as a data warehouse for Confidence. Use when the user chose Databricks for warehouse setup.
- setup-warehouse-redshiftSet up Redshift as a data warehouse for Confidence. Use when the user chose Redshift for warehouse setup.
- setup-warehouse-snowflakeSet up Snowflake as a data warehouse for Confidence. Use when the user chose Snowflake for warehouse setup.
- setup-warehouseSet up a data warehouse for Confidence experimentation analytics. Use when the user asks to connect a warehouse, set up BigQuery/Snowflake/Databricks/Redshift, or configure data connectors.
MCP servers (2)
Added to Claude Code when you install the plugin. You sign in to Confidence the first time it is used.
- confidence-flagsRemote
https://mcp.confidence.dev/mcp/flags - confidence-docsRemote
https://mcp.confidence.dev/mcp/docs
Commands (18)
Shortcuts you type in Claude Code.
- /analyze-projectAnalyze a project and propose feature flag changes using Confidence
- /explore-metricExplore and preview metrics for any event or fact table
- /instrument-eventsAnalyze a project and instrument event tracking with Confidence
- /migrate-eppoMigrate feature flags from Eppo to Confidence
- /migrate-optimizely-adjust-access/migrate-optimizely adjust access — Phase 0: fine-edit the access plan (users, groups, roles, policies, clients). Plan file only — no invites, no IAM writes, no POST /v1/clients.
- /migrate-optimizely-adjust-code/migrate-optimizely adjust code — Phase 2: fine-edit the code plan (style, resolve mode, transforms, files/flags). Plan file only — no source edits, no PRs.
- /migrate-optimizely-adjust-flags/migrate-optimizely adjust flags — Phase 1: fine-edit the flag plan (scope, Migrate/Skip, client, bucketing, schema, rules). Plan file only — no createFlag.
- /migrate-optimizely-execute-access/migrate-optimizely execute access — invite users, create groups, and as soon as each person accepts: put them in the right group, policy, Flag client, and share that group’s flags (Viewer/Editor by role)
- /migrate-optimizely-execute-code/migrate-optimizely execute code — transform Optimizely SDK code from the Phase 2 code plan. Finds the plan file; no path argument needed.
- /migrate-optimizely-execute-flags/migrate-optimizely execute flags — create Confidence flags from the Phase 1 flag plan. Ends with a full resolve gate (every migrated flag). Finds the plan file; no path argument needed.
- /migrate-optimizely-plan-access/migrate-optimizely plan access — Phase 0: map Optimizely users, teams, roles, and Flag-client candidates. Writes a plan file only (no invites, no IAM writes, no POST /v1/clients).
- /migrate-optimizely-plan-code/migrate-optimizely plan code — Phase 2: scan Optimizely SDK usage and write a code migration plan. No file edits. Same split as plan access / plan flags.
- /migrate-optimizely-plan-flags/migrate-optimizely plan flags — Phase 1: scan Optimizely flags and write a flag migration plan. No createFlag. Same split as plan access.
- /migrate-optimizelyMigrate Optimizely to Confidence. No args (or empty) = start from the beginning with plan access. Also: plan/adjust/execute access (Flag clients are Step 4 of plan access), plan/adjust/execute flags, plan/adjust/execute code. Prefer the dedicated / menu items for a specific…
- /migrate-posthogMigrate feature flags from PostHog to Confidence
- /migrate-statsigMigrate feature flags from Statsig to Confidence
- /onboard-confidenceCreate Confidence accounts and onboard users
- /setup-session-recordingSet up Confidence Session Recording in a browser-based project
Install
Run in your terminal
claude plugin install confidence@claude-plugins-officialClaude Code already includes the claude-plugins-official marketplace, so this installs directly. Start a new Claude Code session to use it.
Already in a Claude Code session?
Install
/plugin install confidence@claude-plugins-officialPublished in Anthropic's claude-plugins-official marketplace (anthropics/claude-plugins-official).
Related plugins
- 1FFrontend DesignCreate distinctive, production-grade frontend interfaces with high design quality. Generates creative, polished code that avoids generic AI aesthetics.1.1Mmarketplace installs
- 2SSuperpowersSuperpowers teaches Claude brainstorming, subagent driven development with built in code review, systematic debugging, and red/green TDD. Additionally, it teaches Claude how to author and test new skills.1Mmarketplace installs
- 3
Context7Upstash Context7 MCP server for up-to-date documentation lookup. Connects to Context7's hosted remote MCP server (https://mcp.context7.com/mcp) — no local Node.js or npx required — to pull version-specific documentation and code examples directly from source repositories into your LLM context. Works anonymously out of the box; set CONTEXT7_API_KEY for higher rate limits.418kmarketplace installs
- 4FFeature DevComprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review256kmarketplace installs
- 5TTypeScript LSPTypeScript/JavaScript language server for enhanced code intelligence213kmarketplace installs
- 6RRalph LoopInteractive self-referential AI loops for iterative development, implementing the Ralph Wiggum technique. Claude works on the same task repeatedly, seeing its previous work, until completion.197kmarketplace installs