Agent skill

E2E Verify

API/CLI-level E2E test writing and execution after development, for E2E that needs no browser automation.

No licenceAuto-check: notesTesting & QA

Install E2E Verify

skills CLI

$ npx skills add jh941213/my-cc-harness --skill e2e-verify -a claude-code

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

GitHub CLI

$ gh skill install jh941213/my-cc-harness e2e-verify --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/jh941213/my-cc-harness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills_en/e2e-verify .claude/skills/e2e-verify && 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-verify" agent skill from https://github.com/jh941213/my-cc-harness/tree/main/skills_en/e2e-verify into .claude/skills/e2e-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "e2e-verify", 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/jh941213/my-cc-harness/tree/main/skills_en/e2e-verify

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 jh941213/my-cc-harness --skill e2e-verify -a codex

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

GitHub CLI

$ gh skill install jh941213/my-cc-harness e2e-verify --agent codex

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

Manual copy

$ git clone --depth 1 https://github.com/jh941213/my-cc-harness.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills_en/e2e-verify .agents/skills/e2e-verify && 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-verify" agent skill from https://github.com/jh941213/my-cc-harness/tree/main/skills_en/e2e-verify into .agents/skills/e2e-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "e2e-verify", 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 jh941213/my-cc-harness --skill e2e-verify -a cursor

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

GitHub CLI

$ gh skill install jh941213/my-cc-harness e2e-verify --agent cursor

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

Manual copy

$ git clone --depth 1 https://github.com/jh941213/my-cc-harness.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills_en/e2e-verify .cursor/skills/e2e-verify && 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-verify" agent skill from https://github.com/jh941213/my-cc-harness/tree/main/skills_en/e2e-verify into .cursor/skills/e2e-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "e2e-verify", 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/jh941213/my-cc-harness.git --path skills_en/e2e-verify

--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 jh941213/my-cc-harness --skill e2e-verify -a gemini-cli

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

GitHub CLI

$ gh skill install jh941213/my-cc-harness e2e-verify --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/jh941213/my-cc-harness.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills_en/e2e-verify .gemini/skills/e2e-verify && 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-verify" agent skill from https://github.com/jh941213/my-cc-harness/tree/main/skills_en/e2e-verify into .gemini/skills/e2e-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "e2e-verify", 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 jh941213/my-cc-harness e2e-verify

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 jh941213/my-cc-harness --skill e2e-verify -a github-copilot

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

Manual copy

$ git clone --depth 1 https://github.com/jh941213/my-cc-harness.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills_en/e2e-verify .github/skills/e2e-verify && 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-verify" agent skill from https://github.com/jh941213/my-cc-harness/tree/main/skills_en/e2e-verify into .github/skills/e2e-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "e2e-verify", 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 jh941213/my-cc-harness --skill e2e-verify -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 jh941213/my-cc-harness e2e-verify --agent opencode

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

Manual copy

$ git clone --depth 1 https://github.com/jh941213/my-cc-harness.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills_en/e2e-verify .opencode/skills/e2e-verify && 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-verify" agent skill from https://github.com/jh941213/my-cc-harness/tree/main/skills_en/e2e-verify into .opencode/skills/e2e-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "e2e-verify", 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-verify
GitHub stars: 126
Token cost: ~940 tokens
SKILL.md length: 139 words
Files: 1
Skills in repo: 62
Repo updated: Aug 3, 2026
First seen: Oct 7, 2026
Licence: None found

At a glance

API/CLI-level E2E test writing and execution after development, for E2E that needs no browser automation.

Works in 5 steps: Feature Analysis → Run the App → Write E2E Tests → …
: e2e verification
SKILL.md covers Prerequisites, Workflow, Test Checklist and Verification Loop
Calls curl, npx and npm

What it does

E2E Verify is an agent skill from jh941213/my-cc-harness. API/CLI-level E2E test writing and execution after development, for E2E that needs no browser automation. Verifies actual user flows after /verify. Use the e2e-agent-browser skill when browser automation is needed. Triggers on: e2e verification, e2e-verify, E2E testing. NOT for: unit tests, type checking, build verification, browser-automation E2E.

Its SKILL.md is about 940 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 and Browser automation.

When your agent uses it

: e2e verification
Tasks that involve End-to-end testing
Tasks that involve Browser automation

Example prompts

“/e2e-verify”

Requirements

Node.js
Pre-approved tools (allowed-tools): Read, Write, Edit, Bash, Grep, Glob, Task

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Feature Analysis
Run the App
Write E2E Tests
Run Tests
Debug on Failure

What it can do on your machine

Read from SKILL.md and the folder at commit e9210e2. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Read
- Write
- Edit
- Bash
- Grep
- Glob
- Task
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- curl
- npx
- npm
- bash
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use curl, npx and npm, 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.

Context cost

E2E Verify loads about 940 tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 139 words of instructions outside code blocks.

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

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
```
allowed-tools: Read, Write, Edit, Bash, Grep, Glob, Task
```

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 139 words (~940 tokens).

“After development + /verify completion, verifies that the implemented feature works in an actual browser via E2E tests.”

— opening of SKILL.md by jh941213

name: e2e-verify
allowed-tools: Read, Write, Edit, Bash, Grep, Glob, Task
user-invocable: true
disable-model-invocation: false

Read the full SKILL.md on GitHub

Files

