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.

76

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

The risk profile of this skill

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, actionable skill body with executable commands, sequenced validation-gated workflows, and clean one-level references to real bundle files. The only weakness is light framing prose that slightly inflates the token budget.

Suggestions

Tighten the intro and 'Core principle' framing (e.g. 'Most teams treat flags as throwaway if-statements') to pure operational guidance — the lifecycle diagram already conveys the point.

The 'Anti-patterns' section overlaps conceptually with the taxonomy table; consider folding the most critical anti-pattern into the relevant reference rather than restating in the overview.

DimensionReasoningScore

Conciseness

Mostly lean and executable with tables and code blocks doing the work, but framing prose like "Most teams treat flags as throwaway if-statements; this skill treats them as a controlled lifecycle with measurable debt" is mild over-explanation that could be trimmed.

4 / 5

Actionability

Fully executable, copy-paste-ready commands with concrete args (e.g. `python scripts/rollout_planner.py --population 100000 --target-percent 100 --duration-days 14 --strategy ring`) covering the common cases for all three tools.

5 / 5

Workflow Clarity

Four numbered workflows with explicit validation checkpoints — "Run kill_switch_audit.py — must pass before merge", "Test the kill switch in staging BEFORE production rollout", and abort criteria — plus a feedback loop where audit failure blocks merge.

5 / 5

Progressive Disclosure

SKILL.md is a clear overview with one-level-deep references that all resolve to real bundle files (references/flag_taxonomy.md, provider_comparison.md, rollout_strategies.md, flag_lifecycle.md), scripts, and an asset template — easy to navigate, nothing buried or nested.

5 / 5

Total

19

/

20

Passed

Description

100%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, third-person description that pairs concrete shipped artifacts with an explicit 'Use when...' trigger clause and broad natural trigger terms. It answers what and when with no fluff and occupies a distinct niche.

DimensionReasoningScore

Specificity

Names multiple concrete actions and artifacts: "Ships flag debt scanner, rollout planner, and kill-switch auditor", plus "a /flag-cleanup slash command" and "4 references" — comprehensive coverage, not vague.

5 / 5

Completeness

Explicitly answers both what ("adding, retiring, or auditing feature flags" with the shipped tools) and when ("Use when..." with concrete trigger phrases), matching the anchor for clearly answering both.

5 / 5

Trigger Term Quality

Comprehensive natural triggers including synonyms and provider names: "add a flag", "ship behind a flag", "rollout plan", "kill switch", "stale flags", "flag debt", plus LaunchDarkly/GrowthBook/Statsig/Unleash/Flipt — terms users would actually say.

5 / 5

Distinctiveness Conflict Risk

Clear niche (feature-flag lifecycle) with distinct, domain-specific triggers and named providers; minimal overlap risk with other skills.

5 / 5

Total

20

/

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.

Validation15 / 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.