Foreman Web Testing

Organization

VisionForge-OU

foreman-web-testing

Headless end-to-end / web-app testing for the Foreman e2e stage. Derive end-to-end tests from the PRD's User Flows, drive the real application the way a user would (browser flows, screenshots, accessibility checks for web apps), make them pass via the configured e2e command, and emit the FOREMAN-SUMMARY block Foreman parses.

Overview

Publisher	VisionForge-OU
Repository	`foreman`
Skill name	`foreman-web-testing`
Stars	444
Forks	117
Bundled files	Instructions only
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by VisionForge-OU on GitHub. Read the source before you install it.

Installation

Install the Foreman Web Testing AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/VisionForge-OU/foreman/tree/main/src/foreman/skills/foreman-web-testing
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/VisionForge-OU/foreman/tree/main/src/foreman/skills/foreman-web-testing

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/VisionForge-OU/foreman.git /tmp/foreman
mkdir -p .claude/skills
cp -r /tmp/foreman/src/foreman/skills/foreman-web-testing .claude/skills/foreman-web-testing

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Foreman Web Testing in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Foreman Web Testing on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Foreman Web Testing is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

foreman-web-testing

(Adapted from Anthropic's web-app-testing skill and the e2e half of foreman-tdd — see NOTICE. Made stack-agnostic: the e2e runner is injected by Foreman from config.yaml (commands.e2e), not hard-coded to Playwright; for non-browser projects the same flow-driven discipline applies through whatever e2e command the project declares. Added Foreman's evidence + FOREMAN-SUMMARY contract.)

You run headless in the integration worktree after every issue has landed. Your job is to prove the whole feature works end-to-end along the journeys the PRD promised — not to re-run unit tests. Implement the e2e tests, make them pass, save evidence, then stop with exactly one FOREMAN-SUMMARY block.

Inputs (injected by Foreman in the prompt)

The approved PRD body — its ## User Flows section is your test charter.
The e2e command for the project (commands.e2e, e.g. npx playwright test or pytest -m e2e). Foreman re-runs it itself to verify, so your tests must actually pass under it.
The evidence directory you must populate before claiming done.

Workflow

1. Derive flows from the PRD

Turn each user flow into a concrete end-to-end scenario: the precondition, the steps a real user takes, and the observable outcome ("given A, when B, then C"). Cover the happy path and the obvious failure path the flow implies (invalid input, empty state, permission denied). Do not test through internal functions — exercise the application through its real surface (the running web app, the CLI, the HTTP API).

2. Drive the real application

Web apps: drive a real browser with the project's e2e tooling. Interact the way a user does — locate elements by role/label/text, not brittle CSS nth-child paths; wait on a real condition (an element, a network response), never a fixed sleep. Check the basics a user would feel: the page renders, the primary action works, no console errors, and reasonable accessibility (labelled controls, focus order).
Non-web: drive the same flow through the configured e2e command's surface (API requests, CLI invocations), asserting on real observable output.

Capture a screenshot (or output transcript) per flow as you go — these are your evidence.

3. Make them pass, then verify

Run the e2e command and read its output. Iterate until every derived flow passes. A flow that can't be made to pass because the shipped feature doesn't actually deliver it is a real finding — report it (see escalation below) rather than weakening the test to go green.

4. Save evidence and summarise

Save into the evidence directory Foreman gave you: the e2e run log, and a screenshot (web) or output transcript (non-web) per flow. List every artifact in the FOREMAN-SUMMARY evidence array — an unbacked completion claim is rejected, and Foreman re-runs the e2e command itself regardless of what you claim.

Required output: FOREMAN-SUMMARY

End with exactly one fenced json block, issue_id: "e2e", on Foreman's foreman-summary/v1 schema (same shape foreman-tdd emits): files_touched, tests_added, commands.e2e (ran/passed/output_tail), evidence, open_concerns, and — if a promised flow genuinely cannot pass against the shipped feature — escalate: true with a one-line escalation_question. Set escalate: false when the flows pass. Nothing after the block.

Frequently asked questions

What does the Foreman Web Testing AI skill do?

Why use Foreman Web Testing on TypingMind?

Because you install it once and use it with any model. Foreman Web Testing is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Foreman Web Testing in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/VisionForge-OU/foreman/tree/main/src/foreman/skills/foreman-web-testing. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Foreman Web Testing?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Foreman Web Testing?

As many as you like. As long as a model supports skills, you can use Foreman Web Testing with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Foreman Web Testing AI skill free?

It is published on GitHub by VisionForge-OU. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Skill Creator

anthropics

OrganizationPopular

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a…

E2e Cucumber Playwright

langgenius

OrganizationPopular

Use when writing, changing, or reviewing Cucumber and Playwright tests under `e2e/`, including feature files, step definitions, support code, scenario tags, locators, and assertions. Do not use for…

Channel Message Flows

openclaw

OrganizationPopular

Use when running QA Lab channel message flow evidence.

Claw Score

Audit or refresh OpenClaw maturity scorecard docs from root taxonomy, maturity scores, and QA evidence artifacts without using maintainer discrawl data or committed inventory reports.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

foreman-web-testing

Inputs (injected by Foreman in the prompt)

Workflow

1. Derive flows from the PRD

2. Drive the real application

3. Make them pass, then verify

4. Save evidence and summarise

Required output: FOREMAN-SUMMARY

Frequently asked questions

Related AI Skills

Set up your own AI workspace now