CtrlK
BlogDocsLog inGet started
Tessl Logo

feature-flags-architect

Use when adding, retiring, or auditing feature flags. Triggers on "add a flag", "ship behind a flag", "rollout plan", "kill switch", "stale flags", "flag debt", "LaunchDarkly", "GrowthBook", "Statsig", "Unleash", "Flipt", or any progressive-delivery question. Ships flag debt scanner, rollout planner, and kill-switch auditor (all stdlib Python), 4 references on flag taxonomy + provider trade-offs + rollout strategies + lifecycle, plus a /flag-cleanup slash command.

74

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is feature-flags-architect in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

93%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.

An excellent, well-structured skill body: lean tables, executable commands, four sequenced workflows with validation gates, and a clean one-level-deep bundle layout whose files all exist. The single gap is that error-recovery loops (what to do when an audit fails) are implied rather than explicit.

DimensionReasoningScore

Conciseness

The body is dense and purposeful: taxonomy and provider tables, copy-paste commands, terse bullets, and an anti-patterns list. It explains only skill-specific knowledge (cleanup triggers, provider lock-in trade-offs) and nothing Claude already knows, matching the lean anchor 5.

5 / 5

Actionability

Quick start gives three copy-paste-ready commands; each tool section shows invocations with real flag values and enumerated strategies with defaults ("ring ... Default for risky launches"). Commands are fully executable, covering the common cases.

5 / 5

Workflow Clarity

All four workflows are numbered with validation gates ("Run kill_switch_audit.py — must pass before merge", "Deploy at 0%; verify kill switch works", "should now show one fewer flag"). Falls short of anchor 5 because the fix-and-re-run feedback loop on validation failure is implied by "must pass" rather than explicitly stated as a validate→fix→retry loop.

4 / 5

Progressive Disclosure

All 4 references, 3 scripts, and 1 asset cited in the body exist in the bundle and are one level deep (reference files point back to bundle scripts/assets, not to further content). The References section signals each file with a one-line description, and detail is appropriately pushed out of SKILL.md.

5 / 5

Total

19

/

20

Passed

Description

92%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.

A strong description: it states explicit use-when triggers, lists the concrete capabilities (scanner, planner, auditor), and anchors the niche with provider names. Its only weakness is minor trigger-synonym coverage (e.g., "feature toggle") and a slight inventory flavor in the trailing sentence about references and the slash command.

DimensionReasoningScore

Specificity

"adding, retiring, or auditing feature flags" plus "flag debt scanner, rollout planner, and kill-switch auditor" names multiple concrete actions spanning the full flag lifecycle (create, ramp, kill, retire). Fits anchor 5 rather than 4 because coverage is comprehensive across the domain, not just several actions with gaps.

5 / 5

Completeness

Explicitly answers "when" via "Use when adding, retiring, or auditing feature flags. Triggers on ..." with concrete trigger phrases, and "what" via the three bundled stdlib Python tools. Both halves are explicit, matching the anchor-5 example structure.

5 / 5

Trigger Term Quality

Explicit trigger phrases ("add a flag", "rollout plan", "kill switch", "stale flags", "flag debt") plus all five provider names (LaunchDarkly, GrowthBook, Statsig, Unleash, Flipt) give strong natural-term coverage. Not anchor 5 because common synonyms like "feature toggle" or "A/B test flag" are missing.

4 / 5

Distinctiveness Conflict Risk

A clear feature-flag/progressive-delivery niche with distinct triggers (provider names, "kill switch", "flag debt") that no adjacent skill would claim. Minimal conflict risk with generic rollout or CI skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
alirezarezvani/claude-skills
Reviewed

Table of Contents

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.