CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/behave-testing

Configures Behave for Python BDD scenarios - `pip install behave`, authors `.feature` files in Gherkin, writes step implementations in `features/steps/*.py`, configures via `environment.py` for setup/teardown hooks, organizes via tags, runs via `behave`. Use for Python codebases that want Cucumber-family BDD without Cucumber-Ruby / Cucumber-JS.

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

Overview
Quality
Evals
Security
Files

Quality

Content

82%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 highly actionable, well-sequenced skill body dominated by executable code and commands, with clean sectioning and one-level sibling references. It would tighten up by trimming the quoted Overview fluff and adding an explicit run-then-fix feedback loop in the workflow.

Suggestions

Trim the Overview's three quoted doc blocks to a single framing sentence; the BDD/collaboration exposition is padding Claude already knows.

Add an explicit validation feedback loop in the workflow, e.g. after Step 8: 'Run behave; if scenarios fail, re-read the failing step in Step 4 and fix the matcher/assertion, then re-run'.

Consider splitting the Anti-patterns or pytest-bdd comparison into a referenced file if the skill grows, to keep SKILL.md a lean overview.

DimensionReasoningScore

Conciseness

Mostly lean and code-forward across the nine steps, but the Overview carries three quoted doc blocks ('behave is behaviour-driven development, Python style', the collaboration framing, the 'semi-official Cucumber tier' line) that are mild marketing-style padding Claude does not need.

4 / 5

Actionability

Fully executable throughout: 'pip install behave', a concrete project layout, a complete .feature example, copy-paste step implementations with imports/decorators/assertions, environment.py hooks, tag-filtering and reporting commands, and run invocations — specific examples cover the common cases.

5 / 5

Workflow Clarity

A clear nine-step sequence (install → layout → feature → steps → hooks → tags → reporting → run → alternative) with Step 8 serving as the run/verify checkpoint, but there is no explicit 'run, then fix failing steps' feedback loop stated in the sequence.

4 / 5

Progressive Disclosure

Well-organized into labeled sections (Steps 1-9, Anti-patterns, Limitations, References) with one-level-deep pointers to sibling skills and the external behave docs; no bundle files are provided and no nested references, though the entire body lives in a single file with no 'see X.md for advanced' split.

4 / 5

Total

17

/

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 strong, third-person description that names the tool, lists six concrete actions with specific file paths, and includes an explicit 'Use for' trigger that carves out a distinct niche from sibling Cucumber wrappers. The only minor gap is coverage of a few natural trigger phrasings like 'acceptance criteria'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions with specific artifacts: 'pip install behave', 'authors .feature files in Gherkin', 'writes step implementations in features/steps/*.py', 'configures via environment.py for setup/teardown hooks', 'organizes via tags', 'runs via behave' — comprehensive coverage with concrete file paths.

5 / 5

Completeness

Explicitly answers both: 'what' (configures Behave, authors .feature files, writes steps, configures environment.py, organizes via tags, runs via behave) and 'when' ('Use for Python codebases that want Cucumber-family BDD without Cucumber-Ruby / Cucumber-JS') with a concrete trigger clause.

5 / 5

Trigger Term Quality

Good keyword coverage including Behave, Python BDD, Gherkin, .feature, and the Cucumber-family synonyms (Cucumber-Ruby / Cucumber-JS), but a few natural trigger phrasings a user might say (e.g. 'acceptance criteria', 'BDD tests') are only partially present.

4 / 5

Distinctiveness Conflict Risk

Clear niche — Python BDD via Behave — and explicitly distinguishes itself from Cucumber-Ruby / Cucumber-JS, giving it distinct triggers with minimal conflict risk.

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