Skip to content
TrustedSkillsbeta
Back to all skills

E2E Test Writer

Checked
matteocervelli·vlatest·testing·MIT

Generates comprehensive end-to-end test cases from user stories and specifications for software applications.

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 matteocervelli/llms --skill e2e-test-writer --full-depth -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

matteocervelli

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 matteocervelli/llms at 1e1f2089eb.

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

Commit
1e1f2089eb
Manifest
.archive/claude-v1/skills/e2e-test-writer/SKILL.md
Scanned
1 file, 701 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-test-writer skill generates end-to-end tests based on user descriptions. It can create test cases for web applications, APIs, and other software systems. The generated tests are designed to verify the functionality of a system from start to finish, simulating real user interactions.

When to use it

  • Automating Regression Testing: Quickly generate initial test suites when making changes to an application.
  • New Feature Verification: Create comprehensive tests for newly developed features before release.
  • API Integration Testing: Develop tests that validate the interaction between different APIs or services.
  • User Journey Simulation: Generate tests that mimic specific user workflows through a system.

Key capabilities

  • Generates end-to-end test cases
  • Supports web applications and APIs
  • Creates tests based on textual descriptions

Example prompts

  • "Write an e2e test for logging in to my application with valid credentials."
  • "Generate a test case for adding a new product to the shopping cart on my website."
  • "Create an end-to-end test that verifies the API call to retrieve user data."

Tips & gotchas

The quality of generated tests depends heavily on the clarity and detail provided in the prompt. Be specific about expected inputs, outputs, and system behavior for best results.