feature-flagging

Operational discipline for feature flags as production infrastructure. Flag types, naming, targeting rules, rollout strategy, lifecycle, governance, stale flag management, and the technical debt patterns that bite teams who weren't deliberate about it.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/feature-flagging/SKILL.md

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-structured playbook with clear workflows and excellent progressive disclosure that points to a complete, real reference bundle. Its main weakness is mild verbosity in the intro and closing sections that could be tightened to better respect the token budget.

Suggestions

Tighten the 'Closing: when to remove a flag' section by dropping the analogies to deploys and post-mortems; the cost/compounding point already stands on its own.

Trim the opening paragraph that restates what feature flags are and what they 'enable' — Claude already knows this, so lead directly with the operational discipline framing.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and assumes competence, but the opening restates what feature flags are and the 'Closing' section is padded with philosophical justification ('It is the same discipline behind cleaning up after a deploy...') that could be trimmed.	2 / 3
Actionability	As an instruction-only skill it gives concrete, specific guidance: ramp steps (1→10→25→50→100%), a 5 ms latency budget for fifty flags, <60 s flip targets, naming patterns with examples, and a 5-step cleanup playbook — actionable without code.	3 / 3
Workflow Clarity	Multi-step processes are explicitly sequenced with validation checkpoints: the five lifecycle phases have entry/exit criteria, rollouts use a 'ramp and watch' peak-hour monitoring gate, and stale-flag cleanup is a numbered PR-per-flag process.	3 / 3
Progressive Disclosure	The body is a clear overview with well-signaled, one-level-deep references; every inline link and the 'Reference files' section maps to a real file in references/ (all seven present), so detail is appropriately split.	3 / 3
	Total	11 / 12 Passed

Description

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, well-scoped description that distinguishes the skill clearly, but it omits an explicit 'when to use it' trigger clause and only partially covers the natural vocabulary users would actually say. Adding a 'Use when...' sentence with everyday trigger terms would raise completeness and trigger-term quality.

Suggestions

Append a 'Use when...' trigger clause naming everyday terms users would say, e.g. 'Use when introducing, modifying, or auditing feature flags, kill switches, toggles, or gradual rollouts.'

Broaden trigger vocabulary to include natural variations like 'toggle', 'kill switch', 'dark launch', and 'A/B test' alongside 'feature flags' and 'rollout'.

Dimension	Reasoning	Score
Specificity	The description enumerates many concrete capabilities — 'Flag types, naming, targeting rules, rollout strategy, lifecycle, governance, stale flag management' — matching the anchor that lists multiple specific concrete actions.	3 / 3
Completeness	It clearly answers 'what' the skill does but lacks a 'Use when...' clause or equivalent explicit 'when to use it' trigger, which the guidelines cap at 2.	2 / 3
Trigger Term Quality	It contains the core term 'feature flags' and 'rollout', but misses common natural variations users would say ('toggle', 'kill switch', 'A/B test') and offers no explicit trigger guidance.	2 / 3
Distinctiveness Conflict Risk	'Operational discipline for feature flags as production infrastructure' carves a clear niche, distinct from the related experiment-design and experimentation-analytics skills, unlikely to trigger the wrong skill.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: rampstackco/claude-skills
Path: skills/feature-flagging/SKILL.md
Commit: bc6d961

Reviewed: about 6 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.