Skip to content
TrustedSkillsbeta
Back to all skills

E2E Tester

Checked
redpanda-data·vlatest·testing

The E2E Tester automatically executes end-to-end tests, ensuring application functionality across systems and saving valuable testing time.

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 redpanda-data/console --skill e2e-tester -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

redpanda-data

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 redpanda-data/console at 0d2c900a21.

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

Commit
0d2c900a21
Manifest
frontend/.claude/skills/e2e-tester/SKILL.md
Scanned
4 files, 498 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

e2e-tester

What it does

This skill enables AI agents to execute end-to-end testing workflows, validating system behavior from start to finish. It automates the verification of complex user journeys and ensures application stability across various environments.

When to use it

  • Validating critical user flows in production-like environments before deployment.
  • Automating regression testing suites to catch unintended side effects from code changes.
  • Verifying integration points between different microservices or external APIs.
  • Ensuring compliance with specific business logic rules across the entire application stack.

Key capabilities

  • Executes comprehensive end-to-end test scenarios automatically.
  • Validates full system workflows rather than isolated components.
  • Provides feedback on the success or failure of complex user journeys.

Example prompts

  • "Run an end-to-end test for the new checkout flow to ensure payment processing works correctly."
  • "Execute a regression suite covering all critical paths in the user dashboard."
  • "Verify that the data synchronization between the frontend and backend APIs functions as expected during peak load."

Tips & gotchas

Ensure your test environment mirrors production closely to get accurate results. Limit initial runs to critical paths to avoid excessive execution time or resource consumption.