New: 97,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 Testing

by InsForge in 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.

Apache-2.0Auto-check passedTesting & QA

Install E2E Testing

skills CLI
$ npx skills add InsForge/InsForge --skill e2e-testing -a claude-code

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

GitHub CLI
$ gh skill install InsForge/InsForge e2e-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/InsForge/InsForge.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/insforge-dev/e2e-testing .claude/skills/e2e-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-testing
GitHub stars
13k
Token cost
~1.5k tokens
SKILL.md length
705 words
Files
1
Skills in repo
8
Repo updated
First seen
Licence
Apache-2.0

At a glance

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.

  • Works in 3 steps: Read the root InsForge package.json… → Increment only the patch number. → Build a tag in this form
  • An InsForge maintainer has finished an OSS repo change and is ready to open
  • SKILL.md covers Repositories, Build The Test Tag, Build The InsForge Image and Decide Whether agent-e2e Must…, plus 4 more sections
  • Calls gh and npm; reaches github.com

What it does

E2E Testing is an agent skill from InsForge/InsForge. Use this skill when an InsForge maintainer has finished an OSS repo change and is ready to open, update, or submit the InsForge PR. Runs the release-quality deterministic E2E gate by building a package.json-derived InsForge test image tag, deciding whether sibling agent-e2e fixture coverage must change, dispatching the Deterministic Fixture E2E workflow, waiting for results, and triaging failures before PR submission.

Its SKILL.md is about 1.5k 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. It works with npm. The repository describes itself as: The all-in-one, open-source backend platform for agentic coding. InsForge gives your coding agent database, auth, storage, compute, hosting, and AI gateway to ship full-stack… The licence is Apache-2.0.

When your agent uses it

  • An InsForge maintainer has finished an OSS repo change and is ready to open
  • Submit the InsForge PR

Example prompts

  • “/e2e-testing”

Requirements

  • Docker

Workflow steps

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

  1. Read the root InsForge package.json version.
  2. Increment only the patch number.
  3. Build a tag in this form

What it can do on your machine

Read from SKILL.md and the folder at commit 2ec64b6. 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:

    • gh
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    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 Testing loads about 1.5k tokens when it runs. Until then it costs about 108 tokens; SKILL.md has 705 words of instructions outside code blocks.

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

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 InsForge/InsForge at commit 2ec64b6, republished under its Apache-2.0 licence (© InsForge). 705 words, ~1,524 tokens.

