New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

E2E Scenario Testing

by obra in obra/dotfiles

A skill your agent uses when verifying a running application end-to-end through its real interface — a web UI, a CLI, or a TUI — by writing and executing agent-run "scenario cards" against a freshly…

No licenceAuto-check passedTesting & QA

Install E2E Scenario Testing

skills CLI
$ npx skills add obra/dotfiles --skill e2e-scenario-testing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install obra/dotfiles e2e-scenario-testing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/obra/dotfiles.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/e2e-scenario-testing .claude/skills/e2e-scenario-testing && rm -rf skills-src

Use ~/.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/

Facts

Skill name
e2e-scenario-testing
GitHub stars
116
Token cost
~1.8k tokens
SKILL.md length
856 words
Files
1
Skills in repo
12
Repo updated
First seen
Licence
None found

At a glance

A skill your agent uses when verifying a running application end-to-end through its real interface — a web UI, a CLI, or a TUI — by writing and executing agent-run "scenario cards" against a freshly…

  • Works in 6 steps: Build fresh from the code under test.… → Isolate. Run in a hermetic workdir. If… → Drive the surface (recipes below). → …
  • Verifying a running application end-to-end through its real interface — a web UI
  • SKILL.md covers When to use this, The card format, Running a card and Driving a web UI (browser), plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

E2E Scenario Testing is an agent skill from obra/dotfiles. Use when verifying a running application end-to-end through its real interface — a web UI, a CLI, or a TUI — by writing and executing agent-run "scenario cards" against a freshly built instance with falsifiable assertions. Trigger on "test it end to end", "prove the UI actually works", "write/run a scenario", or after a change touches a user-facing surface that unit tests can't fully cover. Not for unit tests, pure code review, or API-only checks.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering End-to-end testing, Unit testing and Frontend development.

When your agent uses it

  • Verifying a running application end-to-end through its real interface — a web UI
  • A TUI — by writing and executing agent-run scenario cards against a freshly built instance with falsifiable assertions
  • Test it end to end
  • Prove the UI actually works

Example prompts

  • “scenario cards”
  • “test it end to end”
  • “prove the UI actually works”
  • “/e2e-scenario-testing”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Build fresh from the code under test. The single most common mistake is
  2. Isolate. Run in a hermetic workdir. If the app holds a host-level
  3. Drive the surface (recipes below).
  4. Assert against the authoritative record, not just the pixels. The UI can
  5. Capture evidence — a screenshot, the captured pane, the on-disk artifact.
  6. Clean up — shut down what you spawned, remove scratch dirs, leave

What it can do on your machine

Read from SKILL.md and the folder at commit df3be56. 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 (its code samples are markdown and bash).

    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

E2E Scenario Testing loads about 1.8k tokens when it runs. Until then it costs about 118 tokens; SKILL.md has 856 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~118
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k

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

Without a licence we can't republish the file, so here is its outline and opening line. It has 856 words (~1,799 tokens).

“Verify that a running application does what it claims, by driving its real interface the way a user would. The unit of work is a scenario card: a short markdown test written for an agent to execute — not a…”

— opening of SKILL.md by obra
name
e2e-scenario-testing

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .claude/skills/e2e-scenario-testing of obra/dotfiles.

Open the folder on GitHubat commit df3be56

Compare with similar skills

E2E Scenario Testing 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.

E2E Scenario Testing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
E2E Scenario Testing this skillobra/dotfiles116—~1.8kAutomated safety check: PassNone
TDD WorkflowhellangleZ/burn-in-cceverywhere-ralph11211 repos~2.4kAutomated safety check: PassNone
Contractssamchon/nestia2.2k—~1.3kAutomated safety check: PassMIT
Atdd Mutateswingerman/engineer154—~2.7kAutomated safety check: PassMIT
TDD Workflowaffaan-m/ECC275k2 repos~2kAutomated safety check: PassMIT
TDD Workflowaffaan-m/ECC275k2 repos~2.1kAutomated safety check: PassMIT

Similar skills

  • TDD Workflow

    hellangleZ/burn-in-cceverywhere-ralph

    A skill your agent uses when writing new features, fixing bugs, or refactoring code.

    112 GitHub starsUsed in 11 repos~2.4k tokens
    Testing & QAAuto-check passed

  • Contracts

    samchon/nestia

    Defines self-acknowledgments for production declarations and tests.

    2.2k GitHub stars~1.3k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Atdd Mutate

    swingerman/engineer

    A skill your agent uses to add a third validation layer to the ATDD workflow — after acceptance tests verify WHAT and unit tests verify HOW, mutation testing verifies the tests actually catch bugs.

    154 GitHub stars~2.7k tokensUpdated 15 days ago
    Testing & QAAuto-check passed

  • TDD Workflow

    affaan-m/ECC

    新機能の作成、バグ修正、コードのリファクタリング時にこのスキルを使用します。ユニット、統合、E2Eテストを含む80%以上のカバレッジでテスト駆動開発を強制します。

    275k GitHub starsUsed in 2 repos~2k tokens
    Testing & QAAuto-check passed

  • TDD Workflow

    affaan-m/ECC

    새 기능 작성, 버그 수정 또는 코드 리팩터링 시 이 스킬을 사용하세요. An agent skill from affaan-m/ECC.

    275k GitHub starsUsed in 2 repos~2.1k tokens
    Testing & QAAuto-check passed

  • TDD Workflow

    affaan-m/ECC

    Yeni özellikler yazarken, hata düzeltirken veya kod refactor ederken bu skill'i kullanın.

    275k GitHub starsUsed in 1 repo~2.6k tokens
    Testing & QAAuto-check passed

