CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/pairwise-test-case-generator

Generates parameterized test inputs combining boundary-value, equivalence-class, and pairwise-combinatorial cases from a typed multi-input specification - produces the cross-product of cases up to a configurable strength (1-wise / 2-wise / N-wise) using all-pairs reduction so the test surface stays tractable. Emits cases in the project's test-runner-native parametrize format. Use when a function or endpoint takes 3+ inputs whose interactions matter and full Cartesian product would explode.

80

Quality

100%

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

100%

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

The body is well-structured, actionable, and concise, with a clear multi-step workflow and an explicit coverage-report validation step. Content is appropriately split into one real, clearly linked reference file.

DimensionReasoningScore

Conciseness

Lean, table-and-code driven content that assumes Claude's competence; avoids explaining basic testing concepts and every token earns its place via concrete counts, tool tables, and a YAML spec.

3 / 3

Actionability

Provides an executable YAML spec, a concrete tool comparison with named CLIs/libraries (PICT, AllPairs, CATS), and copy-paste-ready parametrize snippets in the linked reference file.

3 / 3

Workflow Clarity

A clear 7-step sequence with an explicit validation checkpoint in Step 5 (review the coverage report, accept constraint-driven gaps or raise strength), forming a real feedback loop.

3 / 3

Progressive Disclosure

SKILL.md is an overview with a single, clearly signaled one-level-deep reference (references/output-formats.md), which exists and appropriately offloads the per-runner format snippets.

3 / 3

Total

12

/

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 description that names concrete actions, includes natural trigger terms, and explicitly covers both what and when with a 'Use when' clause. It is specific enough to avoid conflicts with related single-input skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: generating parameterized test inputs, combining boundary-value/equivalence-class/pairwise cases, all-pairs reduction of the cross-product, and emitting in runner-native parametrize format.

3 / 3

Completeness

Clearly answers both what (generate/reduce/emit parametrize cases) and when via an explicit 'Use when a function or endpoint takes 3+ inputs whose interactions matter and full Cartesian product would explode' trigger.

3 / 3

Trigger Term Quality

Uses natural trigger phrasing users would say: 'function or endpoint takes 3+ inputs whose interactions matter' and 'full Cartesian product would explode', alongside 'parameterized test inputs' and 'pairwise'.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (combinatorial pairwise test generation for 3+ interacting inputs) with distinct triggers that are unlikely to collide with sibling skills like boundary-value-generator.

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