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 (originated as a community port off the SpecFlow codebase); new .NET BDD work targets Reqnroll. Use for .NET projects starting BDD or migrating from SpecFlow.

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

85%

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 a clear sequenced workflow, explicit validation, and clean one-level progressive disclosure. The only weakness is conciseness, due to repeated quoted marketing lines from the Reqnroll home page that do not earn their tokens.

Suggestions

Replace the repeated 'Per [reqnroll-home][rh]: "..."' quote blocks with a single concise factual statement per step; drop marketing phrasing ('reboot', 'Works across common operating systems') that Claude does not need.

Trim the Overview's 'reboot' framing paragraph and the block-quote; lead with the practical distinction (active fork vs. slowed SpecFlow) in one line.

Keep the rh reference link as a single 'Source' citation rather than quoting it inline six times.

DimensionReasoningScore

Conciseness

Mostly efficient and well-organized, but repeated 'Per [reqnroll-home][rh]' marketing quote blocks (Steps 1, 2, 3, 4, 8, 9) and the Overview reboot framing are unnecessary context that could be tightened; it does not explain basic concepts Claude knows, so it stays above 1.

2 / 3

Actionability

Provides fully executable commands and code (dotnet add package, full .feature Gherkin, regex [Binding] steps, async example, dotnet test --filter, JUnit logger, migration find/replace) that are copy-paste ready, matching the score-3 anchor.

3 / 3

Workflow Clarity

Steps 1-9 are clearly sequenced with explicit validation checkpoints and feedback loops (Step 1 'Verify: dotnet build succeeds', Step 7 'fix the matching binding and re-run until it turns green', migration step 4 'Run tests; fix any compatibility issues').

3 / 3

Progressive Disclosure

Overview body splits the full CartSteps binding class and hook class into references/bindings-and-hooks.md, which is verified to exist and is one level deep with no nested references; links are clearly signaled.

3 / 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 concrete actions, natural trigger terms, an explicit 'Use for' clause, and a clear niche. Third-person voice is used correctly with no over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('install via `dotnet add package Reqnroll`', 'author `.feature` files in Gherkin', 'write step bindings as `[Given/When/Then]`-decorated methods', 'runs via `dotnet test`'), matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly answers both what (install/author/bind/run) and when ('Use for .NET projects starting BDD or migrating from SpecFlow'), with an explicit trigger clause.

3 / 3

Trigger Term Quality

Covers natural terms a user would say ('Reqnroll', 'SpecFlow', '.NET BDD', 'Gherkin', 'migrating from SpecFlow'), giving broad rather than partial keyword coverage.

3 / 3

Distinctiveness Conflict Risk

Clear niche as the canonical .NET BDD / SpecFlow successor with distinct triggers; unlikely to conflict, and it distinguishes itself from the legacy specflow-testing alternative.

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