More from obra/dotfiles

All 12 skills in this repo

  • Maintaining Documentation

    obra/dotfiles

    A skill your agent uses when documentation needs creating, checking, or maintaining — docs may have drifted from code, pre-release doc verification, updating docs after finishing code work, adding…

    116 GitHub stars~3.9k tokensUpdated 1 mo ago
    Auto-check passed

  • Chronicle

    obra/dotfiles

    Allows you to view the user's screen as well as several hours of history.

    116 GitHub stars~1.4k tokensUpdated 1 mo ago
    Auto-check passed

  • Roborev Fix

    obra/dotfiles

    A skill your agent uses when the user asks to fix open failing reviews, invokes $roborev-fix, or provides job IDs; do not use when the user only pastes review findings with no request to discover or…

    116 GitHub stars~2.4k tokensUpdated 1 mo ago
    Auto-check passed

  • Syncing Obsidian

    obra/dotfiles

    A skill your agent uses when reading or writing files in an Obsidian vault that is synced with obsync.

    116 GitHub stars~1.7k tokensUpdated 1 mo ago
    Auto-check passed

  • MCP CLI

    obra/dotfiles

    Use MCP servers on-demand via the mcp CLI tool - discover tools, resources, and prompts without polluting context with pre-loaded MCP integrations

    116 GitHub starsUsed in 1 repo~2.3k tokens
    Auto-check passed

  • Roborev Design Review

    obra/dotfiles

    Request a design review for a commit and present the results

    116 GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about E2E Scenario Testing

What does E2E Scenario Testing do?

A skill your agent uses when verifying a running application end-to-end through its real interface — a web UI, a CLI, or a TUI — by writing and executing agent-run "scenario cards" against a freshly…. E2E Scenario Testing is an agent skill from obra/dotfiles. Use when verifying a running application end-to-end through its real interface — a web UI, a CLI, or a TUI — by writing and executing agent-run "scenario cards" against a freshly built instance with falsifiable assertions.

When should I use E2E Scenario Testing?

E2E Scenario Testing fits situations like: verifying a running application end-to-end through its real interface — a web UI; A TUI — by writing and executing agent-run scenario cards against a freshly built instance with falsifiable assertions; test it end to end; prove the UI actually works.

How do I install E2E Scenario Testing in Claude Code?

Run `npx skills add obra/dotfiles --skill e2e-scenario-testing -a claude-code`. Or copy the skill folder (.claude/skills/e2e-scenario-testing in obra/dotfiles) into .claude/skills/e2e-scenario-testing in your project. Claude Code loads it when a task matches its description.

How do I install E2E Scenario Testing in Codex?

Run `npx skills add obra/dotfiles --skill e2e-scenario-testing -a codex`. Or copy the skill folder (.claude/skills/e2e-scenario-testing in obra/dotfiles) into .agents/skills/e2e-scenario-testing in your project. Codex loads it when a task matches its description.

Can I use E2E Scenario Testing 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 obra/dotfiles --skill e2e-scenario-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/e2e-scenario-testing, .gemini/skills/e2e-scenario-testing, .github/skills/e2e-scenario-testing and .opencode/skills/e2e-scenario-testing in your project.

What does E2E Scenario Testing need to run?

SKILL.md names no scripts, command-line tools or credentials: E2E Scenario Testing is instructions for the agent only.

Does E2E Scenario Testing 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 E2E Scenario Testing 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 E2E Scenario Testing use?

No licence was found for E2E Scenario Testing or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.

How many tokens does E2E Scenario Testing use?

About 1.8k tokens (SKILL.md is roughly 7.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to E2E Scenario Testing?

Skills that share tags, products or a category with E2E Scenario Testing: TDD Workflow (hellangleZ/burn-in-cceverywhere-ralph, 112 stars), Contracts (samchon/nestia, 2.2k stars), Atdd Mutate (swingerman/engineer, 154 stars) and TDD Workflow (affaan-m/ECC, 275k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains E2E Scenario Testing?

obra (a GitHub user) maintains it in obra/dotfiles, which has 116 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on August 11, 2026.

Source: obra/dotfiles on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.