CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gherkin-bdd

Write BDD scenarios in Gherkin. Trigger: acceptance criteria, Given/When/Then, feature files, test scenarios.

72

Quality

90%

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

SKILL.md
Quality
Evals
Security

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, high-signal instruction skill: concrete templates and examples, explicit rules with rationale, an anti-pattern table, and a coverage gate with a done-when checklist. Its only minor trim opportunity is the philosophical opening paragraph.

DimensionReasoningScore

Conciseness

The body is lean and assumes Gherkin knowledge: a structure template, one complete Scenario Outline example, seven one-paragraph rules, and a compact anti-pattern table. Only the opening "A Gherkin scenario is a contract..." paragraph is non-operational and could be trimmed, matching 'Efficient; minor instances of over-explanation that could be trimmed'.

4 / 5

Actionability

Guidance is fully concrete: a complete structure template, an executable Scenario Outline with real Examples rows, inline good/bad step pairs ("When the customer submits the order" vs "When I click '#submit-btn'"), and an anti-pattern table with fixes — copy-paste-ready for the common cases.

5 / 5

Workflow Clarity

For this single-purpose skill the action is unambiguous (work from the use-case/edge-case list, write one scenario per case), and the "Done when" checklist provides explicit validation gates (every case maps to a scenario, exactly one When, observable Then, no inter-scenario dependencies).

5 / 5

Progressive Disclosure

No bundle files exist and none are needed at this length (~68 lines); the content is cleanly sectioned (Structure, Rules, Anti-patterns, Coverage) with no inlined material that belongs in a separate file.

5 / 5

Total

19

/

20

Passed

Description

82%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 concise, third-person description with an explicit trigger clause and concrete, natural trigger phrases. Its only weakness is that it names a single capability rather than enumerating what the skill does more comprehensively.

Suggestions

Add 1-2 more concrete capabilities after "Write BDD scenarios in Gherkin" (e.g., 'review and refactor existing scenarios, map acceptance criteria to feature files') to lift specificity.

Add missing natural synonyms such as 'BDD', 'Cucumber', or '.feature' to the trigger list for fuller keyword coverage.

DimensionReasoningScore

Specificity

"Write BDD scenarios in Gherkin" names the domain and one concrete action, but lists no other capabilities (e.g., reviewing or refactoring existing scenarios, mapping acceptance criteria to features), matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'.

3 / 5

Completeness

It explicitly answers both parts: the what is "Write BDD scenarios in Gherkin" and the when is the explicit "Trigger:" clause with concrete trigger phrases, matching the top anchor for clearly and explicitly answering both what AND when.

5 / 5

Trigger Term Quality

The trigger list "acceptance criteria, Given/When/Then, feature files, test scenarios" contains natural phrases users would say, but common synonyms and extensions such as "BDD", "Cucumber", and ".feature" are missing, matching 'Good keyword coverage; a few natural terms missing'.

4 / 5

Distinctiveness Conflict Risk

Gherkin/BDD is a clear niche, and "Given/When/Then", "feature files", and "acceptance criteria" are distinct triggers with minimal overlap risk against other testing or documentation skills.

5 / 5

Total

17

/

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.

Repository

YoizenSA/dev-ai-workflow

Path

ywai/skills/gherkin-bdd/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.