Name: Feature Flags
Availability: InStock
Author: christopherlouet

Install

$ agentstack add skill-christopherlouet-claude-base-feature-flags

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

✓ Prompt-injection patterns
✓ Secret / credential exfiltration
✓ Dangerous shell & filesystem operations
✓ Untrusted network calls
✓ Known-malicious package signatures

What it can access

✓ Network access No
✓ Filesystem access No
✓ Shell / process execution No
✓ Environment & secrets No
✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

Links to your public security report.

[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-christopherlouet-claude-base-feature-flags)

Reliability & compatibility

✓ Security review passed

0 installs to date

— no reviews yet

● 2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →

About

Feature Flags (pointer)

SDK code, targeting rules syntax and dashboard integration drift on each vendor release and are canonical at:

LaunchDarkly — launchdarkly.com/docs (SaaS, advanced targeting + experimentation)
Unleash — docs.getunleash.io (self-hosted open source)
ConfigCat — configcat.com/docs (SaaS, generous free tier)
PostHog Feature Flags — posthog.com/docs/feature-flags (paired with product analytics; see also recipe)
OpenFeature — openfeature.dev (vendor-neutral SDK standard — use to avoid lock-in)

Use-case taxonomy (version-agnostic)

| Type | Purpose | Lifetime | |---|---|---| | Release toggle | Deploy inactive code; flip on after smoke test | Short (days/weeks) | | Experiment toggle | A/B test; emits exposure events for analysis | Bounded by experiment duration | | Ops toggle | Circuit breakers, kill switches, degraded modes | Long-lived | | Permission toggle | Feature gating by role/plan/cohort | Permanent (treat like config) |

Choose by lifetime: short → cheap implementation, long-lived → invest in observability + naming discipline.

Foundation discipline (keep across releases)

Default OFF: every flag defaults to its conservative value (usually off). A flag that ships defaulting to ON is a hidden behaviour change.
2-sprint rule: remove release toggles within 2 sprints of full rollout. Stale flags accrue as tech debt — surface them via qa-tech-debt.
Log every evaluation: missing evaluation logs make debugging "why did user X see variant Y" impossible. Vendor SDKs offer this; if rolling custom, log it.
No business logic in flag values: a flag is a boolean (or enum); complex conditions belong in code paths the flag selects, not inside the flag service.
Naming convention: __ (e.g. checkout_express_enabled). Scope-first sorts/filters cleanly in dashboards.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Author: christopherlouet
Source: christopherlouet/claude-base
License: MIT
Homepage: https://christopherlouet.github.io/claude-base/

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

v0.1.0 Imported from the upstream source.