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

70%

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

71%Weight 40%Scale 1-5

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

The body is a well-structured operational playbook with concrete, actionable prescriptions and excellent progressive disclosure to 7 real reference files, dragged down only by moderate rhetorical verbosity and some restatement between the framework section and earlier content.

Suggestions

Trim the rhetorical framing in the intro and the 'Closing: when to remove a flag' section, and either cut or sharply condense the '14 considerations' framework since it restates points already made in the section bodies.

Add one short executable snippet (e.g., a pseudocode bulk-evaluation or flag-evaluation call) so the performance and testing sections have a concrete code anchor rather than only prose.

Make the rollout abort/rollback checkpoint an explicit numbered step ('If error rate or latency regresses at any step, roll back to the previous percentage before re-evaluating') to close the validation gap.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with high-value non-obvious specifics (e.g., '5 ms total budget for fifty flag checks', '30 days for release flags'), but the rhetorical intro/closing and the '14 considerations' framework that restates earlier sections add padding that could be tightened, keeping it at the 3 anchor.	3 / 5
Actionability	Concrete, directly applicable prescriptions abound — the naming format '<type>_<owner>_<semantic_name>_<version_or_date>', the 1/5/10/25/50/100 ramp schedule, the Viewer/Editor/Approver/Admin tiers, and the 5-step cleanup playbook — but platform-specific executable code/commands are explicitly deferred to platform docs, a minor gap that stops it at 4.	4 / 5
Workflow Clarity	Multi-step processes are clearly sequenced — the stale-flag cleanup is a 5-step playbook with PR-review and merge-before-delete validation gates, and rollout has 'watch one peak hour before advancing' checkpoints — with only minor implicit validation gaps in the rollout abort path.	4 / 5
Progressive Disclosure	A clear overview body with well-signaled one-level-deep references (e.g., 'For deeper coverage... see [`references/flag-naming-conventions.md`]' and a dedicated 'Reference files' section) all mapping to real files in ./references/, giving easy navigation and appropriate content split.	5 / 5
	Total	16 / 20 Passed

Description

70%Weight 40%Scale 1-5

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

The description is specific and distinctive, naming a comprehensive set of feature-flag operational capabilities, but it lacks an explicit 'Use when...' trigger clause, which caps its completeness at 3 and slightly limits trigger-term coverage.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when introducing, modifying, or auditing feature flags, or designing flag governance') to surface trigger phrases and lift completeness.

Include natural synonyms users say — 'feature toggles', 'kill switches', 'A/B test flags' — to broaden trigger-term coverage.

Reframe the topic enumeration with a few verb-actions (e.g., 'Define flag types, enforce naming, design targeting rules, plan rollouts') to nudge specificity toward 5.

Dimension	Reasoning	Score
Specificity	The phrase 'Flag types, naming, targeting rules, rollout strategy, lifecycle, governance, stale flag management' lists several specific concrete capabilities with comprehensive coverage, though framed as topics/nouns rather than verb-actions, leaving it just below the 5 anchor.	4 / 5
Completeness	It clearly states what the skill covers ('Operational discipline for feature flags as production infrastructure' plus the topic enumeration) but has no 'Use when...' clause or equivalent explicit trigger guidance in the description, capping completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Natural terms like 'feature flags', 'targeting rules', 'rollout strategy', and 'stale flag management' give good keyword coverage, but common synonyms such as 'feature toggle', 'kill switch', and 'A/B test flags' are absent, stopping short of the 5 anchor.	4 / 5
Distinctiveness Conflict Risk	'Feature flags as production infrastructure' with flag-specific terminology (flag types, targeting rules, stale flag management) carves a clear niche with distinct triggers and minimal conflict risk with adjacent skills.	5 / 5
	Total	16 / 20 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: 0479242

Reviewed: 6 days 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.