CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/reqnroll-testing

Configures Reqnroll (the canonical .NET BDD framework) - install via `dotnet add package Reqnroll`, author `.feature` files in Gherkin, write step bindings as `[Given/When/Then]`-decorated methods in any C# class, runs via `dotnet test`. Reqnroll is the SpecFlow successor (SpecFlow reached end-of-life 2024-12-31); covers the SpecFlow-to-Reqnroll migration path, and references/specflow-legacy.md maintains not-yet-migrated SpecFlow projects. Use for .NET projects starting BDD, migrating from SpecFlow, or maintaining legacy SpecFlow suites.

75

Quality

94%

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%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 tight, highly actionable skill body with clear sequencing, explicit validation loops, and well-organized one-level-deep references. Only minor conciseness trim opportunities around quoted homepage blurbs.

Suggestions

Trim or paraphrase the quoted reqnroll.net blocks in Steps 2, 4, and 8 where the surrounding prose already conveys the same point, to save tokens.

Consider condensing the per-step "Per [reqnroll-home][rh]:" quotations into a single source citation at the top, since they repeat throughout.

DimensionReasoningScore

Conciseness

Lean numbered steps with executable code and terse prose, but a few quoted reqnroll.net blurbs restate what the surrounding sentences already convey and could be trimmed.

4 / 5

Actionability

Fully executable, copy-paste-ready guidance across install, feature authoring, step bindings, async, hooks, tags, and CI run commands, covering the common cases comprehensively.

5 / 5

Workflow Clarity

Clear 9-step sequence with explicit validation checkpoints (Step 1 "Verify: dotnet build succeeds", Step 7 fix-and-rerun loop) and a reinforcing worked example.

5 / 5

Progressive Disclosure

SKILL.md serves as an overview with well-signaled one-level-deep references to real files (bindings-and-hooks.md, specflow-legacy.md), each described by purpose, with no nested reference chains.

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 highly specific, well-structured description that explicitly covers both capability and trigger conditions in third person. Minor room for broader keyword synonyms, but overall excellent.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — install via `dotnet add package`, author `.feature` files in Gherkin, write `[Given/When/Then]` bindings, run via `dotnet test`, and the migration path — covering the full workflow comprehensively.

5 / 5

Completeness

Explicitly answers both what (install, author, bind, run, migrate) and when ("Use for .NET projects starting BDD, migrating from SpecFlow, or maintaining legacy SpecFlow suites") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural keywords ("starting BDD", "migrating from SpecFlow", "legacy SpecFlow", ".NET", Gherkin), but missing common synonyms such as "Cucumber" or behavior-driven variations that a user might say.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (.NET BDD via Reqnroll/SpecFlow) with distinct triggers and minimal overlap risk; sibling skills are explicitly scoped to other languages in the body.

5 / 5

Total

19

/

20

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