Testing
kortix-ai/suna
A skill your agent uses for every Kortix test task, behavior change, bug fix, refactor, API route change, CLI change, SDK change, browser journey, test failure, coverage question, local benchmark…
A skill your agent uses when Playwright scripts fail, tests are flaky, selectors stop working, or timeouts occur - provides systematic debugging approach for browser automation issues
Install Playwright Debugging
$ npx skills add ed3dai/ed3d-plugins --skill playwright-debugging -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ed3dai/ed3d-plugins playwright-debugging --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/ed3dai/ed3d-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ed3d-playwright/skills/playwright-debugging .claude/skills/playwright-debugging && 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 "playwright-debugging" agent skill from https://github.com/ed3dai/ed3d-plugins/tree/main/plugins/ed3d-playwright/skills/playwright-debugging into .claude/skills/playwright-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "playwright-debugging", 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/ed3dai/ed3d-plugins/tree/main/plugins/ed3d-playwright/skills/playwright-debuggingType 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 ed3dai/ed3d-plugins --skill playwright-debugging -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ed3dai/ed3d-plugins playwright-debugging --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ed3dai/ed3d-plugins.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/ed3d-playwright/skills/playwright-debugging .agents/skills/playwright-debugging && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "playwright-debugging" agent skill from https://github.com/ed3dai/ed3d-plugins/tree/main/plugins/ed3d-playwright/skills/playwright-debugging into .agents/skills/playwright-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "playwright-debugging", 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 ed3dai/ed3d-plugins --skill playwright-debugging -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ed3dai/ed3d-plugins playwright-debugging --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ed3dai/ed3d-plugins.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/ed3d-playwright/skills/playwright-debugging .cursor/skills/playwright-debugging && 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 "playwright-debugging" agent skill from https://github.com/ed3dai/ed3d-plugins/tree/main/plugins/ed3d-playwright/skills/playwright-debugging into .cursor/skills/playwright-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "playwright-debugging", 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/ed3dai/ed3d-plugins.git --path plugins/ed3d-playwright/skills/playwright-debugging--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 ed3dai/ed3d-plugins --skill playwright-debugging -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ed3dai/ed3d-plugins playwright-debugging --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ed3dai/ed3d-plugins.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/ed3d-playwright/skills/playwright-debugging .gemini/skills/playwright-debugging && 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 "playwright-debugging" agent skill from https://github.com/ed3dai/ed3d-plugins/tree/main/plugins/ed3d-playwright/skills/playwright-debugging into .gemini/skills/playwright-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "playwright-debugging", 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 ed3dai/ed3d-plugins playwright-debuggingInstalls 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 ed3dai/ed3d-plugins --skill playwright-debugging -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ed3dai/ed3d-plugins.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/ed3d-playwright/skills/playwright-debugging .github/skills/playwright-debugging && 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 "playwright-debugging" agent skill from https://github.com/ed3dai/ed3d-plugins/tree/main/plugins/ed3d-playwright/skills/playwright-debugging into .github/skills/playwright-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "playwright-debugging", 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 ed3dai/ed3d-plugins --skill playwright-debugging -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ed3dai/ed3d-plugins playwright-debugging --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ed3dai/ed3d-plugins.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/ed3d-playwright/skills/playwright-debugging .opencode/skills/playwright-debugging && 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 "playwright-debugging" agent skill from https://github.com/ed3dai/ed3d-plugins/tree/main/plugins/ed3d-playwright/skills/playwright-debugging into .opencode/skills/playwright-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "playwright-debugging", 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
playwright-debugging- GitHub stars
- 250
- Token cost
- ~3.3k tokens
- SKILL.md length
- 856 words
- Files
- 1
- Skills in repo
- 34
- Repo updated
- First seen
- Licence
- None found
At a glance
A skill your agent uses when Playwright scripts fail, tests are flaky, selectors stop working, or timeouts occur - provides systematic debugging approach for browser automation issues
- Works in 4 steps: Reproduce and Isolate → Add Visibility → Inspect Element State → …
- Playwright scripts fail
- SKILL.md covers Overview, When to Use, Quick Reference and Diagnostic Framework, plus 6 more sections
- Calls npx
What it does
Playwright Debugging is an agent skill from ed3dai/ed3d-plugins. Use when Playwright scripts fail, tests are flaky, selectors stop working, or timeouts occur - provides systematic debugging approach for browser automation issues
Its SKILL.md is about 3.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering Browser testing, Debugging and Browser automation. It works with Playwright. The repository describes itself as: Ed's repo of Claude Code plugins, centered around a research-plan-implement workflow. Only a tiny bit cursed. If you're lucky.
When your agent uses it
- Playwright scripts fail
- Tests are flaky
- Selectors stop working
- Timeouts occur - provides systematic debugging approach for browser automation issues
Example prompts
- “/playwright-debugging”
Requirements
- Node.js
Workflow steps
4 steps, taken from the step headings in SKILL.md.
- Reproduce and Isolate
- Add Visibility
- Inspect Element State
- Verify Selector
What it can do on your machine
Read from SKILL.md and the folder at commit 0c90f4b. 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
Shell commands in SKILL.md call:
npx
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx, 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
Playwright Debugging loads about 3.3k tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 856 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
Without a licence we can't republish the file, so here is its outline and opening line. It has 856 words (~3,334 tokens).
“Browser automation failures fall into predictable categories. This skill provides a systematic approach to diagnose and fix issues quickly.”
- name
- playwright-debugging
- user-invocable
- false
Files
Just SKILL.md in plugins/ed3d-playwright/skills/playwright-debugging of ed3dai/ed3d-plugins.
Open the folder on GitHubat commit 0c90f4b
Compare with similar skills
Playwright Debugging 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 |
|---|---|---|---|---|---|---|
| Playwright Debugging this skilled3dai/ed3d-plugins | 250 | — | ~3.3k | Automated safety check: Pass | None | |
| Testingkortix-ai/suna | 20k | — | ~3.6k | Automated safety check: Notes | Custom licence | |
| UI Visual DebuggingNangoHQ/nango | 13k | — | ~1.3k | Automated safety check: Pass | Custom licence | |
| E2E Tests Studiomastra-ai/mastra | 29k | — | ~4.3k | Automated safety check: Pass | Custom licence | |
| Debuggingidavidov13/agentic-playwright | 223 | — | ~6.2k | Automated safety check: Notes | MIT | |
| playwright-cli Browser Automationgithub/gh-aw | 5.3k | 23 repos | ~2.8k | Automated safety check: Pass | MIT |
Similar skills
UI Visual Debugging
NangoHQ/nango
A skill your agent uses when modifying or visually debugging Nango frontend UI, including packages/webapp, packages/connect-ui, browser interactions, screenshots, and visual regressions.
E2E Tests Studio
mastra-ai/mastra
REQUIRED when modifying any file in packages/playground-ui or packages/playground.
Debugging
idavidov13/agentic-playwright
Playwright test debugging conventions for the scaffold — reading failure messages, classifying failure modes (TimeoutError, ZodError, strict-mode violation, locator not found, network errors, schema…
- Official
playwright-cli Browser Automation
github/gh-aw
Drives a real browser from the command line with playwright-cli to open pages, interact, mock requests, save state and work with Playwright tests.
Playwright Skill
lackeyjb/playwright-skill
Complete browser automation with Playwright. An agent skill from lackeyjb/playwright-skill.
More from ed3dai/ed3d-plugins
All 34 skills in this repoSystematic Debugging
ed3dai/ed3d-plugins
A skill your agent uses when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis…
Testing Skills With Subagents
ed3dai/ed3d-plugins
A skill your agent uses when creating or editing skills, before deployment, to verify they work under pressure and resist rationalization - applies RED-GREEN-REFACTOR cycle to process documentation…
Brainstorming
ed3dai/ed3d-plugins
A skill your agent uses when creating or developing anything, before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning…
Writing Good Tests
ed3dai/ed3d-plugins
A skill your agent uses when writing or reviewing tests - covers test philosophy, condition-based waiting, mocking strategy, and test isolation
Writing Skills
ed3dai/ed3d-plugins
A skill your agent uses when creating new skills, editing existing skills, or verifying skills work before deployment - applies TDD to process documentation by testing with subagents before writing…
Coding Effectively
ed3dai/ed3d-plugins
ALWAYS use this skill when writing or refactoring code. An agent skill from ed3dai/ed3d-plugins.
Related
Works with
Categories
Questions about Playwright Debugging
What does Playwright Debugging do?
A skill your agent uses when Playwright scripts fail, tests are flaky, selectors stop working, or timeouts occur - provides systematic debugging approach for browser automation issues. Playwright Debugging is an agent skill from ed3dai/ed3d-plugins.
When should I use Playwright Debugging?
Playwright Debugging fits situations like: playwright scripts fail; tests are flaky; selectors stop working; timeouts occur - provides systematic debugging approach for browser automation issues.
How do I install Playwright Debugging in Claude Code?
Run `npx skills add ed3dai/ed3d-plugins --skill playwright-debugging -a claude-code`. Or copy the skill folder (plugins/ed3d-playwright/skills/playwright-debugging in ed3dai/ed3d-plugins) into .claude/skills/playwright-debugging in your project. Claude Code loads it when a task matches its description.
How do I install Playwright Debugging in Codex?
Run `npx skills add ed3dai/ed3d-plugins --skill playwright-debugging -a codex`. Or copy the skill folder (plugins/ed3d-playwright/skills/playwright-debugging in ed3dai/ed3d-plugins) into .agents/skills/playwright-debugging in your project. Codex loads it when a task matches its description.
Can I use Playwright Debugging 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 ed3dai/ed3d-plugins --skill playwright-debugging -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/playwright-debugging, .gemini/skills/playwright-debugging, .github/skills/playwright-debugging and .opencode/skills/playwright-debugging in your project.
What does Playwright Debugging need to run?
Going by SKILL.md and its folder, Playwright Debugging needs the command-line tools its instructions call (npx). Our summary lists: Node.js.
Does Playwright Debugging access the network?
SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Playwright Debugging 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 Playwright Debugging use?
No licence was found for Playwright Debugging or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Playwright Debugging use?
About 3.3k tokens (SKILL.md is roughly 13k 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 Playwright Debugging?
Skills that share tags, products or a category with Playwright Debugging: Testing (kortix-ai/suna, 20k stars), UI Visual Debugging (NangoHQ/nango, 13k stars), E2E Tests Studio (mastra-ai/mastra, 29k stars) and Debugging (idavidov13/agentic-playwright, 223 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Playwright Debugging?
ed3dai (a GitHub organization) maintains it in ed3dai/ed3d-plugins, which has 250 GitHub stars. The repository holds 34 skills in this directory. The repository was last updated on September 6, 2026.
Source: ed3dai/ed3d-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.