Skip to content
TrustedSkillsbeta
Back to all skills

Shadow Testing

Listed
rysweet·vlatest·testing

Simulates user interactions against live systems to proactively identify bugs and performance bottlenecks without impacting real users.

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 rysweet/amplihack --skill shadow-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

rysweet

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 failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No pipe-to-shell installers: failed

    Runs code fetched at install time in 11 places.

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

    What it found (3 of 11)

    • .claude/skills/shadow-testing/README.md:159pip install straight from a URL
      pip install git+https://github.com/org/my-lib &&
    • .claude/skills/shadow-testing/README.md:174pip install straight from a URL
      amplifier-shadow exec multi-test "pip install git+https://github.com/org/cli"
    • .claude/skills/shadow-testing/SKILL.md:131pip install straight from a URL
      amplifier-shadow exec test-lib "uv pip install git+https://github.com/myorg/my-library"

  • 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

    Only contacts known or declared hosts: github.com.

    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.

    Hosts contacted

    github.comsource host

  • 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.

  • Pinned to a commit: passed

    Scanned rysweet/amplihack at 84424457d5.

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

Commit
84424457d5
Manifest
.claude/skills/shadow-testing/SKILL.md
Scanned
12 files, 2,237 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 shadow-testing skill enables AI agents to perform automated testing in isolated environments, often referred to as "shadow mode." It allows agents to validate code changes or system behaviors without disrupting live production services.

When to use it

  • You need to verify a new feature works correctly before merging it into the main branch.
  • You want to run performance benchmarks on a specific configuration without affecting real users.
  • You are debugging an issue and need to simulate traffic patterns safely.
  • Your team requires a safety net to prevent regression bugs from reaching production.

Key capabilities

  • Executes test suites in isolated shadow environments.
  • Validates system behavior against expected outcomes without live impact.
  • Supports automated verification of code changes prior to deployment.
  • Provides feedback on potential issues before they affect production systems.

Example prompts

  • "Run a full regression test suite in shadow mode for the new checkout flow."
  • "Simulate high-traffic load testing on the API endpoints without impacting live users."
  • "Validate the latest database migration script in an isolated environment first."

Tips & gotchas

Ensure your agent has read-only access to the target systems to prevent accidental data modification during shadow tests. Always review test logs carefully, as failures in shadow mode may still indicate critical logic errors that require immediate attention.