Skip to content
TrustedSkillsbeta
Back to all skills

E2E Testing Automation

Checked
aj-geddes·vlatest·testing·MIT

Helps with testing, automation as part of testing, debugging, and quality assurance workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add aj-geddes/useful-ai-prompts --skill e2e-testing-automation -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

aj-geddes

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned aj-geddes/useful-ai-prompts at 3f5182cfd7.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
3f5182cfd7
Manifest
skills/e2e-testing-automation/SKILL.md
Scanned
7 files, 542 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

The e2e-testing-automation skill enables AI agents to generate, execute, and maintain comprehensive end-to-end test suites across diverse web applications. It automates the verification of user workflows from start to finish, ensuring critical business logic remains intact after code changes.

When to use it

  • Validating complex multi-step user journeys involving several different pages or services.
  • Ensuring regression stability when integrating new features into an existing application.
  • Automating quality assurance checks for critical production deployments before release.
  • Verifying that third-party integrations and API interactions function correctly within the full application context.

Key capabilities

  • Generates executable end-to-end test scripts based on defined user stories or workflows.
  • Executes tests across various browser environments to ensure cross-browser compatibility.
  • Provides detailed reporting on test execution results, including pass/fail statuses and error logs.
  • Maintains test suites by automatically updating selectors when application UIs change slightly.

Example prompts

  • "Create an end-to-end test suite for the user registration flow on my React application."
  • "Run the existing e2e tests against the staging environment and summarize any failures."
  • "Update the current test scripts to include a new checkout process involving payment gateway integration."

Tips & gotchas

Ensure your target application has stable DOM elements or unique identifiers, as unstable selectors can cause frequent test failures. This skill is best suited for high-level workflow validation rather than testing internal unit logic or database transactions in isolation.