Skip to content
TrustedSkillsbeta
Back to all skills

Playwright Bdd Step Definitions

Checked
thebushidocollective·vlatest·testing

Generates Playwright BDD step definitions from user stories, automating test creation for robust web application validation.

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 playwright-bdd-step-definitions -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/tools/playwright-bdd/skills/playwright-bdd-step-definitions/SKILL.md
Scanned
1 file, 584 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 allows AI agents to generate Playwright BDD (Behavior Driven Development) step definitions from feature files. It automates the process of creating test code based on human-readable scenarios, significantly reducing manual effort in test automation. The generated step definitions are ready for integration into a Playwright testing framework.

When to use it

  • Automating repetitive tests: Quickly generate step definitions for existing Gherkin feature files.
  • New project setup: Bootstrap a new Playwright BDD testing suite from scratch using generated step definitions.
  • Reducing development time: Accelerate the creation of automated tests by automating the initial code generation.
  • Maintaining test suites: Update or regenerate step definitions when feature file scenarios change.

Key capabilities

  • Generates Playwright step definitions from Gherkin feature files.
  • Supports BDD testing frameworks.
  • Automates test code creation.

Example prompts

  • "Generate Playwright step definitions for this feature file: [paste feature file content]"
  • "Create a new Playwright BDD test suite based on the following scenario: [paste scenario description]"
  • “Update the existing step definitions to reflect these changes in my feature file: [paste modified feature file content]”

Tips & gotchas

  • Ensure your Gherkin feature files are well-formatted and follow BDD best practices for optimal results.
  • The generated code may require minor adjustments based on specific project requirements or framework configurations.