Flaggr ships agent skills — packaged instructions that teach coding agents (Claude Code, Devin, Cursor, and any agent that reads SKILL.md conventions) how to drive flaggr.dev correctly: evaluation, toggles, rollout safety, and SDK wiring.

Install with npx

# Auto-detects .agents/skills, .claude/skills, or .devin/skills in your project
npx @flaggr/skills
 
# Install globally — available in every project
npx @flaggr/skills --global
 
# Explicit target directory
npx @flaggr/skills --target .claude/skills

Preview first: npx @flaggr/skills --list and --dry-run.

Claude Code plugin marketplace

The Flaggr repo is a Claude Code plugin marketplace — one command installs the skills and wires the MCP server:

/plugin marketplace add flaggr/flaggr
/plugin install flaggr

The bundled plugin registers @flaggr/mcp-server via npx — set FLAGGR_API_TOKEN in your environment (or let the MCP login tool handle auth interactively).

Bundled skills

flaggr

Core operations — the default skill agents load when you mention flags:

• Evaluation (evaluate_flag, POST /api/flags/evaluate, batch eval)
• Flag CRUD and toggles (toggle_flag, bulk_toggle_flags)
• Health and safety (get_flag_health, check_and_rollback_flag, toggle-impact analysis)
• Auth — token minting, Bearer scopes, public-flag evaluation
• REST quick reference with fields, ETag, and summary params

flaggr-rollouts

Progressive delivery workflows — activated when you ask for rollouts, canaries, or kill switches:

• start_canary_rollout — staged ramps with health gating and minimum soak
• check_and_rollback_flag — circuit-breaker rollback on error/latency drift
• simulate_flag_targeting — blast-radius estimation before changing rules
• Cohorts, overrides, scheduled rules, bandit experiments

flaggr-openfeature

SDK integration — activated when wiring Flaggr into application code:

• FlaggrWebProvider / Go SDK setup with stream / batch / poll update modes
• OFREP endpoint for vendor-neutral OpenFeature clients
• Transport selection — when to use REST eval vs SSE push vs Connect-RPC

Authentication

Skills assume a fgr_ API token — mint one at console → profile, project settings, or POST /api/projects/{id}/tokens. For read-only exploration, the public pixel-grid demo service works with no token at all — try it in the API explorer.

See also

• MCP server guide — the underlying tool surface
• API explorer — live Try-It for every endpoint
• Authentication — token types and scopes