Best for
- Use when setting up the SDK, configuring a relay proxy, or adding flag test helpers.
laurigates/claude-plugins/configure-plugin/skills/configure-feature-flags/SKILL.md
Feature flags with OpenFeature and providers (GOFF, flagd, LaunchDarkly). Use when setting up the SDK, configuring a relay proxy, or adding flag test helpers.
Decision brief
Check and configure feature flag infrastructure using the OpenFeature standard with pluggable providers.
Compatibility matrix
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/laurigates/claude-plugins --skill "configure-plugin/skills/configure-feature-flags"Inspect the Agent Skill "configure-feature-flags" from https://github.com/laurigates/claude-plugins/blob/c056e44b978db58648ad20440dc1515cb09af09d/configure-plugin/skills/configure-feature-flags/SKILL.md at commit c056e44b978db58648ad20440dc1515cb09af09d. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
Check for existing feature flag infrastructure:
Check for complete feature flag setup:
Print a formatted compliance report:
Based on detected language, install and configure the OpenFeature SDK with the selected provider. Use code templates from REFERENCE.md.
Create flags.goff.yaml with example flags covering common patterns: - Simple boolean flag - Percentage rollout - Multi-variant flag (A/B test) - Environment-specific flag - User-specific override - Scheduled rollout
Permission review
The documentation asks the agent to create, modify, or delete local files.
Create test file using in-memory provider for feature flag unit tests.Evidence record
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 91/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 54 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Check and configure feature flag infrastructure using the OpenFeature standard with pluggable providers.
| Use this skill when... | Use another approach when... |
|---|---|
| Adding feature flag infrastructure to a new project | Creating or editing individual flag definitions in YAML |
| Setting up OpenFeature SDK with a provider (GOFF, flagd, LaunchDarkly) | Debugging why a specific flag evaluation returns unexpected values |
| Auditing existing feature flag configuration for completeness | Writing application logic that consumes feature flags |
| Configuring relay proxy infrastructure (Docker, Kubernetes) | Managing LaunchDarkly or Split dashboard settings |
| Adding feature flag test helpers and in-memory providers | Configuring error tracking (/configure:sentry instead) |
find . -maxdepth 1 -name \'package.json\'find . -maxdepth 1 -name \'pyproject.toml\'find . -maxdepth 1 -name \'go.mod\'find . -maxdepth 1 -name \'Cargo.toml\'find . -maxdepth 1 \( -name package.json -o -name pyproject.toml -o -name Cargo.toml -o -name go.mod \) -exec grep -l 'openfeature' {} +find . -maxdepth 2 -name 'flags.goff.yaml' -o -name 'flags.goff.yml'find . -maxdepth 1 -name 'docker-compose*.yml' -o -name 'docker-compose*.yaml'find . -maxdepth 1 -name \'.project-standards.yaml\'Parse from $ARGUMENTS:
--check-only: Report compliance status without modifications--fix: Apply all fixes automatically without prompting--provider <provider>: Override provider detection (goff, flagd, launchdarkly, split)CRITICAL: Before configuring feature flags, verify latest SDK and provider versions using WebSearch or WebFetch:
Execute this feature flag configuration workflow:
Check for existing feature flag infrastructure:
| Indicator | Language | Detected Provider |
|---|---|---|
@openfeature/server-sdk in package.json | Node.js | OpenFeature (check for provider) |
@openfeature/web-sdk in package.json | Browser JS | OpenFeature Web |
@openfeature/react-sdk in package.json | React | OpenFeature React |
openfeature-sdk in pyproject.toml | Python | OpenFeature Python |
@openfeature/go-feature-flag-provider | Node.js | GO Feature Flag |
go-feature-flag-relay-proxy in docker-compose | Any | GO Feature Flag Relay |
flagd in docker-compose/k8s | Any | flagd provider |
Check for complete feature flag setup:
Print a formatted compliance report:
Feature Flag Compliance Report
==============================
Project: [name]
Language: [detected]
Provider: [detected or None]
OpenFeature SDK: [status per check]
Provider Config: [status per check]
Infrastructure: [status per check]
Overall: [X issues found]
Recommendations: [list specific fixes]
If --check-only, stop here.
Based on detected language, install and configure the OpenFeature SDK with the selected provider. Use code templates from REFERENCE.md.
Create flags.goff.yaml with example flags covering common patterns:
Use flag templates from REFERENCE.md.
Create test file using in-memory provider for feature flag unit tests.
Update .project-standards.yaml:
components:
feature_flags: "2025.1"
feature_flags_sdk: "openfeature"
feature_flags_provider: "[goff|flagd|launchdarkly]"
Print a summary of all changes made including SDK installed, provider configured, flag file created, and next steps (start relay, initialize in app, use flags in code).
For detailed code templates, flag configuration patterns, and infrastructure manifests, see REFERENCE.md.
| Context | Command |
|---|---|
| Quick compliance check | /configure:feature-flags --check-only |
| Auto-fix with GOFF provider | /configure:feature-flags --fix --provider goff |
| Validate flag config | goff lint --file flags.goff.yaml |
| Check relay proxy health | `curl -s http://localhost:1031/health |
| List configured flags | `curl -s http://localhost:1031/v1/feature/flags |
| Check SDK installed (JS) | `jq -r '.dependencies |
| Flag | Description |
|---|---|
--check-only | Report status without offering fixes |
--fix | Apply all fixes automatically without prompting |
--provider <provider> | Override provider detection (goff, flagd, launchdarkly, split) |
# Check compliance and offer fixes
/configure:feature-flags
# Check only, no modifications
/configure:feature-flags --check-only
# Auto-fix with GO Feature Flag provider
/configure:feature-flags --fix --provider goff
# Configure for LaunchDarkly
/configure:feature-flags --fix --provider launchdarkly
goff lint before deployment/configure:all - Run all compliance checks/configure:sentry - Error tracking (often used with feature flags for rollback)Frequently asked questions
Check and configure feature flag infrastructure using the OpenFeature standard with pluggable providers.
The source record exposes this install command: npx skills add https://github.com/laurigates/claude-plugins --skill "configure-plugin/skills/configure-feature-flags". Inspect the command and pinned source before running it.
Static rules flagged write-files in the source; the page lists the matching lines and excerpts.
Alternatives
coreyhaines31/marketingskills
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program
alirezarezvani/claude-skills
App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklist
equinor/neqsim
Engineering deliverable quality — the nine analytical-depth moves (contributor ranking, adjudicating the source document, quantitative rule-outs, robustness crossover, conservatism direction, discriminating test), results.json schema, figure→discussion→linked_results traceability, evidence matrices, assumptions/gaps registers, citation conventions, KaTeX math formatting, units consistency, executive-summary structure, AACE class declaration. USE WHEN: producing a task report, a PEPR/M1/root-caus
JasonColapietro/suede-creator-skills
Suede-owned experimentation discipline for hypotheses, sample sizing, test duration, significance, and repeatable experiment programs. Use when comparing variants, deciding whether a result is reliable, or building an experiment backlog and cadence. NOT FOR: analytics instrumentation (use suede-analytics), post-click conversion diagnosis (use suede-site-alchemy), or writing the variant copy itself (use suede-copy).