Skip to content
TrustedSkillsbeta
Back to all skills

Bdd Patterns

Checked
thebushidocollective·vlatest·testing

Analyzes behavioral data to identify recurring patterns and anomalies, providing actionable insights for optimization.

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-patterns -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-patterns/SKILL.md
Scanned
1 file, 111 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 helps AI agents understand and apply Behavior-Driven Development (BDD) patterns. It enables the creation of clear, business-readable specifications that drive software implementation using a Given-When-Then structure. The skill facilitates writing acceptance tests understandable by stakeholders, defining behavior before coding, and creating living documentation from those tests.

When to use it

  • Write acceptance tests that non-technical stakeholders can understand.
  • Define the desired behavior of a feature before development begins.
  • Create "living documentation" – test suites that also serve as specifications.
  • Improve communication and collaboration between developers and business teams.
  • Ensure new features align with specific business requirements.

Key capabilities

  • Given-When-Then Structure: Applying the core BDD pattern for defining scenarios.
  • Feature File Organization: Structuring tests to represent user stories and their related behaviors.
  • Scenario Outlines: Creating data-driven tests using examples to cover multiple input variations.
  • Step Definition Patterns: Understanding how to translate scenario steps into executable code (example provided in Ruby/Cucumber).
  • Backgrounds: Defining common setup steps that are reused across multiple scenarios.

Example prompts

  • "Generate a BDD feature file for user authentication with valid credentials."
  • "Create a Scenario Outline example for password validation, including tests for short passwords and passwords needing a number."
  • "Show me an example of a Background section in a BDD feature file."

Tips & gotchas

  • Focus on writing scenarios from the perspective of the user.
  • Avoid technical implementation details within your scenario descriptions; use declarative language instead.
  • Keep individual scenarios focused on testing a single, specific behavior.