Skip to content
TrustedSkillsbeta
Back to all skills

E2E Testing

Checked
hieutrtr·vlatest·testing

Automates end-to-end user flows, identifying bugs and performance bottlenecks across entire application workflows.

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 hieutrtr/ai1-skills --skill e2e-testing -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

hieutrtr

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 hieutrtr/ai1-skills at d8244c1acd.

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

Scanned
5 files, 1,046 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

What it does

The e2e-testing skill enables AI agents to perform end-to-end testing of web applications, ensuring that all components work together as intended from the user's perspective. It automates interactions with web pages, validates expected outcomes, and identifies issues in workflows or integrations.

When to use it

  • Testing a full user journey on a web application, such as logging in, making a purchase, and checking order confirmation.
  • Validating that API calls and front-end components work together correctly after code changes.
  • Ensuring that new features are fully functional across different browsers or devices before deployment.

Key capabilities

  • Automates browser interactions (e.g., clicking buttons, filling forms).
  • Validates page content and responses against expected results.
  • Supports testing of complex workflows involving multiple pages or services.

Example prompts

  • "Run end-to-end tests for the user registration flow on the website."
  • "Test if the login button redirects to the dashboard after successful authentication."
  • "Verify that the payment process completes without errors using a test credit card."

Tips & gotchas

  • Ensure that the web application is accessible and stable during testing.
  • Some tests may require specific environments or dependencies, such as a running server or mock APIs.