agentleFS
kyto64kyto64/aidd-template-scale/.claude/skills/agentic-e2e/SKILL.md

agentic-e2e

Skill0 starsChanged 2 months agoMITView on GitHub

E2E UI verification via headless Chrome and CDP. Requires stack-paths.md and a running app.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If any required field is empty → STOP.

    line 14
  2. Distinctive:

    Stop Chrome when done.

    line 26
  3. Distinctive:

    Do not store credentials in scripts.

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Agentic E2E

User request: $ARGUMENTS

Gate: stack-paths.md

  1. Read docs/development/stack-paths.md
  2. If any required field is empty → STOP.

Gate: OS support

Supported for Linux and WSL only (see skill README in repo). On other OS, stop and ask user to run manual browser tests.

Steps

  1. Confirm app is running (start_command / local_base_url).
  2. Launch Chrome: .claude/skills/agentic-e2e/launch_chrome.sh
  3. Drive UI: node .claude/skills/agentic-e2e/cdp_drive.mjs --url "<url>" --expect "<text>"
  4. Report pass/fail with screenshot path if script provides one.
  5. Stop Chrome when done.

Notes

  • Do not store credentials in scripts; use test accounts via env vars your project defines.
  • This skill does not replace full E2E suites — use for targeted agent verification.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.