Skill Claude CodeCodex
Export Spotify Ads API campaign data to CSV — full campaign hierarchies with ad sets, ads, targeting, budgets, and performance metrics for offline review, campaign analysis, or budget reconciliation.
Skill Claude CodeCodex
Diagnose existing Spotify Ads Pixel, Conversions API (CAPI), and dataset implementations when events are missing, stale, duplicated, unexpectedly high or low, not deduplicated, attached to the wrong account, or present in diagnostics but absent from campaign reporting. Use for Pixel/CAPI troubleshooting…
Skill Claude CodeCodex
Plan and configure Spotify Ads conversion measurement with Spotify Pixel, direct or Google Tag Manager-based Conversions API (CAPI), datasets, advanced matching, mobile apps, event mapping, parameters, ad-account sharing, and CAPI credentials. Use when a user asks to design or implement measurement, install Pixel…
Skill Claude CodeCodex
Check Spotify Ads API campaign health — pacing, delivery issues, budget burn rate, stalled campaigns, and underpacing alerts. Use for one-shot health checks or recurring monitoring when the host supports scheduled automations.
Skill Claude CodeCodex
Pull Spotify Ads API reporting data — aggregate metrics, audience insights, or async CSV reports.
Plugin Claude Code
Plugin marketplace listing 1 plugin: confidence.
Plugin Claude Code
Access Confidence feature flags, experiments, and migration tools directly from Claude Code.
MCP server Claude CodeCodexCursor +2
MCP server "confidence-flags", hosted remotely at mcp.confidence.dev, as configured in spotify/confidence-ai-plugins.
MCP server Claude CodeCodexCursor +2
MCP server "confidence-docs", hosted remotely at mcp.confidence.dev, as configured in spotify/confidence-ai-plugins.
Instructions file
Instructions for spotify/confidence-ai-plugins, covering confidence plugin, commands, skills and mcp servers.
Instructions file Gemini CLI
Instructions for spotify/confidence-ai-plugins, covering confidence extension, available tool categories and guidelines.
Command
Analyze a project and propose feature flag changes using Confidence.
Command
Explore and preview metrics for any event or fact table.
Command
Analyze a project and instrument event tracking with Confidence.
Command
Migrate feature flags from Eppo to Confidence.
Command
/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.
Command
/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.
Command
/migrate-optimizely adjust flags — Phase 1: fine-edit the flag plan (scope, Migrate/Skip, client, bucketing, schema, rules). Plan file only — no createFlag.
Command
/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).
Command
/migrate-optimizely execute code — transform Optimizely SDK code from the Phase 2 code plan. Finds the plan file; no path argument needed.
Command
/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.
Command
/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).
Command
/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.
Command
/migrate-optimizely plan flags — Phase 1: scan Optimizely flags and write a flag migration plan. No createFlag. Same split as plan access.