Agent skill

E2E Example Acceptance

Validate or update example-level E2E coverage. An agent skill from farm-fe/farm.

MITAuto-check passedTesting & QA

Install E2E Example Acceptance

skills CLI

$ npx skills add farm-fe/farm --skill e2e-example-acceptance -a claude-code

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

GitHub CLI

$ gh skill install farm-fe/farm e2e-example-acceptance --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/farm-fe/farm.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/e2e-example-acceptance .claude/skills/e2e-example-acceptance && 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/

Paste into Claude Code

Install the "e2e-example-acceptance" agent skill from https://github.com/farm-fe/farm/tree/main/.github/skills/e2e-example-acceptance into .claude/skills/e2e-example-acceptance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "e2e-example-acceptance", 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

$skill-installer install https://github.com/farm-fe/farm/tree/main/.github/skills/e2e-example-acceptance

Type 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.

skills CLI

$ npx skills add farm-fe/farm --skill e2e-example-acceptance -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install farm-fe/farm e2e-example-acceptance --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/farm-fe/farm.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/e2e-example-acceptance .agents/skills/e2e-example-acceptance && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "e2e-example-acceptance" agent skill from https://github.com/farm-fe/farm/tree/main/.github/skills/e2e-example-acceptance into .agents/skills/e2e-example-acceptance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "e2e-example-acceptance", 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.

skills CLI

$ npx skills add farm-fe/farm --skill e2e-example-acceptance -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install farm-fe/farm e2e-example-acceptance --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/farm-fe/farm.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/e2e-example-acceptance .cursor/skills/e2e-example-acceptance && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "e2e-example-acceptance" agent skill from https://github.com/farm-fe/farm/tree/main/.github/skills/e2e-example-acceptance into .cursor/skills/e2e-example-acceptance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "e2e-example-acceptance", 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

$ gemini skills install https://github.com/farm-fe/farm.git --path .github/skills/e2e-example-acceptance

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add farm-fe/farm --skill e2e-example-acceptance -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install farm-fe/farm e2e-example-acceptance --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/farm-fe/farm.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/e2e-example-acceptance .gemini/skills/e2e-example-acceptance && rm -rf skills-src

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

Paste into Gemini CLI

Install the "e2e-example-acceptance" agent skill from https://github.com/farm-fe/farm/tree/main/.github/skills/e2e-example-acceptance into .gemini/skills/e2e-example-acceptance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "e2e-example-acceptance", 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.

GitHub CLI

$ gh skill install farm-fe/farm e2e-example-acceptance

Installs 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).

skills CLI

$ npx skills add farm-fe/farm --skill e2e-example-acceptance -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/farm-fe/farm.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/e2e-example-acceptance .github/skills/e2e-example-acceptance && rm -rf skills-src

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

Paste into GitHub Copilot

Install the "e2e-example-acceptance" agent skill from https://github.com/farm-fe/farm/tree/main/.github/skills/e2e-example-acceptance into .github/skills/e2e-example-acceptance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "e2e-example-acceptance", 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.

skills CLI

$ npx skills add farm-fe/farm --skill e2e-example-acceptance -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install farm-fe/farm e2e-example-acceptance --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/farm-fe/farm.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/e2e-example-acceptance .opencode/skills/e2e-example-acceptance && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "e2e-example-acceptance" agent skill from https://github.com/farm-fe/farm/tree/main/.github/skills/e2e-example-acceptance into .opencode/skills/e2e-example-acceptance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "e2e-example-acceptance", 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: e2e-example-acceptance
GitHub stars: 5.6k
Token cost: ~776 tokens
SKILL.md length: 253 words
Files: 1
Skills in repo: 20
Repo updated: Sep 22, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Validate or update example-level E2E coverage. An agent skill from farm-fe/farm.

Works in 5 steps: Identify affected examples → Build each affected example → Run start and preview checks for each… → …
Adding/updating e2e.spec.ts
SKILL.md covers When to Use, Mandatory Acceptance Flow, Authoring Template and Reporting Format, plus 1 more section
Calls npm and pnpm

What it does

E2E Example Acceptance is an agent skill from farm-fe/farm. Validate or update example-level E2E coverage. Use when adding/updating e2e.spec.ts, debugging example start/build/preview behavior, or verifying browser console/request errors and page expectations.

Its SKILL.md is about 780 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires Node, pnpm, and Playwright dependencies installed.

It sits in Testing & QA, covering End-to-end testing. It works with npm. The repository describes itself as: Extremely fast Vite-compatible web build tool written in Rust. The licence is MIT.

When your agent uses it

Adding/updating e2e.spec.ts
Debugging example start/build/preview behavior
Verifying browser console/request errors and page expectations

Example prompts

“/e2e-example-acceptance”

Requirements

Compatibility (from SKILL.md): Requires Node, pnpm, and Playwright dependencies installed.

Workflow steps

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

Identify affected examples
Build each affected example
Run start and preview checks for each affected example
Browser-level acceptance criteria
Update or add E2E tests when needed