Just SKILL.md in skills_en/e2e-verify of jh941213/my-cc-harness.

Open the folder on GitHubat commit e9210e2

Compare with similar skills

E2E Verify 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 Verify compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
E2E Verify this skilljh941213/my-cc-harness	126	—	~940	Automated safety check: Notes	None	2 mo ago
E2E Flow Verifierproffesor-for-testing/agentic-qe	494	—	~1.1k	Automated safety check: Pass	MIT	4 days ago
playwright-cli Browser Automationgithub/gh-aw	5.4k	24 repos	~2.8k	Automated safety check: Pass	MIT	today
Kane CLI Browser TestingLambdaTest/kane-cli	247	—	~8.4k	Automated safety check: Pass	Apache-2.0	3 days ago
Playwright E2E Testingactivepieces/activepieces	25k	—	~6.8k	Automated safety check: Pass	Custom licence	today
Test Electron AppPostHog/code	179	—	~2.9k	Automated safety check: Pass	MIT	2 mo ago

Similar skills

E2E Flow Verifier
proffesor-for-testing/agentic-qe
A skill your agent uses when verifying complete user flows end-to-end with the qe-browser skill (Vibium), recording session evidence, and asserting state at each step.
494 GitHub stars~1.1k tokensUpdated 4 days ago
Testing & QAAuto-check passed
playwright-cli Browser Automation
github/gh-aw
Official
Drives a real browser from the command line with playwright-cli to open pages, interact, mock requests, save state and work with Playwright tests.
5.4k GitHub starsUsed in 24 repos~2.8k tokens
Testing & QAAuto-check passed
Kane CLI Browser Testing
LambdaTest/kane-cli
Drives a real browser through the kane-cli tool and designs requirement-linked test suites from a PRD or a plain description, with mobile and cloud-grid runs.
247 GitHub stars~8.4k tokensUpdated 3 days ago
Testing & QAAuto-check passed
Playwright E2E Testing
activepieces/activepieces
Playwright modern end-to-end testing framework with cross-browser automation, auto-wait, and built-in test runner
25k GitHub stars~6.8k tokensUpdated today
Testing & QAAuto-check passed
Test Electron App
PostHog/code
Official
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser.
179 GitHub stars~2.9k tokensUpdated 2 mo ago
Testing & QAAuto-check passed
Test Electron App
PostHog/posthog
Official
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser.
40k GitHub stars~3k tokensUpdated today
Testing & QAAuto-check passed

Questions about E2E Verify

What does E2E Verify do?

API/CLI-level E2E test writing and execution after development, for E2E that needs no browser automation. E2E Verify is an agent skill from jh941213/my-cc-harness. API/CLI-level E2E test writing and execution after development, for E2E that needs no browser automation.

When should I use E2E Verify?

E2E Verify fits situations like: : e2e verification; tasks that involve End-to-end testing; tasks that involve Browser automation.

How do I install E2E Verify in Claude Code?

Run `npx skills add jh941213/my-cc-harness --skill e2e-verify -a claude-code`. Or copy the skill folder (skills_en/e2e-verify in jh941213/my-cc-harness) into .claude/skills/e2e-verify in your project. Claude Code loads it when a task matches its description.

How do I install E2E Verify in Codex?

Run `npx skills add jh941213/my-cc-harness --skill e2e-verify -a codex`. Or copy the skill folder (skills_en/e2e-verify in jh941213/my-cc-harness) into .agents/skills/e2e-verify in your project. Codex loads it when a task matches its description.

Can I use E2E Verify 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 jh941213/my-cc-harness --skill e2e-verify -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-verify, .gemini/skills/e2e-verify, .github/skills/e2e-verify and .opencode/skills/e2e-verify in your project.

What does E2E Verify need to run?

Going by SKILL.md and its folder, E2E Verify needs the command-line tools its instructions call (curl, npx, npm and bash). Our summary lists: Node.js. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash, Grep, Glob, Task.

Does E2E Verify access the network?

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

Is E2E Verify safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does E2E Verify use?

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

How many tokens does E2E Verify use?

About 940 tokens (SKILL.md is roughly 3.8k 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 Verify?

Skills that share tags, products or a category with E2E Verify: E2E Flow Verifier (proffesor-for-testing/agentic-qe, 494 stars), playwright-cli Browser Automation (github/gh-aw, 5.4k stars), Kane CLI Browser Testing (LambdaTest/kane-cli, 247 stars) and Playwright E2E Testing (activepieces/activepieces, 25k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains E2E Verify?

jh941213 (a GitHub user) maintains it in jh941213/my-cc-harness, which has 126 GitHub stars. The repository holds 62 skills in this directory. The repository was last updated on August 3, 2026.

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

E2E Verify

Install E2E Verify

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

Context cost

Safety

SKILL.md

Files

Compare with similar skills

Similar skills

E2E Flow Verifier

playwright-cli Browser Automation

Kane CLI Browser Testing

Playwright E2E Testing

Test Electron App

Test Electron App

More from jh941213/my-cc-harness

API Design Principles

Tailwind Design System

Docs Architecture

Auto Memory

Async Python Patterns

Python Testing Patterns

Questions about E2E Verify

Install E2E Verify

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

Context cost

Safety

SKILL.md

Files

Compare with similar skills

Similar skills

More from jh941213/my-cc-harness

Related

Questions about E2E Verify