Source profileQuality 91/100

laurigates/claude-plugins/configure-plugin/skills/configure-feature-flags/SKILL.md

configure-feature-flags

Feature flags with OpenFeature and providers (GOFF, flagd, LaunchDarkly). Use when setting up the SDK, configuring a relay proxy, or adding flag test helpers.

Source repository stars
54
Declared platforms
0
Static risk flags
1
Last source update
2026-08-28
Source checked
2026-08-28

Decision brief

What it does: where it fits

Check and configure feature flag infrastructure using the OpenFeature standard with pluggable providers.

Best for

  • Use when setting up the SDK, configuring a relay proxy, or adding flag test helpers.

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/laurigates/claude-plugins --skill "configure-plugin/skills/configure-feature-flags"
Safe inspection promptEditorial

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

What the source asks the agent to do

  1. 01

    Step 1: Detect project language and existing setup

    Check for existing feature flag infrastructure:

    Check for existing feature flag infrastructure:
  2. 02

    Step 2: Analyze current state

    Check for complete feature flag setup:

    Verify OpenFeature SDK installed for project languageCheck provider package installedVerify provider initialized in application startup
  3. 03

    Step 3: Generate compliance report

    Print a formatted compliance report:

    Print a formatted compliance report:If --check-only, stop here.
  4. 04

    Step 4: Install SDK and configure provider (if --fix or user confirms)

    Based on detected language, install and configure the OpenFeature SDK with the selected provider. Use code templates from REFERENCE.md.

    Install OpenFeature SDK and provider packagesCreate feature flag client wrapper moduleCreate evaluation context helper
  5. 05

    Step 5: Create flag configuration

    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

    Simple boolean flagPercentage rolloutMulti-variant flag (A/B test)

Permission review

Static risk signals and limitations

Writes files

medium · line 123

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

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score91/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars54SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
laurigates/claude-plugins
Skill path
configure-plugin/skills/configure-feature-flags/SKILL.md
Commit
c056e44b978db58648ad20440dc1515cb09af09d
License
MIT
Collected
2026-08-28
Default branch
main
View the original SKILL.md

/configure:feature-flags

Check and configure feature flag infrastructure using the OpenFeature standard with pluggable providers.

When to Use This Skill

Use this skill when...Use another approach when...
Adding feature flag infrastructure to a new projectCreating 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 completenessWriting 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 providersConfiguring error tracking (/configure:sentry instead)

Context

  • Package JSON: !find . -maxdepth 1 -name \'package.json\'
  • Python project: !find . -maxdepth 1 -name \'pyproject.toml\'
  • Go project: !find . -maxdepth 1 -name \'go.mod\'
  • Cargo project: !find . -maxdepth 1 -name \'Cargo.toml\'
  • OpenFeature SDK: !find . -maxdepth 1 \( -name package.json -o -name pyproject.toml -o -name Cargo.toml -o -name go.mod \) -exec grep -l 'openfeature' {} +
  • GOFF config: !find . -maxdepth 2 -name 'flags.goff.yaml' -o -name 'flags.goff.yml'
  • Docker compose: !find . -maxdepth 1 -name 'docker-compose*.yml' -o -name 'docker-compose*.yaml'
  • Project standards: !find . -maxdepth 1 -name \'.project-standards.yaml\'

Parameters

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)

Version Checking

CRITICAL: Before configuring feature flags, verify latest SDK and provider versions using WebSearch or WebFetch:

  1. OpenFeature JS SDK: Check npm
  2. OpenFeature Python SDK: Check PyPI
  3. GO Feature Flag: Check GitHub releases
  4. flagd: Check GitHub releases

Execution

Execute this feature flag configuration workflow:

Step 1: Detect project language and existing setup

Check for existing feature flag infrastructure:

IndicatorLanguageDetected Provider
@openfeature/server-sdk in package.jsonNode.jsOpenFeature (check for provider)
@openfeature/web-sdk in package.jsonBrowser JSOpenFeature Web
@openfeature/react-sdk in package.jsonReactOpenFeature React
openfeature-sdk in pyproject.tomlPythonOpenFeature Python
@openfeature/go-feature-flag-providerNode.jsGO Feature Flag
go-feature-flag-relay-proxy in docker-composeAnyGO Feature Flag Relay
flagd in docker-compose/k8sAnyflagd provider

Step 2: Analyze current state

Check for complete feature flag setup:

  1. Verify OpenFeature SDK installed for project language
  2. Check provider package installed
  3. Verify provider initialized in application startup
  4. Check evaluation context configuration
  5. Check hooks configured (logging, telemetry)
  6. For GOFF: verify flag configuration file exists, relay proxy configured
  7. For flagd: verify container/service configured, gRPC/HTTP endpoints

Step 3: Generate compliance report

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.

Step 4: Install SDK and configure provider (if --fix or user confirms)

Based on detected language, install and configure the OpenFeature SDK with the selected provider. Use code templates from REFERENCE.md.

  1. Install OpenFeature SDK and provider packages
  2. Create feature flag client wrapper module
  3. Create evaluation context helper
  4. Create middleware for HTTP frameworks (Express, FastAPI, etc.)

Step 5: Create flag configuration

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

Use flag templates from REFERENCE.md.

Step 6: Configure infrastructure

  1. Create docker-compose entry for relay proxy (local development)
  2. Optionally create Kubernetes manifests for production

Step 7: Create test configuration

Create test file using in-memory provider for feature flag unit tests.

Step 8: Update standards tracking

Update .project-standards.yaml:

components:
  feature_flags: "2025.1"
  feature_flags_sdk: "openfeature"
  feature_flags_provider: "[goff|flagd|launchdarkly]"

Step 9: Print completion report

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.

Agentic Optimizations

ContextCommand
Quick compliance check/configure:feature-flags --check-only
Auto-fix with GOFF provider/configure:feature-flags --fix --provider goff
Validate flag configgoff 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

Flags

FlagDescription
--check-onlyReport status without offering fixes
--fixApply all fixes automatically without prompting
--provider <provider>Override provider detection (goff, flagd, launchdarkly, split)

Examples

# 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

Error Handling

  • No package manager found: Cannot install SDK, provide manual steps
  • Provider not supported: List supported providers, suggest alternatives
  • Relay proxy unreachable: Check Docker/K8s configuration
  • Invalid flag syntax: Validate with goff lint before deployment

See Also

Frequently asked questions

What to verify before installation and use

What does the configure-feature-flags source document cover?

Check and configure feature flag infrastructure using the OpenFeature standard with pluggable providers.

How do I install configure-feature-flags?

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.

Which permission-related actions were detected?

Static rules flagged write-files in the source; the page lists the matching lines and excerpts.

Alternatives

Compare before choosing

Computed 10045,960

coreyhaines31/marketingskills

ab-testing

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

Computed 10025,136

alirezarezvani/claude-skills

app-store-optimization

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

Computed 100147

equinor/neqsim

neqsim-professional-reporting

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

Computed 100133

JasonColapietro/suede-creator-skills

suede-ab-testing

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).