Index of every page on this site: llms.txt
All skills
e2e-inc avatar

/create-verification-skill

@a5d1788 #9 trending · Oct 2026
by e2ee2e-inc/e2e14k stars
782
Run it yourself

Generate a project-local verify-<app> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for /create-verification-skill, "make a verification skill for this repo", or when a project has no scripted way to prove UI behavior.

Use this Skill: https://skilld.dev/gh/e2e-inc/e2e/create-verification-skill

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesexampleverify-playgroundfeatureslogin.md

≈463 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Sign in and dashboard

A cookie session: sign in on /login, land on /dashboard, sign out.

Sub-features

  • Username and Password fields, Sign in button. A wrong password stays on /login and shows the Invalid credentials alert.
  • /dashboard greets the user in the Greeting status and offers Sign out; signed out, /dashboard redirects to /login.

How to get to it (user POV)

Nav link Login, or /login. Account: the admin credential in e2e.config.ts (never the password itself; type_secret over MCP, credentials.user('admin') in a test).

Driving it with e2e

tests/auth.setup.e2e.ts saves the admin session (a fill, so later screenshots are withheld) and admin-cookie (a cookie, screenshots stay); tests/dashboard.e2e.ts uses both and pins sign out and the wrong-password alert. Locators: screen.getByLabel('Username'), screen.getByLabel('Password'), screen.getByRole('button', 'Sign in'), screen.getByRole('alert'), screen.getByRole('status', 'Greeting'), screen.getByRole('link', 'Sign out').

Proof

The URL is /dashboard and Greeting reads Welcome back, admin!. Store: a session cookie exists (browser.cookies()); after sign out it is gone and /dashboard lands on /login.

Charters

login-errors|web|default|Starting at /login, try a wrong password, an unknown account, and an empty form; report errors that are missing, misleading, or leak detail

Signed in, run alone with --session admin-cookie:

dashboard-signout|web|skeptic|Starting at /dashboard signed in as admin, sign out and go back; report state that survives sign out

Gotchas

  • admin is the dev account the app ships with; its existence is not a finding. A charter that fills the password prints no screenshot evidence after it; use the cookie session to keep them.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning4d3 checks · Risk SAFE
  • Gen Agent Trust Hub4d

    This skill is used to generate sub-skills for application verification. It includes functionality to execute project-specific commands and generate new scripts, which is expected for developer tools. The primary security consideration is a low risk of indirect prompt injection, as the skill processes untrusted local code and documentation to generate instructions for subsequent agent actions.

  • Socket4d

    No alerts

  • Snyk4d

    Risk: MEDIUM · 2 issues

Signed by skilld at a5d1788. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 5 days ago
disable-model-invocation
true
Other metadata
metadata
{
  "openclaw": {
    "homepage": "https://e2e.com",
    "requires": {
      "bins": [
        "node",
        "npx"
      ]
    }
  }
}

README badge

README badge for e2e-inc/e2e/create-verification-skill