Wreck Explore
Explore a running local web app through Playwright MCP as a normal user (every core flow plus data-integrity checks) and then in character as each persona from .wreck-it/personas.md, recording reproducible bugs with wreck-it. Use as stages 4–5 of a wreck-it run, or when the user asks to "click through my app like a user", "test the happy paths", "try my app as a beginner", or "check my core flows".
Install
/plugin marketplace add miyannishar/wreck-itThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add miyannishar/wreck-it --skill wreck-exploregit clone --depth 1 https://github.com/miyannishar/wreck-it.git /tmp/wreck-it
mkdir -p ~/.claude/skills
cp -r /tmp/wreck-it/skills/wreck-explore ~/.claude/skills/wreck-explorePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# wreck-explore `WRECK` means `npx @miyanishar/wreck-it`. Two passes: 1. **Normal-user pass**, persona `normal-user`. 2. **Persona exploration**, every other persona in `.wreck-it/personas.md` except `chaos-monkey`. Needs `.wreck-it/discovery.json` (`WRECK discover`), `.wreck-it/personas.md` (wreck-personas skill) and Playwright MCP. Follow the wreck-it skill's rules, and record bugs as in its `references/recording-findings.md` (structured steps, role/label targets, assertions for correct behavior, replayed in a fresh context before `reproduced: true`). ## Per page, every time After each navigation or meaningful action: 1. `browser_snapshot` to read the page. Use the role and name values it shows for targets. 2. Run the oddity script: `browser_evaluate` with the output of `WRECK oddity-script` (fetch it once and reuse it). 3. Check `browser_console_messages` (errors) and `browser_network_requests` (4xx/5xx). 4. Log coverage: `WRECK run visit <route> --persona <slug>`. 5. Before recording a finding, take a screenshot with `browser_take_screenshot` that shows the failure, inspect it, and attach its actual path in `evidence.screenshots`. Refresh the evidence during reproduction when needed; follow the shared recording guide for storage and presentation. ## Pass 1: normal-user (stage `normal`) `WRECK run stage normal running`
Details
- Skill name
wreck-explore- Repository
- miyannishar/wreck-it
- Path
skills/wreck-explore/SKILL.md- License
- MIT
- Repo updated
- 25 October 2026
- Listed in
- karanb192/awesome-claude-skills
FAQ
What does the Wreck Explore skill do?
Explore a running local web app through Playwright MCP as a normal user (every core flow plus data-integrity checks) and then in character as each persona from .wreck-it/personas.md, recording reproducible bugs with wreck-it. Use as stages 4–5 of a wreck-it run, or when the user asks to "click through my app like a user", "test the happy paths", "try my app as a beginner", or "check my core flows".
How do I install the Wreck Explore skill?
Claude Code plugin: /plugin marketplace add miyannishar/wreck-it. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Related skills
Wreck Chaos
miyannishar/wreck-it
Chaos-test a running local web app as the chaos-monkey persona, using a page sweep, an API fuzzer (plus Schemathesis when there's an OpenAPI spec), hostile form inputs, double-submits, back/forward/refresh mid-flow, multiple tabs, offline/slow/500-injected network, expired or tampered sessions, an axe-core scan and keyboard-only navigation. Records reproducible bugs with wreck-it. Use as stage 6 of a wreck-it run, or when the user asks to "break my forms", "chaos test", "try weird inputs", "test offline", or "check accessibility".
Wreck It
miyannishar/wreck-it
Full wreck-it run against a locally running web app. It tests like normal users, ICP personas, rushed beginners, chaos monkeys and traffic spikes, then writes a scored bug report with source file:line and regression Playwright tests. Use when the user says "wreck my app", "wreck it", "test my app like a user", "find bugs before launch", "is my app ready to ship", or asks for a readiness score. Also for one feature, such as "test the checkout", "just test signup", "check the coupon flow" (a focused run). For a single stage ("just stress test my API", "only check accessibility"), use the matchin
Wreck Load
miyannishar/wreck-it
Page speed and load testing for a local web app with the wreck-it CLI. It measures each page with Lighthouse on a simulated phone (LCP, CLS, TBT), diagnoses slow pages with Chrome DevTools performance traces when available, runs ramp, spike and soak load profiles (p50/p90/p99 latency, error rate, breaking point, memory trend), then traces slow endpoints to causes such as N+1 queries, missing indexes or blocking work. Use as stage 7 of a wreck-it run, or when the user asks to "stress test my API", "load test", "how many users can my app handle", "find slow endpoints", "check page speed", or "ru
Tracking Regression Tests
jeremylongshore/claude-code-plugins-plus-skills
This skill enables Claude to track and run regression tests, ensuring new changes don't break existing functionality. It is triggered when the user asks to "track regression", "run regression tests", or uses the shortcut "reg". The skill helps in maintaining code stability by identifying critical tests, automating their execution, and analyzing the impact of changes. It also provides insights into test history and identifies flaky tests. The skill uses the `regression-test-tracker` plugin.
Wreck Personas
miyannishar/wreck-it
Derive realistic user personas (the app's ideal customers plus built-in normal-user, rushed-beginner and chaos-monkey) and their missions for wreck-it testing, saved to .wreck-it/personas.md. Use as stage 3 of a wreck-it run, or when the user asks "who would use my app", "make test personas", or wants to edit the personas used for testing.
Testing Load Balancers
jeremylongshore/claude-code-plugins-plus-skills
This skill enables Claude to test load balancing strategies. It validates traffic distribution across backend servers, tests failover scenarios when servers become unavailable, verifies sticky sessions, and assesses health check functionality. Use this skill when the user asks to "test load balancer", "validate traffic distribution", "test failover", "verify sticky sessions", or "test health checks". It is specifically designed for testing load balancing configurations using the `load-balancer-tester` plugin.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.