Write and Verify Playwright Tests
appsmithorg/appsmith
Writes a Playwright end-to-end test from a prompt, runs it against a live Appsmith deployment and retries with fixes up to three times until it passes.
Clicks through every flow of an app clone and tests it for bugs: a test plan generated from the recon flows with happy paths and edge cases, Playwright end-to-end tests where possible, a browser…
Install Replica Test
$ npx skills add Jakeschincariol/replica-skill --skill replica-test -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Jakeschincariol/replica-skill replica-test --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Jakeschincariol/replica-skill.git skills-src && mkdir -p .claude/skills && cp -r skills-src/replica-test .claude/skills/replica-test && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "replica-test" agent skill from https://github.com/Jakeschincariol/replica-skill/tree/main/replica-test into .claude/skills/replica-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "replica-test", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Jakeschincariol/replica-skill/tree/main/replica-testType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Jakeschincariol/replica-skill --skill replica-test -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Jakeschincariol/replica-skill replica-test --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jakeschincariol/replica-skill.git skills-src && mkdir -p .agents/skills && cp -r skills-src/replica-test .agents/skills/replica-test && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "replica-test" agent skill from https://github.com/Jakeschincariol/replica-skill/tree/main/replica-test into .agents/skills/replica-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "replica-test", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Jakeschincariol/replica-skill --skill replica-test -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Jakeschincariol/replica-skill replica-test --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jakeschincariol/replica-skill.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/replica-test .cursor/skills/replica-test && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "replica-test" agent skill from https://github.com/Jakeschincariol/replica-skill/tree/main/replica-test into .cursor/skills/replica-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "replica-test", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Jakeschincariol/replica-skill.git --path replica-test--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Jakeschincariol/replica-skill --skill replica-test -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Jakeschincariol/replica-skill replica-test --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jakeschincariol/replica-skill.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/replica-test .gemini/skills/replica-test && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "replica-test" agent skill from https://github.com/Jakeschincariol/replica-skill/tree/main/replica-test into .gemini/skills/replica-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "replica-test", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Jakeschincariol/replica-skill replica-testInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Jakeschincariol/replica-skill --skill replica-test -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Jakeschincariol/replica-skill.git skills-src && mkdir -p .github/skills && cp -r skills-src/replica-test .github/skills/replica-test && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "replica-test" agent skill from https://github.com/Jakeschincariol/replica-skill/tree/main/replica-test into .github/skills/replica-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "replica-test", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Jakeschincariol/replica-skill --skill replica-test -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Jakeschincariol/replica-skill replica-test --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jakeschincariol/replica-skill.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/replica-test .opencode/skills/replica-test && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "replica-test" agent skill from https://github.com/Jakeschincariol/replica-skill/tree/main/replica-test into .opencode/skills/replica-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "replica-test", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
replica-test- GitHub stars
- 1.2k
- Token cost
- ~819 tokens
- SKILL.md length
- 402 words
- Files
- 4
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- MIT
At a glance
Clicks through every flow of an app clone and tests it for bugs: a test plan generated from the recon flows with happy paths and edge cases, Playwright end-to-end tests where possible, a browser…
- Works in 5 steps: the plan → automate what you can → click through the rest → …
- The user says test my clone
- SKILL.md covers The rule, Step 1: the plan, Step 2: automate what you can and Step 3: click through the rest, plus 3 more sections
- Runs TypeScript scripts from its folder; calls npx and npm
What it does
Replica Test is an agent skill from Jakeschincariol/replica-skill. Clicks through every flow of an app clone and tests it for bugs: a test plan generated from the recon flows with happy paths and edge cases, Playwright end-to-end tests where possible, a browser click-through where not, and bug reports in a fixed format with severity, steps and evidence. Use when the user says "test my clone", "find bugs", "QA this", "click through everything", "write e2e tests", "does it work", or after /replica-build or /replica-backend.
Its SKILL.md is about 820 tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files (for example `bug-report.md`, `e2e.example.spec.ts` and `test-plan.md`).
It sits in Testing & QA, covering Test generation, QA and bug reports and End-to-end testing. It works with Playwright. The repository describes itself as: Eleven free Claude skills that clone any app: reverse-engineer it, rebuild it, test it for bugs, then fix what its users hate. Free, MIT. The licence is MIT.
When your agent uses it
- The user says test my clone
- Click through everything
- Write e2e tests
- After /replica-build
Example prompts
- “test my clone”
- “find bugs”
- “QA this”
- “/replica-test”
Requirements
- Node.js
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 77c9436. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships script files (TypeScript), which the agent can run.
Shell commands in SKILL.md call:
npxnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx and npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Replica Test loads about 819 tokens when it runs. Until then it costs about 118 tokens; SKILL.md has 402 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Jakeschincariol/replica-skill at commit 77c9436, republished under its MIT licence (© Jakeschincariol). 402 words, ~819 tokens.
Download SKILL.mdSave it as
.claude/skills/replica-test/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- replica-test
- description
- Clicks through every flow of an app clone and tests it for bugs: a test plan generated from the recon flows with happy paths and edge cases, Playwright end-to-end tests where possible, a browser click-through where not, and bug reports in a fixed format with severity, steps and evidence. Use when the user says "test my clone", "find bugs", "QA this", "click through everything", "write e2e tests", "does it work", or after /replica-build or /replica-backend.
replica-test
Reads the flows in replica/recon.md. Writes replica/test-plan.md,
replica/bugs.md, and end-to-end tests in the project (e2e/). Templates in
this folder: test-plan.md, bug-report.md, e2e.example.spec.ts.
The rule
Test your clone, not the original. Never load test, fuzz, script or hammer the original app's servers. Using the original by hand, as a normal user, to see how it behaves is fine.
Step 1: the plan
For every flow F01, F02... in the recon map, write:
- Happy path: the steps, and what the user should see at the end.
- Edge cases that apply. Go down this list for every flow: empty input, very long input, emoji and accents, two tabs at once, double click on submit, back button mid-flow, refresh mid-flow, slow network, offline, expired session, second user's data (must be invisible), time zones and daylight saving, mobile width, keyboard only, screen reader labels.
- Negative cases: wrong password, card declined (Stripe test card
4000 0000 0000 0002), permission denied, deleted record.
Number every case: F01-H1, F01-E3, F01-N2.
Step 2: automate what you can
Playwright, one spec per flow, against the local dev server with seed data.
Use roles and labels for selectors (getByRole('button', { name: 'Book' })),
never CSS classes. See e2e.example.spec.ts.
npm i -D @playwright/test && npx playwright install chromium
npx playwright testAdd to every spec: fail on console errors, fail on any 5xx response, and an
axe accessibility scan (@axe-core/playwright) on each screen.
Show full SKILL.md (184 more words)Show less
Step 3: click through the rest
What cannot be automated (emails arriving, OAuth with real providers, payments end to end, visual glitches) gets a manual pass. If a browser tool is available, drive the local clone with it and screenshot each step. Otherwise give the user the checklist and wait for answers.
Step 4: report bugs
Every bug goes in replica/bugs.md in the bug-report.md format: an ID, a
severity, exact steps, expected, actual, evidence. Severity:
| means | |
|---|---|
| S1 | data loss, security hole, payments wrong, core flow blocked |
| S2 | a feature broken, no workaround |
| S3 | broken with a workaround, or visibly wrong |
| S4 | cosmetic |
Only report what you reproduced. "Might be an issue" goes in a separate "to check" list.
Step 5: fix loop
Fix S1 and S2 first. For every fix: write the failing test first, fix, watch
it pass, keep the test. Re-run the whole suite after each batch. Update
bugs.md with the commit that fixed each one.
Output
test-plan.md, the specs, bugs.md, and a summary: cases run, passed,
failed, bugs by severity, fixed so far. Ship nothing with an open S1. Next:
/replica-diff.
© Jakeschincariol, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files in replica-test of Jakeschincariol/replica-skill.
- SKILL.md
- bug-report.md
- e2e.example.spec.ts
- test-plan.md
Open the folder on GitHubat commit 77c9436
Compare with similar skills
Replica Test next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Replica Test this skillJakeschincariol/replica-skill | 1.2k | — | ~819 | Automated safety check: Pass | MIT | |
| Write and Verify Playwright Testsappsmithorg/appsmith | 41k | — | ~2.9k | Automated safety check: Notes | Apache-2.0 | |
| Dogfoodredf0x1/camofox-browser | 412 | — | ~1.2k | Automated safety check: Pass | MIT | |
| E2Esendou-ink/sendou.ink | 297 | — | ~2.1k | Automated safety check: Notes | AGPL-3.0 | |
| Twenty QA Scouttwentyhq/twenty | 58k | — | ~2k | Automated safety check: Pass | Custom licence | |
| Agentic Browser Testingpetrkindlmann/qa-skills | 168 | — | ~4.5k | Automated safety check: Pass | MIT |
Similar skills
Dogfood
redf0x1/camofox-browser
QA testing workflow for CamoFox Browser — systematic testing with console capture, error detection, and Playwright tracing.
E2E
sendou-ink/sendou.ink
Run, debug, and manage Playwright e2e tests. An agent skill from sendou-ink/sendou.ink.
Twenty QA Scout
twentyhq/twenty
Browser QA for a pull request against a running Twenty app: scenarios drawn from the diff, run in a real browser, checked in the database and logs, and closed with a verdict and report.
Agentic Browser Testing
petrkindlmann/qa-skills
Goal-driven E2E testing where a browser agent (Playwright MCP / computer-use) reads a natural-language goal and explores the app via the accessibility tree to assert outcomes — no pre-written script.
E2E Tests Studio
mastra-ai/mastra
REQUIRED when modifying any file in packages/playground-ui or packages/playground.
More from Jakeschincariol/replica-skill
All 11 skills in this repoReplica Architect
Jakeschincariol/replica-skill
Plans the stack, database schema and API for an app clone, from the recon map replica-recon wrote.
Replica Brand
Jakeschincariol/replica-skill
Names and rebrands an app clone so it is the user's own: name candidates with the trademark, domain, store and handle checks to run, a new palette checked for contrast, a logo brief, a voice guide…
Replica Deploy
Jakeschincariol/replica-skill
Ships an app clone live on the user's own domain: a preflight gate (tests green, parity must-haves done, rebrand sweep clean, listing linted, legal pages up), production database and env vars, the…
Replica Design
Jakeschincariol/replica-skill
Rebuilds an app's design system for a clone: colour roles, type scale, spacing, radius, shadows and every component with its states, as design tokens plus component specs, with original assets…
Replica Diff
Jakeschincariol/replica-skill
Compares an app clone against the original: a feature parity score from the feature matrix (weighted by must, should, could) with the missing list in build order, plus a screenshot layout diff that…
Replica Entrepreneur
Jakeschincariol/replica-skill
Researches the app being cloned and reads what its real users say in public reviews (App Store, Google Play, G2, Capterra, Trustpilot, Reddit, Hacker News, its own feature-request board), then ranks…
Related
Works with
Categories
Questions about Replica Test
What does Replica Test do?
Clicks through every flow of an app clone and tests it for bugs: a test plan generated from the recon flows with happy paths and edge cases, Playwright end-to-end tests where possible, a browser…. Replica Test is an agent skill from Jakeschincariol/replica-skill. Clicks through every flow of an app clone and tests it for bugs: a test plan generated from the recon flows with happy paths and edge cases, Playwright end-to-end tests where possible, a browser click-through where not, and bug reports in a fixed format with severity, steps and evidence.
When should I use Replica Test?
Replica Test fits situations like: the user says test my clone; click through everything; write e2e tests; after /replica-build.
How do I install Replica Test in Claude Code?
Run `npx skills add Jakeschincariol/replica-skill --skill replica-test -a claude-code`. Or copy the skill folder (replica-test in Jakeschincariol/replica-skill) into .claude/skills/replica-test in your project. Claude Code loads it when a task matches its description.
How do I install Replica Test in Codex?
Run `npx skills add Jakeschincariol/replica-skill --skill replica-test -a codex`. Or copy the skill folder (replica-test in Jakeschincariol/replica-skill) into .agents/skills/replica-test in your project. Codex loads it when a task matches its description.
Can I use Replica Test in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Jakeschincariol/replica-skill --skill replica-test -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/replica-test, .gemini/skills/replica-test, .github/skills/replica-test and .opencode/skills/replica-test in your project.
What does Replica Test need to run?
Going by SKILL.md and its folder, Replica Test needs TypeScript for the scripts in its folder and the command-line tools its instructions call (npx and npm). Our summary lists: Node.js.
Does Replica Test access the network?
SKILL.md contains no URLs. Its commands use npx and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Replica Test safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Replica Test use?
Replica Test is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Replica Test use?
About 819 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Replica Test?
Skills that share tags, products or a category with Replica Test: Write and Verify Playwright Tests (appsmithorg/appsmith, 41k stars), Dogfood (redf0x1/camofox-browser, 412 stars), E2E (sendou-ink/sendou.ink, 297 stars) and Twenty QA Scout (twentyhq/twenty, 58k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Replica Test?
Jakeschincariol (a GitHub user) maintains it in Jakeschincariol/replica-skill, which has 1,158 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 3, 2026.
Source: Jakeschincariol/replica-skill on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.