Skip to content
TrustedSkillsbeta
Back to all skills

Bdd Scenarios

Checked
thebushidocollective·vlatest·testing

Generates Gherkin-style BDD scenarios from a given prompt, streamlining test case creation and improving collaboration.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add thebushidocollective/han --skill bdd-scenarios -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

thebushidocollective

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned thebushidocollective/han at 19caa51d5f.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
19caa51d5f
Manifest
plugins/patterns/bdd/skills/bdd-scenarios/SKILL.md
Scanned
1 file, 121 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill generates Gherkin-style Behavior Driven Development (BDD) scenarios based on a given prompt. It helps users create clear, maintainable BDD scenarios that capture business requirements and drive implementation. The skill emphasizes writing specific, declarative, and business-focused scenarios using domain language, while avoiding implementation details.

When to use it

  • Define acceptance criteria for user stories.
  • Document expected system behavior.
  • Create comprehensive test coverage.
  • Identify edge cases early in development.
  • Communicate requirements clearly.

Key capabilities

  • Generates Gherkin-style BDD scenarios.
  • Focuses on specific, declarative, and business-focused scenario writing.
  • Provides examples of good and bad scenarios to illustrate best practices.
  • Supports the creation of edge case scenarios.
  • Demonstrates the use of tags for organization and filtering.

Example prompts

  • "Generate a BDD scenario for user registration with valid details."
  • "Create an acceptance criteria scenario for order refunds within 30 days."
  • "Write a BDD scenario illustrating what happens when a user tries to register with an existing email address."

Tips & gotchas

  • Start with the "happy path" scenario before adding edge cases.
  • Keep scenarios concise, ideally between 3-7 steps.
  • Review generated scenarios with stakeholders to ensure clarity and accuracy.