CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/specflow-testing

Maintains SpecFlow tests on existing .NET projects - authors Gherkin `.feature` files, writes C# `[Binding]` step definitions, runs them via xUnit/NUnit/MsTest, and migrates a project to Reqnroll. SpecFlow is the legacy .NET BDD framework and Reqnroll is its maintained fork. Use only for existing SpecFlow projects, especially mid-migration; new .NET BDD projects use `reqnroll-testing` instead.

70

Quality

88%

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

72%

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

An actionable, well-structured legacy-spec skill whose code and commands are copy-paste ready. The main weaknesses are mild redundancy of the SpecFlow/Reqnroll framing and a missing explicit validation checkpoint in the destructive migration workflow.

Suggestions

Add an explicit validation checkpoint to the migration workflow (e.g., a numbered 'Run `dotnet test` and only proceed to step N when green; fix the first failing binding, then re-run') instead of the bare 'fix any breakages'.

Consolidate the legacy-vs-maintained framing so it appears once (e.g., in Overview) and remove restatements from Step 4, Anti-patterns, and Limitations to tighten conciseness.

Move the time-sensitive version (`3.9.74`) and date ("forked in 2023") into a labeled 'legacy/deprecated' note so they do not penalize conciseness as the framework ages.

DimensionReasoningScore

Conciseness

Mostly efficient and assumes Claude knows Gherkin/BDD, but the legacy-vs-maintained framing recurs across Overview, Step 4, Anti-patterns, and Limitations, and time-sensitive items (version `3.9.74`, "forked from it in 2023") sit outside a deprecated section, so it could be tightened.

2 / 3

Actionability

Provides executable, copy-paste-ready package references, a Gherkin feature, C# `[Binding]` step definitions, and concrete `dotnet remove`/`add`/`test` commands for migration.

3 / 3

Workflow Clarity

The migration is clearly sequenced (remove → add → find/replace → run), but for a destructive/batch operation the only validation is a bare "Run tests; fix any breakages" with no explicit checkpoint or checklist, which caps it at 2.

2 / 3

Progressive Disclosure

No bundle files exist (references/scripts/assets all absent); the ~130-line body is well-organized into clear sections and the References point to sibling skills one level deep, satisfying the simple-skill bar.

3 / 3

Total

10

/

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, third-person description that names specific concrete actions, supplies natural trigger terms, and gives an explicit use-when clause with clear routing away from the sibling Reqnroll skill. The SpecFlow-vs-Reqnroll framing aids distinctiveness.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "authors Gherkin `.feature` files", "writes C# `[Binding]` step definitions", "runs them via xUnit/NUnit/MsTest", "migrates a project to Reqnroll" — matching the level-3 anchor.

3 / 3

Completeness

Explicitly answers both what (maintains/tests/migrates) and when ("Use only for existing SpecFlow projects, especially mid-migration; new .NET BDD projects use `reqnroll-testing` instead"), with an explicit trigger clause.

3 / 3

Trigger Term Quality

Good coverage of natural terms a user would say: "SpecFlow tests", "Gherkin", ".feature files", "Reqnroll", "xUnit/NUnit/MsTest", and "mid-migration".

3 / 3

Distinctiveness Conflict Risk

Clear niche — legacy SpecFlow on existing .NET projects, mid-migration — with explicit routing of new work to `reqnroll-testing`, making it unlikely to trigger for the wrong skill.

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