live-verified-bdd SKILL.md skillA
live-verified-bdd from beakpoint-insights/roost is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add beakpoint-insights/roost/live-verified-bdd@git:20261026.505a1daPins git:20261026.505a1da in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- beakpoint-insights/roost
- Path
skills/live-verified-bdd/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261026.505a1da, committed Oct 26, 2026
- First version recorded
- Oct 26, 2026
- Size
- 6,410 bytes
- Repository stars
- 30
- License
- MIT
Write or revise Cucumber scenarios for a feature that already runs, then walk each one in the live app with Playwright and correct it to match what the app does. Use to write test scenarios, or to check that existing scenarios still match the app. Doesn't file anything in the tracker; hand the result to create-xray-test. For a new epic that isn't built yet, use shape-epic.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Live-Verified BDD Test Writing Write Cucumber/Gherkin scenarios and check each one in the running app before calling them done. Every scenario is walked through in the browser with Playwright. The app is the source of truth, not the code. ## When to Use - Writing scenarios for a feature that already runs - Checking that existing scenarios still match what the app does - The user says "write tests", "BDD", "Cucumber", "Gherkin" or "E2E test cases" for something that's built ## When Not to Use - **Filing scenarios as the team's tests:** the tests adapter's "Create a test" does that. This skill hands off to it at the end. - **A new epic that isn't built yet:** there's no app to check against. `shape-epic` writes those scenarios from the prototype. This file holds the Gherkin style guide that the other skills follow. **First, load the team config with `roost-config`.** `stack.services` gives the app's URLs, and `qa.test_account_email` the pattern for test accounts. ## Workflow ### Phase 1: Gather Context Ask the user for: 1. **What to test** — feature name, ticket, or area of the app 2. **Scope** — which vendors/entities/flows to include (avoid testing everything) …
Read the whole file at its exact version.
How to install
mdr add beakpoint-insights/roost/live-verified-bdd@sha256:d486b9e8698c2609The line at the top of this page pins the label git:20261026.505a1da, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_p44wsexl7hfcqk6g)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Oct 26, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261026.505a1da latest | 2026-10-26 | 505a1da | 6,410 B | A | view · diff |
| git:20261026.66cdcd9 | 2026-10-26 | 66cdcd9 | 6,386 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6410 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
beakpoint-insights/roost · 30 stars · license MIT · pushed 2026-10-31 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_p44wsexl7hfcqk6g GET https://markdownregistry.com/api/v1/resolve?ref=beakpoint-insights/roost/live-verified-bdd GET https://markdownregistry.com/api/v1/blob/d486b9e8698c2609abdffb06dda3c1044b8dfee8e8798931bc6a910e99a64691
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.