Download SKILL.mdSave it as .claude/skills/e2e-testing/SKILL.md (or your agent's skills folder).
name
e2e-testing
description
Use this skill when an InsForge maintainer has finished an OSS repo change and is ready to open, update, or submit the InsForge PR. Runs the release-quality deterministic E2E gate by building a package.json-derived InsForge test image tag, deciding whether sibling agent-e2e fixture coverage must change, dispatching the Deterministic Fixture E2E workflow, waiting for results, and triaging failures before PR submission.

InsForge E2E Testing Gate

Use this skill after local implementation and normal InsForge pre-PR checks pass, and before opening, updating, or submitting the InsForge OSS PR.

This is an additional release-quality gate. It does not replace local typecheck, lint, test, or build validation from the parent insforge-dev skill.

Repositories

  • InsForge OSS repo: current workspace.
  • E2E repo: remote GitHub repository InsForge/agent-e2e.

Use the remote InsForge/agent-e2e repository for workflow dispatch and read-only workflow checks. Do not rely on a developer-specific local checkout path. Create or use a local checkout only when the deterministic fixture tests must be edited.

Build The Test Tag

  1. Read the root InsForge package.json version.
  2. Increment only the patch number.
  3. Build a tag in this form:
text
v<major>.<minor>.<patch+1>-<feature-or-issue-slug>

Example: root version 2.2.3 and feature storage returning rls becomes v2.2.4-storage-returning-rls.

Use the package.json version as the only source of truth for the base version. Ignore higher existing test tags when calculating the base version.

Slug rules:

  • Prefer the issue key, PR topic, or branch topic.
  • Lowercase all letters.
  • Replace runs of non-alphanumeric characters with one hyphen.
  • Trim leading and trailing hyphens.
  • Keep it short enough to scan in GitHub Actions and image tags.

Build The InsForge Image

Dispatch the InsForge Build and Push Docker Image workflow with the test tag:

bash
gh workflow run "Build and Push Docker Image" --repo InsForge/InsForge --ref <insforge-feature-branch> -f test_tag=<test-tag>

Then wait for the matching run to complete:

bash
gh run list --repo InsForge/InsForge --workflow "Build and Push Docker Image" --limit 10
gh run watch --repo InsForge/InsForge <run-id>

Do not start the cross-repo E2E workflow until the image build succeeds.

Decide Whether agent-e2e Must Change

Inspect the InsForge diff and compare it with deterministic fixture coverage in InsForge/agent-e2e.

For read-only checks, prefer remote GitHub access such as gh api, gh repo view, or remote file reads. Use a local checkout only when editing fixture files or when remote inspection is not enough to understand coverage.

Update agent-e2e when the InsForge change adds, removes, or changes behavior that the deterministic fixture should assert, including:

  • API contract or validation behavior.
  • Auth, permissions, RLS, storage, realtime, functions, schedules, AI, SDK, or CLI-visible behavior.
  • Any regression that local tests cover but the release gate should also protect across the deployed runtime.

Do not update agent-e2e for internal refactors, docs-only changes, local test-only changes, or behavior already covered by the deterministic fixture with no assertion change needed.

Ignore Support Desk Agent E2E (Exploratory). It is not part of this gate.

If No E2E Test Update Is Needed

Run the deterministic fixture workflow from agent-e2e main:

bash
gh workflow run "Deterministic Fixture E2E" --repo InsForge/agent-e2e --ref main -f insforge_tag=<test-tag>

Find and watch the run:

bash
gh run list --repo InsForge/agent-e2e --workflow "Deterministic Fixture E2E" --limit 10
gh run watch --repo InsForge/agent-e2e <run-id>
Show full SKILL.md (309 more words)Show less

If E2E Tests Need An Update

Work in a local checkout of the remote InsForge/agent-e2e repo only for the fixture update.

  1. Use an existing clean checkout or clone https://github.com/InsForge/agent-e2e.git into an isolated workspace.
  2. Fetch origin and start from origin/main.
  3. Create a branch named codex/<short-topic>.
  4. Update only the deterministic fixture validators, fixtures, app assertions, and docs needed for the InsForge behavior change.
  5. Run the smallest local validation that gives confidence:
bash
npm run typecheck
npm run lint
npm run fixture:e2e:dry

Run broader validation when the changed fixture area supports it.

  1. Open an agent-e2e PR for the fixture update.
  2. Dispatch the deterministic fixture workflow from the agent-e2e branch that contains the fixture update:
bash
gh workflow run "Deterministic Fixture E2E" --repo InsForge/agent-e2e --ref <agent-e2e-branch> -f insforge_tag=<test-tag>
  1. Watch the run before proceeding with the InsForge PR.

Interpret Results

If the deterministic fixture workflow passes:

  • Link the run in the InsForge PR body or final PR notes.
  • If an agent-e2e PR was required, link that PR too.
  • Proceed with opening, updating, or submitting the InsForge OSS PR.

If the deterministic fixture workflow fails:

  1. Inspect the failed job logs and uploaded artifact.
  2. Identify whether the failure is caused by the InsForge implementation, the new or existing deterministic fixture, a transient infrastructure problem, or an unrelated existing failure.
  3. Fix the correct branch:
    • InsForge implementation bug: update the InsForge branch, rebuild the test image with the same tag or a new short retry tag, then rerun E2E.
    • Fixture bug or missing assertion update: update the agent-e2e branch, rerun local validation, then rerun E2E from that branch.
    • Transient infrastructure issue: rerun once after noting the evidence.
  4. Do not submit the InsForge PR until the deterministic result is clear or the user explicitly accepts the risk.

Report Back

When finished, report:

  • Test tag used.
  • InsForge image workflow run result.
  • Whether agent-e2e changed.
  • Deterministic Fixture E2E run result.
  • Links to the InsForge PR, agent-e2e PR if any, and workflow runs.

© InsForge, 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

Just SKILL.md in .codex/skills/insforge-dev/e2e-testing of InsForge/InsForge.

Open the folder on GitHubat commit 2ec64b6

Compare with similar skills

E2E 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 Testing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
E2E Testing this skillInsForge/InsForge13k—~1.5kAutomated safety check: PassApache-2.0
OpenHarness End-to-End EvalsHKUDS/OpenHarness16k1 repos~2.1kAutomated safety check: NotesMIT
Qwen Code E2E TestingQwenLM/qwen-code28k—~2.1kAutomated safety check: PassApache-2.0
RStudio Playwright Test Runnerrstudio/rstudio5.1k—~801Automated safety check: PassCustom licence
tmux Real User TestingQwenLM/qwen-code28k—~2.3kAutomated safety check: PassApache-2.0
Interactive CLI Testing With tui-testslopus/happy24k—~603Automated safety check: PassMIT

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

  • 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 today
    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

  • Playwright

    Kiln-AI/Kiln

    Look at Kiln's UI in a real browser, and run its end-to-end tests.

    5.2k GitHub stars~1.3k tokensUpdated today
    Testing & QAAuto-check passed

More from InsForge/InsForge

All 8 skills in this repo

  • Doc Author

    InsForge/InsForge

    Write, edit, and maintain documentation. An agent skill from InsForge/InsForge.

    13k GitHub stars~3.7k tokensUpdated today
    Auto-check passed

  • Backend

    InsForge/InsForge

    A skill your agent uses when contributing to InsForge's backend package.

    13k GitHub stars~1.7k tokensUpdated today
    Auto-check passed

  • Dashboard

    InsForge/InsForge

    A skill your agent uses when contributing to InsForge's shared dashboard package.

    13k GitHub stars~2.3k tokensUpdated today
    Auto-check passed

  • Docs

    InsForge/InsForge

    A skill your agent uses when contributing to InsForge's product documentation in this repository.

    13k GitHub stars~761 tokensUpdated today
    Auto-check passed

  • Insforge Dev

    InsForge/InsForge

    Use this skill set when contributing to the InsForge monorepo itself.

    13k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Shared Schemas

    InsForge/InsForge

    A skill your agent uses when contributing to InsForge's shared schema package.

    13k GitHub stars~628 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about E2E Testing

What does E2E Testing do?

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. E2E Testing is an agent skill from InsForge/InsForge. Use this skill when an InsForge maintainer has finished an OSS repo change and is ready to open, update, or submit the InsForge PR.

When should I use E2E Testing?

E2E Testing fits situations like: an InsForge maintainer has finished an OSS repo change and is ready to open; submit the InsForge PR.

How do I install E2E Testing in Claude Code?

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

How do I install E2E Testing in Codex?

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

Can I use E2E 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 InsForge/InsForge --skill e2e-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-testing, .gemini/skills/e2e-testing, .github/skills/e2e-testing and .opencode/skills/e2e-testing in your project.

What does E2E Testing need to run?

Going by SKILL.md and its folder, E2E Testing needs the command-line tools its instructions call (gh and npm). Our summary lists: Docker.

Does E2E Testing access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

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

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

About 1.5k tokens (SKILL.md is roughly 6.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 Testing?

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

Who maintains E2E Testing?

InsForge (a GitHub organization) maintains it in InsForge/InsForge, which has 13,064 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 6, 2026.

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