CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/reqnroll-testing

Use for any question or task about BDD in .NET or C#: starting with Gherkin feature files, moving off SpecFlow (end-of-life 2024-12-31), or writing [Given/When/Then] C# step bindings. Configures Reqnroll with hooks, async steps, tags and dotnet test runs, and has a SpecFlow migration path.

Quality

92%

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 well-engineered skill body: every step carries executable commands or code, validation and fix-and-rerun loops are explicit, and bulk detail is correctly split into two clearly-signaled one-level-deep reference files. The only trimmable fat is the repeated source citations and the opening framework-description quote.

DimensionReasoningScore

Conciseness

Efficient overall: steps are short, commands are bare, and detail is deferred to reference files. Minor over-explanation could be trimmed — the Overview blockquote of what Reqnroll is and the 'Per [reqnroll-home][rh]' attestation repeated ~7 times — which keeps it below anchor 5's 'every token earns its place' but above anchor 3 since there is no substantial unnecessary explanation.

4 / 5

Actionability

Fully executable throughout: copy-paste 'dotnet add package Reqnroll.xUnit' install commands, a complete Features/Cart.feature file, a runnable async [Then] binding, 'dotnet test --filter "FullyQualifiedName~Cart"' and a JUnit logger command, plus a concrete worked example. The common cases (install, author, bind, run, migrate) are all covered with real code or commands.

5 / 5

Workflow Clarity

Nine clearly sequenced steps with explicit validation and feedback loops: Step 1 has '**Verify:** dotnet build succeeds and restores both packages', and Step 7 closes the loop — 'If a scenario fails or reports an undefined step, fix the matching binding... and re-run until it turns green'. Migration (Step 9) also ends in 'Run tests; fix any compatibility issues'. Matches anchor 5's explicit validation with error-recovery loops.

5 / 5

Progressive Disclosure

The body is an overview that pushes full detail to two real, one-level-deep bundle files — references/bindings-and-hooks.md (full binding class, cucumber-expression variant, hook class) and references/specflow-legacy.md (legacy support, EOL background, full migration path) — both present in the bundle, clearly signaled inline at the point of need, and indexed in a References section. Navigation is easy and nothing is nested further.

5 / 5

Total

19

/

20

Passed

Description

87%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 pairs an explicit 'Use for...' trigger clause rich in natural domain keywords (BDD, .NET, C#, Gherkin, SpecFlow, Given/When/Then) with a concrete capability list (hooks, async steps, tags, dotnet test runs, migration path). The only gaps are minor — a couple of body capabilities and the 'Cucumber' synonym are not surfaced.

DimensionReasoningScore

Specificity

Lists several concrete actions — "starting with Gherkin feature files", "writing [Given/When/Then] C# step bindings", "Configures Reqnroll with hooks, async steps, tags and dotnet test runs" — matching the 'several specific actions; minor gaps' anchor. It falls short of anchor 5's comprehensive coverage because body capabilities like IDE support, cucumber expressions, and Rule blocks are not mentioned.

4 / 5

Completeness

Explicitly answers both parts: the trigger clause "Use for any question or task about BDD in .NET or C#... moving off SpecFlow... or writing [Given/When/Then] C# step bindings" gives concrete 'when' guidance, and "Configures Reqnroll with hooks, async steps, tags and dotnet test runs, and has a SpecFlow migration path" gives a clear 'what'. This matches the anchor-5 example structure; the explicit 'Use for...' clause means the completeness cap does not apply.

5 / 5

Trigger Term Quality

Good natural-keyword coverage: "BDD in .NET or C#", "Gherkin feature files", "SpecFlow", "Given/When/Then", "step bindings" — phrases users would actually say. A few natural terms are missing (the 'Cucumber' synonym for Cucumber-style BDD, the '.feature' file extension), which keeps it below anchor 5's 'including synonyms and file extensions'.

4 / 5

Distinctiveness Conflict Risk

The niche is sharply pinned to ".NET or C#" BDD with SpecFlow/Reqnroll-specific terms, so it would not trigger for general testing skills or sibling-language BDD wrappers (Cucumber-JVM, Python behave). Clear niche with distinct triggers — anchor 5.

5 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

On this page