Skylv Feature Flag

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

Security Scan

This skill is a small, instruction-only guide for feature-flag best practices and does not request credentials, install software, or perform actions — it is internally consistent with its stated purpose.

Purpose & Capability

Name and description promise feature-flag management; the SKILL.md contains implementation guidance, a code snippet, rollout percentages, and monitoring suggestions. The skill does not claim to integrate with any external service, and it does not request credentials or tools, so the requested footprint is appropriate for a documentation-style helper. Note: it is advisory only and does not actually create or toggle flags.

Instruction Scope

Instructions are high-level guidance and a sample snippet (isFeatureEnabled / renderNewCheckout). They do not instruct the agent to read files, access environment variables, call external endpoints, or transmit data. There is no scope creep in the runtime instructions.

Install Mechanism

No install spec and no code files — lowest-risk category. Nothing is downloaded or written to disk.

Credentials

The skill requests no environment variables or credentials. That's proportionate for a documentation/instruction-only skill. Be aware that any real integration with a feature-flag service would require separate credentials not included here.

Persistence & Privilege

always is false and the skill is user-invocable. It does not request permanent presence or modify other skills or system-wide settings.

Assessment

This is an advisory, instruction-only skill that provides best practices and a sample code snippet for feature flags — it will not actually create or toggle flags or access your systems. It's safe to install from a security footprint perspective, but: (1) if you expect automated flag management, ask for a concrete implementation or connectors (which will need credentials); (2) verify the author/source if you plan to rely on it operationally; and (3) do not supply any secrets to this skill as it currently does not need them.

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