What it can do on your machine

Read from SKILL.md and the folder at commit 2000ef8. 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
Shell commands in SKILL.md call:
- npm
- pnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm and pnpm, which can reach the network depending on how they are called.
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.
Compatibility
Requires Node, pnpm, and Playwright dependencies installed.
From compatibility in the SKILL.md frontmatter.

Context cost

E2E Example Acceptance loads about 776 tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 253 words of instructions outside code blocks.

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

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 farm-fe/farm at commit 2000ef8, republished under its MIT licence (© farm-fe). 253 words, ~776 tokens.

Download SKILL.mdSave it as .claude/skills/e2e-example-acceptance/SKILL.md (or your agent's skills folder).

name: e2e-example-acceptance
description: Validate or update example-level E2E coverage. Use when adding/updating e2e.spec.ts, debugging example start/build/preview behavior, or verifying browser console/request errors and page expectations.
compatibility: Requires Node, pnpm, and Playwright dependencies installed.
license: MIT
metadata.author: farm
metadata.version: 1.0

Run example acceptance with executable checks for start/build/preview and browser behavior.

When to Use

Adding a new examples/<name>/e2e.spec.ts
Updating an existing E2E case for an example
Verifying regression fixes in an example before merge
Confirming no browser console/page/request anomalies during acceptance

Mandatory Acceptance Flow

Identify affected examples
- From changed files, collect all examples/<name>/... paths.
- If no explicit list is provided, ask for the intended scope.
Build each affected example
- cd examples/<name> && npm run build
Run start and preview checks for each affected example
- For examples with dedicated e2e.spec.ts, run targeted E2E:
- pnpm run test-e2e -- --example <name>
- For examples without a dedicated test, run smoke checks manually:
  - cd examples/<name> && npm run start
  - cd examples/<name> && npm run preview
Browser-level acceptance criteria
- Console: no unhandled error/pageerror messages.
- Network: no unexpected requestfailed entries.
- Content: assert key selectors/text that prove feature correctness.
Update or add E2E tests when needed
- Prefer dedicated examples/<name>/e2e.spec.ts for feature-specific behavior.
- Keep assertions deterministic; avoid brittle timing-only checks.
- Include both start and preview coverage unless the example is explicitly single-mode.

Authoring Template

import { basename, dirname } from "path";
import { fileURLToPath } from "url";
import { expect, startAndTest } from "../../e2e/index.js";

const name = basename(import.meta.url);
const projectPath = dirname(fileURLToPath(import.meta.url));

export default async function (ctx) {
  const runTest = (command?: "start" | "preview") =>
    startAndTest(
      projectPath,
      async (page) => {
        await page.waitForSelector("#root > *", { timeout: 10000 });
        // assert page content and absence of runtime anomalies
      },
      command,
    );

  await ctx.test("e2e start", () => runTest());
  await ctx.test("e2e preview", () => runTest("preview"));
}

Reporting Format

Examples: list of verified examples
Build: pass/fail per example
E2E Start: pass/fail per example
E2E Preview: pass/fail per example
Anomalies: console/request/pageerror summary
Notes: expected skips or known caveats

Guardrails

Do not rely only on build success; start/preview behavior must be observed.
Do not use pnpm run ready unless the user explicitly asks for full CI parity.
Do not edit generated dist/ files.
Use the new standalone E2E runner (see scripts/test-e2e.mts) — vitest is no longer involved.

Files

Just SKILL.md in .github/skills/e2e-example-acceptance of farm-fe/farm.

Open the folder on GitHubat commit 2000ef8

Compare with similar skills

E2E Example Acceptance 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 Example Acceptance compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
E2E Example Acceptance this skillfarm-fe/farm	5.6k	—	~776	Automated safety check: Pass	MIT	15 days ago
OpenHarness End-to-End EvalsHKUDS/OpenHarness	16k	1 repos	~2.1k	Automated safety check: Notes	MIT	4 mo ago
Qwen Code E2E TestingQwenLM/qwen-code	28k	—	~2.1k	Automated safety check: Pass	Apache-2.0	today
E2E TestingInsForge/InsForge	13k	—	~1.5k	Automated safety check: Pass	Apache-2.0	yesterday
RStudio Playwright Test Runnerrstudio/rstudio	5.1k	—	~801	Automated safety check: Pass	Custom licence	yesterday
tmux Real User TestingQwenLM/qwen-code	28k	—	~2.3k	Automated safety check: Pass	Apache-2.0	today

Similar skills

OpenHarness End-to-End Evals
HKUDS/OpenHarness
Validates OpenHarness features by running real multi-turn agent loops with live LLM calls against an unfamiliar codebase, checking actual tool execution.
16k GitHub starsUsed in 1 repo~2.1k tokens
Testing & QAAuto-check: notes
Qwen Code E2E Testing
QwenLM/qwen-code
Guides end-to-end testing of the Qwen Code CLI in headless mode with real model calls, MCP test servers and inspection of raw API traffic.
28k GitHub stars~2.1k tokensUpdated today
Testing & QAAuto-check passed
E2E Testing
InsForge/InsForge
A skill your agent uses when an InsForge maintainer has finished an OSS repo change and is ready to open, update, or submit the InsForge PR.
13k GitHub stars~1.5k tokensUpdated yesterday
Testing & QAAuto-check passed
RStudio Playwright Test Runner
rstudio/rstudio
Runs RStudio's Playwright end-to-end tests against the desktop app or a server build with the project's npm scripts, asking you which mode to use first.
5.1k GitHub stars~801 tokensUpdated yesterday
Testing & QAAuto-check passed
tmux Real User Testing
QwenLM/qwen-code
Drives Qwen Code in a real tmux session the way a user would and saves a readable step-by-step transcript of each screen for maintainers to review.
28k GitHub stars~2.3k tokensUpdated today
Testing & QAAuto-check passed
Interactive CLI Testing With tui-test
slopus/happy
Tests interactive CLI and TUI programs with Microsoft's tui-test, driving prompts, arrow keys and screen output in a real pseudo-terminal.
24k GitHub stars~603 tokensUpdated today
Testing & QAAuto-check passed

More from farm-fe/farm

All 20 skills in this repo

Using Superpowers
farm-fe/farm
A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
5.6k GitHub starsUsed in 34 repos~1.4k tokens
Auto-check passed
Finishing A Development Branch
farm-fe/farm
A skill your agent uses when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for…
5.6k GitHub starsUsed in 33 repos~1.8k tokens
Auto-check passed
Receiving Code Review
farm-fe/farm
A skill your agent uses when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and…
5.6k GitHub starsUsed in 44 repos~1.6k tokens
Auto-check passed
Rust Best Practices
farm-fe/farm
Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook.
5.6k GitHub starsUsed in 3 repos~1.1k tokens
Auto-check passed
Requesting Code Review
farm-fe/farm
A skill your agent uses when completing tasks, implementing major features, or before merging to verify work meets requirements
5.6k GitHub starsUsed in 37 repos~702 tokens
Auto-check passed
Verification Before Completion
farm-fe/farm
A skill your agent uses when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any…
5.6k GitHub starsUsed in 45 repos~1k tokens
Auto-check passed

Works with

Questions about E2E Example Acceptance

What does E2E Example Acceptance do?

Validate or update example-level E2E coverage. An agent skill from farm-fe/farm. E2E Example Acceptance is an agent skill from farm-fe/farm. Validate or update example-level E2E coverage.

When should I use E2E Example Acceptance?

E2E Example Acceptance fits situations like: adding/updating e2e.spec.ts; debugging example start/build/preview behavior; verifying browser console/request errors and page expectations.

How do I install E2E Example Acceptance in Claude Code?

Run `npx skills add farm-fe/farm --skill e2e-example-acceptance -a claude-code`. Or copy the skill folder (.github/skills/e2e-example-acceptance in farm-fe/farm) into .claude/skills/e2e-example-acceptance in your project. Claude Code loads it when a task matches its description.

How do I install E2E Example Acceptance in Codex?

Run `npx skills add farm-fe/farm --skill e2e-example-acceptance -a codex`. Or copy the skill folder (.github/skills/e2e-example-acceptance in farm-fe/farm) into .agents/skills/e2e-example-acceptance in your project. Codex loads it when a task matches its description.

Can I use E2E Example Acceptance 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 farm-fe/farm --skill e2e-example-acceptance -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-example-acceptance, .gemini/skills/e2e-example-acceptance, .github/skills/e2e-example-acceptance and .opencode/skills/e2e-example-acceptance in your project.

What does E2E Example Acceptance need to run?

Going by SKILL.md and its folder, E2E Example Acceptance needs the command-line tools its instructions call (npm and pnpm). Compatibility (from SKILL.md): Requires Node, pnpm, and Playwright dependencies installed..

Does E2E Example Acceptance access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is E2E Example Acceptance 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 Example Acceptance use?

E2E Example Acceptance is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does E2E Example Acceptance use?

About 776 tokens (SKILL.md is roughly 3.1k 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 Example Acceptance?

Skills that share tags, products or a category with E2E Example Acceptance: OpenHarness End-to-End Evals (HKUDS/OpenHarness, 16k stars), Qwen Code E2E Testing (QwenLM/qwen-code, 28k stars), E2E Testing (InsForge/InsForge, 13k stars) and RStudio Playwright Test Runner (rstudio/rstudio, 5.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains E2E Example Acceptance?

farm-fe (a GitHub organization) maintains it in farm-fe/farm, which has 5,594 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on September 22, 2026.

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

Install E2E Example Acceptance

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Compatibility

Context cost

Safety

SKILL.md

When to Use

Mandatory Acceptance Flow

Authoring Template

Reporting Format

Guardrails

Files

Compare with similar skills

Similar skills

More from farm-fe/farm

Related

Questions about E2E Example Acceptance