Skip to content
TrustedSkillsbeta
Back to all skills

E2E Test Builder

Checked
patricio0312rev·vlatest·testing·MIT

Automatically generates comprehensive end-to-end test suites based on user requirements and system specifications.

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 patricio0312rev/skills --skill e2e-test-builder -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

patricio0312rev

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 patricio0312rev/skills at 79ea6af485.

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

Scanned
1 file, 367 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-test-builder skill enables AI agents to generate, execute, and manage end-to-end testing workflows. It automates the creation of comprehensive test suites that verify application functionality from start to finish without manual intervention.

When to use it

  • Automating regression testing for critical user journeys in web or mobile applications.
  • Validating complex multi-step workflows involving different system components.
  • Rapidly generating test cases based on updated requirements or new feature deployments.
  • Ensuring consistent coverage across various environments and device configurations.

Key capabilities

  • Automated generation of end-to-end test scripts.
  • Execution of full application lifecycle tests.
  • Integration with existing CI/CD pipelines for continuous validation.
  • Support for diverse testing frameworks and tools.

Example prompts

"Create an end-to-end test suite for the user login flow on my web application." "Generate automated tests to verify the checkout process across different browser devices." "Build a comprehensive e2e test plan that covers all major user scenarios in our mobile app."

Tips & gotchas

Ensure your target applications have stable APIs and clear entry points for reliable automation. Limit initial test scope to core functionalities until the framework stabilizes.