CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/feature-flag-test-matrix-reference

Pure-reference catalog of feature-flag test matrix design. Defines the flag-state combinatorics problem (N flags × M variants × K user-segments = N×M×K test cases), the canonical coverage strategies (pairwise interaction coverage; default-only smoke; full matrix; risk-driven matrix), the kill-switch + percentage-rollout test patterns, and the relationship between flags + experiments (flags toggle behaviour; experiments measure outcome). Use when designing the flag-test surface for a new project or auditing existing flag-test coverage.

77

Quality

97%

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

Overview
Quality
Evals
Security
Files

Quality

Content

92%

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

A well-structured, dense reference catalog with concrete actionable guidance and a clear sequenced workflow. Its main weakness is progressive disclosure: a single long file where detailed strategies and the worked example could be split into reference files.

Suggestions

Split the detailed coverage strategies and the worked example into separate reference files (e.g. references/coverage-strategies.md, references/worked-example.md), keeping SKILL.md as a concise overview that links one level deep.

Move the special flag-state categories and flag-test layering tables into a reference file, surfacing only the key categories inline with pointers to the full tables.

Add a short navigation block near the top listing the reference files so the overview reads as an index rather than the full catalog inline.

DimensionReasoningScore

Conciseness

The body is a dense reference catalog with tables and minimal prose, assuming Claude's competence (it never explains what a feature flag is), so every section earns its place.

3 / 3

Actionability

It provides a concrete 7-step process, named tools and strategies, and a fully worked billing example; though code-free, the guidance is specific and actionable, which the rubric permits for instruction-only skills.

3 / 3

Workflow Clarity

The 'How to use' steps are a clearly numbered sequence with an embedded verification gate in step 2 (compute N×M×K to confirm enumeration is infeasible) and an anti-patterns table serving as a checklist.

3 / 3

Progressive Disclosure

Sections are well-organized and the References section is clearly signaled with no nested references, but the ~190-line body is monolithic with no bundle-file split for the detailed strategies and worked example.

2 / 3

Total

11

/

12

Passed

Description

100%

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, specific description with explicit trigger guidance, concrete enumerated capabilities, and a clear distinct niche. It uses third-person voice and avoids vague fluff.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete contents — the combinatorics problem, four named coverage strategies, kill-switch/percentage-rollout patterns, and the flags-vs-experiments relationship — rather than vague language.

3 / 3

Completeness

It explicitly answers both what (the catalog of strategies and patterns) and when, via an explicit 'Use when designing the flag-test surface for a new project or auditing existing flag-test coverage' clause.

3 / 3

Trigger Term Quality

It uses natural practitioner terms a user would actually say — 'feature-flag test matrix', 'flag-test surface', 'auditing flag-test coverage', 'kill-switch', 'percentage-rollout' — with good coverage of variations.

3 / 3

Distinctiveness Conflict Risk

The niche is narrow and specific — feature-flag test matrix design/auditing — with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents