Web Application Testing
anthropics/skills
Tests local web applications with Python Playwright scripts, checking frontend behavior, capturing screenshots and reading browser console logs.
Scannable BDD tests written in domain language. An agent skill from lexler/skill-factory.
Install Bdd With Approvals
$ npx skills add lexler/skill-factory --skill bdd-with-approvals -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install lexler/skill-factory bdd-with-approvals --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/lexler/skill-factory.git skills-src && mkdir -p .claude/skills && cp -r skills-src/output_skills/testing/bdd-with-approvals .claude/skills/bdd-with-approvals && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "bdd-with-approvals" agent skill from https://github.com/lexler/skill-factory/tree/main/output_skills/testing/bdd-with-approvals into .claude/skills/bdd-with-approvals/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bdd-with-approvals", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/lexler/skill-factory/tree/main/output_skills/testing/bdd-with-approvalsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add lexler/skill-factory --skill bdd-with-approvals -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install lexler/skill-factory bdd-with-approvals --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/lexler/skill-factory.git skills-src && mkdir -p .agents/skills && cp -r skills-src/output_skills/testing/bdd-with-approvals .agents/skills/bdd-with-approvals && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "bdd-with-approvals" agent skill from https://github.com/lexler/skill-factory/tree/main/output_skills/testing/bdd-with-approvals into .agents/skills/bdd-with-approvals/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bdd-with-approvals", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add lexler/skill-factory --skill bdd-with-approvals -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install lexler/skill-factory bdd-with-approvals --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/lexler/skill-factory.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/output_skills/testing/bdd-with-approvals .cursor/skills/bdd-with-approvals && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "bdd-with-approvals" agent skill from https://github.com/lexler/skill-factory/tree/main/output_skills/testing/bdd-with-approvals into .cursor/skills/bdd-with-approvals/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bdd-with-approvals", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/lexler/skill-factory.git --path output_skills/testing/bdd-with-approvals--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add lexler/skill-factory --skill bdd-with-approvals -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install lexler/skill-factory bdd-with-approvals --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/lexler/skill-factory.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/output_skills/testing/bdd-with-approvals .gemini/skills/bdd-with-approvals && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "bdd-with-approvals" agent skill from https://github.com/lexler/skill-factory/tree/main/output_skills/testing/bdd-with-approvals into .gemini/skills/bdd-with-approvals/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bdd-with-approvals", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install lexler/skill-factory bdd-with-approvalsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add lexler/skill-factory --skill bdd-with-approvals -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/lexler/skill-factory.git skills-src && mkdir -p .github/skills && cp -r skills-src/output_skills/testing/bdd-with-approvals .github/skills/bdd-with-approvals && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "bdd-with-approvals" agent skill from https://github.com/lexler/skill-factory/tree/main/output_skills/testing/bdd-with-approvals into .github/skills/bdd-with-approvals/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bdd-with-approvals", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add lexler/skill-factory --skill bdd-with-approvals -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install lexler/skill-factory bdd-with-approvals --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/lexler/skill-factory.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/output_skills/testing/bdd-with-approvals .opencode/skills/bdd-with-approvals && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "bdd-with-approvals" agent skill from https://github.com/lexler/skill-factory/tree/main/output_skills/testing/bdd-with-approvals into .opencode/skills/bdd-with-approvals/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bdd-with-approvals", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
bdd-with-approvals- GitHub stars
- 239
- Token cost
- ~731 tokens
- SKILL.md length
- 354 words
- Files
- 3 (incl. references)
- Skills in repo
- 25
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Scannable BDD tests written in domain language. An agent skill from lexler/skill-factory.
- Works in 3 steps: Parser - extracts input from fixture… → Formatter (printer) - converts actual… → Single test file discovers and runs all…
- Testing & QA work in your project
- SKILL.md covers The Problem, Executable Specifications, Approved Fixtures and Format Design, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Bdd With Approvals is an agent skill from lexler/skill-factory. Scannable BDD tests written in domain language. Use when doing BDD.
Its SKILL.md is about 730 tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/approved-fixtures.md` and `references/approved-logs.md`).
It sits in Testing & QA. The licence is Apache-2.0.
When your agent uses it
- Testing & QA work in your project
Example prompts
- “/bdd-with-approvals”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Parser - extracts input from fixture format
- Formatter (printer) - converts actual output to fixture format
- Single test file discovers and runs all fixtures
What it can do on your machine
Read from SKILL.md and the folder at commit e262032. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Bdd With Approvals loads about 731 tokens when it runs, and up to ~2.2k if it reads all its reference files. Until then it costs about 22 tokens; SKILL.md has 354 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from lexler/skill-factory at commit e262032, republished under its Apache-2.0 licence (© lexler). 354 words, ~731 tokens.
Download SKILL.mdSave it as
.claude/skills/bdd-with-approvals/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- bdd-with-approvals
- description
- Scannable BDD tests written in domain language. Use when doing BDD.
BDD with Approval Tests
The Problem
Specifications live in documents. They drift from reality because nothing enforces them.
Tests verify implementation. Written after code, they document what IS, not what SHOULD BE. They're noisy. You can't glance at them and quickly validate correctness.
You need an artifact that:
- Captures expected behavior before code exists
- Stays in sync because it's executable
- A human can validate at a glance
Executable Specifications
The fixture file IS that artifact. Write it BEFORE implementation.
Think through scenarios by creating approval files. Describe expected behavior in domain language. Implementation is driven by making these specs pass. Specs stay executable, never go stale.
A human looks at the fixture and immediately sees: correct or not. No translation between "spec" and "test". They're the same artifact.
For the approval testing technique itself (verify, scrubbers, combinations), see /approval-tests. For nulled infrastructure in system tests, see /nullables.
Approved Fixtures
Test files combining input and expected output in a format designed for human validation.
## Input
(context, parameters, initial state)
## Output
(expected results, side effects, final state)Test runner reads fixtures, executes code, compares output. Adding test cases = adding files, not code.
Design the format for YOUR domain:
- Grid/spatial problems → ASCII art
- Transformations → before/after
- Workflows → step sequences with results
- API interactions → request/response pairs
See references/approved-fixtures.md for examples.
Show full SKILL.md (151 more words)Show less
Format Design
The question: Can someone validate correctness in <5 seconds?
Design for human eyes, not machine parsing. Match the domain's natural representation. How you'd explain it on a whiteboard.
What makes formats scannable:
- Columnar layouts with visual alignment
- Consistent structure across all cases
- Whitespace that groups related elements
Avoid:
- Dense JSON (hard to scan)
- Single-line formats (no visual structure)
- Formats requiring mental parsing
Implementation
One-time per domain:
- Parser - extracts input from fixture format
- Formatter (printer) - converts actual output to fixture format
- Single test file discovers and runs all fixtures
Keep parser/formatter simple. Format should be close to natural representation.
Approved Logs
Turn production logs into tests by copying and fixing incorrect lines. Quick bug reproduction.
Caveat: Logs are for runtime observability, not test validation. Tying tests to log format creates coupling. Log changes break tests. Use sparingly when logs happen to capture the behavior well.
© lexler, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in output_skills/testing/bdd-with-approvals of lexler/skill-factory.
- SKILL.md
- references/approved-fixtures.md
- references/approved-logs.md
Open the folder on GitHubat commit e262032
Compare with similar skills
Bdd With Approvals next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Bdd With Approvals this skilllexler/skill-factory | 239 | — | ~731 | Automated safety check: Pass | Apache-2.0 | |
| Web Application Testinganthropics/skills | 180k | 51 repos | ~966 | Automated safety check: Pass | Apache-2.0 | |
| Diagnosing Bugsfossasia/eventyay-interpretation | 1.6k | 32 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| TDDpietheinstrengholt/rssmonster | 564 | 30 repos | ~906 | Automated safety check: Pass | MIT | |
| TDD WorkflowhellangleZ/burn-in-cceverywhere-ralph | 112 | 11 repos | ~2.4k | Automated safety check: Pass | None | |
| TDDsanity-io/sanity | 6.4k | 20 repos | ~1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Diagnosing Bugs
fossasia/eventyay-interpretation
Diagnosis loop for hard bugs and performance regressions. An agent skill from fossasia/eventyay-interpretation.
TDD
pietheinstrengholt/rssmonster
Test-driven development. An agent skill from pietheinstrengholt/rssmonster.
TDD Workflow
hellangleZ/burn-in-cceverywhere-ralph
A skill your agent uses when writing new features, fixing bugs, or refactoring code.
- Official
TDD
sanity-io/sanity
Test-driven development with red-green-refactor loop. An agent skill from sanity-io/sanity.
Context Driven Development
Ibrahim-3d/orchestrator-supaconductor
A skill your agent uses when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md…
More from lexler/skill-factory
All 25 skills in this repoC4 Architecture Diagrams
lexler/skill-factory
Creates C4 model diagrams at every zoom level, from system landscape to code, in ASCII, Mermaid or Structurizr, for designing or documenting software architecture.
Launching Agent Teams
lexler/skill-factory
Plans and launches Claude Code agent teams with distinct roles, right-sized tasks and detailed spawn prompts, and says when subagents or worktrees fit better.
Claude Code Statusline Writer
lexler/skill-factory
Guides writing and debugging Claude Code status line scripts that read session JSON from stdin and print one line of text.
Augmented Coding Patterns Reference
lexler/skill-factory
Catalog of obstacles, anti-patterns and patterns for working with AI coding agents, covering context management and reliability, from a published patterns collection.
Approval Testing Toolkit
lexler/skill-factory
Writes snapshot-style approval tests in Python, JavaScript, TypeScript or Java, comparing output against an approved file instead of writing individual assertions.
Hotspots
lexler/skill-factory
Find where a codebase actually costs time by mining its git history (Tornhill hotspot analysis).
Related
Categories
Questions about Bdd With Approvals
What does Bdd With Approvals do?
Scannable BDD tests written in domain language. An agent skill from lexler/skill-factory. Bdd With Approvals is an agent skill from lexler/skill-factory. Scannable BDD tests written in domain language.
When should I use Bdd With Approvals?
Bdd With Approvals fits situations like: testing & QA work in your project.
How do I install Bdd With Approvals in Claude Code?
Run `npx skills add lexler/skill-factory --skill bdd-with-approvals -a claude-code`. Or copy the skill folder (output_skills/testing/bdd-with-approvals in lexler/skill-factory) into .claude/skills/bdd-with-approvals in your project. Claude Code loads it when a task matches its description.
How do I install Bdd With Approvals in Codex?
Run `npx skills add lexler/skill-factory --skill bdd-with-approvals -a codex`. Or copy the skill folder (output_skills/testing/bdd-with-approvals in lexler/skill-factory) into .agents/skills/bdd-with-approvals in your project. Codex loads it when a task matches its description.
Can I use Bdd With Approvals in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add lexler/skill-factory --skill bdd-with-approvals -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bdd-with-approvals, .gemini/skills/bdd-with-approvals, .github/skills/bdd-with-approvals and .opencode/skills/bdd-with-approvals in your project.
What does Bdd With Approvals need to run?
SKILL.md names no scripts, command-line tools or credentials: Bdd With Approvals is instructions for the agent only.
Does Bdd With Approvals access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Bdd With Approvals safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Bdd With Approvals use?
Bdd With Approvals is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Bdd With Approvals use?
About 731 tokens (SKILL.md is roughly 2.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.5k tokens, read only when the agent opens those files.
What are the alternatives to Bdd With Approvals?
Skills that share tags, products or a category with Bdd With Approvals: Web Application Testing (anthropics/skills, 180k stars), Diagnosing Bugs (fossasia/eventyay-interpretation, 1.6k stars), TDD (pietheinstrengholt/rssmonster, 564 stars) and TDD Workflow (hellangleZ/burn-in-cceverywhere-ralph, 112 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Bdd With Approvals?
lexler (a GitHub user) maintains it in lexler/skill-factory, which has 239 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on October 10, 2026.
Source: lexler/skill-factory on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.