Feature Toggle Manager

Feature flag management. Creates and toggles feature flags for A/B testing. Triggers: feature flag, a b test, toggle feature, abtesting.

Security Scan

Internally consistent documentation-only skill for feature-flag guidance; it does not request credentials, install code, or perform any actions.

Purpose & Capability

Name and description match the content of SKILL.md (feature flag guidance). The skill does not request unrelated binaries, env vars, or config paths—everything requested (nothing) is proportionate to a documentation/help skill.

Instruction Scope

SKILL.md contains conceptual code snippets, rollout strategies, and best practices only. It does not instruct the agent to read files, call external endpoints, or access environment variables. There is no scope creep.

Install Mechanism

No install spec and no code files. This is the lowest-risk model (instruction-only); nothing will be downloaded or written to disk by the skill itself.

Credentials

Skill declares no required environment variables, credentials, or config paths. No sensitive data is requested or implied by the instructions.

Persistence & Privilege

always is false and model invocation is not disabled (normal defaults). The skill does not request elevated persistence or modify other skills/configurations.

Assessment

This skill is documentation-only: it provides patterns, a sample feature-check snippet, and rollout advice but contains no implementation or integrations. It cannot access your system or cloud by itself. If you expect a working feature-flag service, you'll need to connect or implement an actual provider (e.g., LaunchDarkly, Unleash) and supply appropriate credentials/env vars; review those integrations separately before granting any secrets. If you plan to let an agent act autonomously, add explicit checks and limits in the implementation to avoid accidental wide rollouts.

Feature Flag Manager

Overview

Implements feature flags for controlled rollouts and A/B testing.

When to Use

• User asks to "add a feature flag"
• User wants to "A/B test" or "gradually roll out"

Implementation

if (isFeatureEnabled("new_checkout_flow", userId)) { renderNewCheckout(); } else { renderLegacyCheckout(); }

Rollout Strategy

1-5% = internal users 10-25% = beta users 25-50% = canary 100% = full rollout

Monitor: error rate, conversion, latency

Anti-Patterns

• Do not use flags for permanent features
• Limit active flags to under 20
• Clean up flags after rollout