Open Browser
JasonHonKL/Openbrowser
A skill your agent uses whenever the task involves browsing web pages, extracting page content, clicking forms, or completing web workflows.
Migrates and converts test automation scripts between Selenium, Playwright, Puppeteer, and Cypress.
Install Test Framework Migration Skill
$ npx skills add sickn33/agentic-awesome-skills --skill test-framework-migration-skill -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sickn33/agentic-awesome-skills test-framework-migration-skill --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/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/test-framework-migration-skill .claude/skills/test-framework-migration-skill && 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 "test-framework-migration-skill" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/test-framework-migration-skill into .claude/skills/test-framework-migration-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-framework-migration-skill", 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/sickn33/agentic-awesome-skills/tree/main/skills/test-framework-migration-skillType 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 sickn33/agentic-awesome-skills --skill test-framework-migration-skill -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sickn33/agentic-awesome-skills test-framework-migration-skill --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/test-framework-migration-skill .agents/skills/test-framework-migration-skill && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "test-framework-migration-skill" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/test-framework-migration-skill into .agents/skills/test-framework-migration-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-framework-migration-skill", 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 sickn33/agentic-awesome-skills --skill test-framework-migration-skill -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sickn33/agentic-awesome-skills test-framework-migration-skill --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/test-framework-migration-skill .cursor/skills/test-framework-migration-skill && 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 "test-framework-migration-skill" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/test-framework-migration-skill into .cursor/skills/test-framework-migration-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-framework-migration-skill", 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/sickn33/agentic-awesome-skills.git --path skills/test-framework-migration-skill--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 sickn33/agentic-awesome-skills --skill test-framework-migration-skill -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sickn33/agentic-awesome-skills test-framework-migration-skill --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/test-framework-migration-skill .gemini/skills/test-framework-migration-skill && 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 "test-framework-migration-skill" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/test-framework-migration-skill into .gemini/skills/test-framework-migration-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-framework-migration-skill", 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 sickn33/agentic-awesome-skills test-framework-migration-skillInstalls 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 sickn33/agentic-awesome-skills --skill test-framework-migration-skill -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/test-framework-migration-skill .github/skills/test-framework-migration-skill && 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 "test-framework-migration-skill" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/test-framework-migration-skill into .github/skills/test-framework-migration-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-framework-migration-skill", 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 sickn33/agentic-awesome-skills --skill test-framework-migration-skill -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sickn33/agentic-awesome-skills test-framework-migration-skill --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/test-framework-migration-skill .opencode/skills/test-framework-migration-skill && 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 "test-framework-migration-skill" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/test-framework-migration-skill into .opencode/skills/test-framework-migration-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-framework-migration-skill", 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
test-framework-migration-skill- GitHub stars
- 47k
- Used in
- 1 other repo
- Token cost
- ~2.2k tokens
- SKILL.md length
- 660 words
- Files
- 1
- Skills in repo
- 1,394
- Repo updated
- First seen
- Licence
- MIT
At a glance
Migrates and converts test automation scripts between Selenium, Playwright, Puppeteer, and Cypress.
- Works in 5 steps: Detect Source Framework → Detect Target Framework → Detect Language → …
- Tasks that involve Browser testing
- SKILL.md covers When to Use, Step 1 — Detect Source Framework, Step 2 — Detect Target Framework and Step 3 — Detect Language, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Test Framework Migration Skill is an agent skill from sickn33/agentic-awesome-skills. Migrates and converts test automation scripts between Selenium, Playwright, Puppeteer, and Cypress.
Its SKILL.md is about 2.2k 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, Code migrations and End-to-end testing. It works with Playwright, Selenium, Cypress and Puppeteer. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.
When your agent uses it
- Tasks that involve Browser testing
- Tasks that involve Code migrations
- Tasks that involve End-to-end testing
Example prompts
- “Use the test-framework-migration-skill skill to migrate and converts test automation scripts between Selenium, Playwright, Puppeteer, and Cypress”
- “/test-framework-migration-skill”
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 1e53ce2. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
github.com
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
Test Framework Migration Skill loads about 2.2k tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 660 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 sickn33/agentic-awesome-skills at commit 1e53ce2, republished under its MIT licence (© sickn33). 660 words, ~2,177 tokens.
Download SKILL.mdSave it as
.claude/skills/test-framework-migration-skill/SKILL.md (or your agent's skills folder).- name
- test-framework-migration-skill
- description
- Migrates and converts test automation scripts between Selenium, Playwright, Puppeteer, and Cypress.
- risk
- critical
- source
- https://github.com/LambdaTest/agent-skills/tree/main/test-framework-migration-skill
- source_repo
- LambdaTest/agent-skills
- source_type
- community
- date_added
- 2026-07-01
- license
- MIT
- license_source
- https://github.com/LambdaTest/agent-skills/blob/main/LICENSE
Test Framework Migration Skill
When to Use
Use this skill when you need migrates and converts test automation scripts between Selenium, Playwright, Puppeteer, and Cypress. Use when the user asks to migrate, convert, or port tests from one framework to another; rewrite tests in a different framework; or switch from Selenium to Playwright, Playwright to...
You are a senior QA automation architect. You migrate test automation scripts from one framework (Selenium, Playwright, Puppeteer, Cypress) to another by applying API mappings, lifecycle changes, and pattern conversions from the skill reference docs.
Step 1 — Detect Source Framework
Determine the source framework from the user message or from open files:
| Signal in message or code | Source framework |
|---|---|
| "Selenium", "WebDriver", "driver.findElement", "By.id", "ChromeDriver" | Selenium |
| "Playwright", "page.getByRole", "expect(locator).toBeVisible", "@playwright/test" | Playwright |
| "Puppeteer", "page.$", "page.goto", "puppeteer.launch" | Puppeteer |
| "Cypress", "cy.get", "cy.visit", "cy.contains", "cy.should" | Cypress |
If ambiguous (e.g. user says "convert my tests" with no file open), ask: "Which framework are your current tests in (Selenium, Playwright, Puppeteer, or Cypress)?"
Step 2 — Detect Target Framework
Determine the target framework from the user message:
| User says... | Target |
|---|---|
| "to Playwright", "to playwright" | Playwright |
| "to Selenium", "to WebDriver" | Selenium |
| "to Puppeteer" | Puppeteer |
| "to Cypress" | Cypress |
If the user only names the source (e.g. "convert my Selenium tests"), ask: "Which framework do you want to migrate to (Playwright, Puppeteer, Cypress, or keep Selenium with another language)?"
Step 3 — Detect Language
| Source → Target | Language note |
|---|---|
| Selenium (Java/Python/C#) → Playwright | Playwright is typically JS/TS; migration usually implies rewriting to TypeScript or JavaScript. Mention this if source is Java/C#/Python. |
| Selenium (JS) → Playwright | Same language (JS/TS) possible. |
| Playwright/Puppeteer/Cypress → Selenium | Target can be Java, Python, JS, C#. Prefer same as project or ask. |
| Playwright ↔ Puppeteer ↔ Cypress | Typically stay in JS/TS. |
For language matrix details (which frameworks support which languages), see reference/overview.md.
Step 4 — Route to Reference
Always read the matching reference file before generating migrated code:
| Source → Target | Reference file |
|---|---|
| Selenium → Playwright | reference/selenium-to-playwright.md |
| Playwright → Selenium | reference/playwright-to-selenium.md |
| Selenium → Puppeteer | reference/selenium-to-puppeteer.md |
| Puppeteer → Selenium | reference/puppeteer-to-selenium.md |
| Puppeteer → Playwright | reference/puppeteer-to-playwright.md |
| Playwright → Puppeteer | reference/playwright-to-puppeteer.md |
| Cypress → Playwright | reference/cypress-to-playwright.md |
| Playwright → Cypress | reference/playwright-to-cypress.md |
| Selenium → Cypress | reference/selenium-to-cypress.md |
| Cypress → Selenium | reference/cypress-to-selenium.md |
If the pair is not in the table, say so and suggest the closest supported migration (e.g. add WebDriverIO later as a new reference file).
Show full SKILL.md (294 more words)Show less
Step 5 — Apply Mappings
Using the reference doc:
- Locators — Convert using the API mapping table (e.g.
By.id("x")→page.getByRole(...)orpage.locator('#x')). - Waits — Convert wait strategy (explicit wait / auto-wait / cy.should).
- Actions — Map click, type, select, etc.
- Assertions — Map to target's assertion style.
- Lifecycle — Adjust setup/teardown (driver vs page, launch vs connect).
- Cloud (TestMu) — If user runs on cloud, point to target framework's cloud docs after migration.
After generating migrated code, validate against the "Gotchas" section of the reference to avoid common pitfalls.
Cross-References for Deep Patterns
| Need | Where to look |
|---|---|
| Full Playwright patterns, POM, cloud | playwright-skill and playwright-skill/reference/cloud-integration.md |
| Full Selenium patterns, POM, cloud | selenium-skill and selenium-skill/reference/cloud-integration.md |
| Full Puppeteer patterns, cloud | puppeteer-skill and puppeteer-skill/reference/cloud-integration.md |
| Full Cypress patterns, cloud | cypress-skill and cypress-skill/reference/cloud-integration.md |
| TestMu capabilities (all frameworks) | shared/testmu-cloud-reference.md |
Validation Workflow
After generating migrated code:
- Ensure every locator/action/assertion was converted using the reference mapping (no leftover source API).
- Ensure lifecycle (setup/teardown) matches target framework.
- If target is Playwright: use auto-wait assertions (
expect(locator).toBeVisible()), not rawwaitForTimeout. - If target is Cypress: no async/await with
cycommands; use chain style. - If target is Selenium: use explicit
WebDriverWait, neverThread.sleep.
Reference Files Summary
| File | When to read |
|---|---|
| reference/overview.md | Framework comparison, language matrix, when to migrate |
| reference/playbook.md | Full migration workflow, debugging table, CI/CD checklist, best practices |
reference/<source>-to-<target>.md | Before converting any script for that pair |
Example
User request:
Use @test-framework-migration-skill for this task: Migrates and converts test automation scripts between Selenium, Playwright, Puppeteer, and Cypress.
Limitations
- Use this skill only when the task clearly matches its upstream source and local project context.
- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.
© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/test-framework-migration-skill of sickn33/agentic-awesome-skills.
Open the folder on GitHubat commit 1e53ce2
Used in 1 other repository
We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Test Framework Migration Skill 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 |
|---|---|---|---|---|---|---|
| Test Framework Migration Skill this skillsickn33/agentic-awesome-skills | 47k | 1 repos | ~2.2k | Automated safety check: Pass | MIT | |
| Open BrowserJasonHonKL/Openbrowser | 114 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Playwright Migrationzebbern/claude-code-guide | 4.6k | 2 repos | ~187 | Automated safety check: Pass | MIT | |
| Test Migrationpetrkindlmann/qa-skills | 163 | — | ~5.3k | Automated safety check: Pass | MIT | |
| RStudio Selenium to Playwright Migrationrstudio/rstudio | 5.1k | — | ~3.6k | Automated safety check: Pass | Custom licence | |
| Migratealirezarezvani/claude-skills | 28k | 1 repos | ~1k | Automated safety check: Pass | MIT |
Similar skills
Playwright Migration
zebbern/claude-code-guide
Step-by-step migration guides for moving to Playwright from Cypress or Selenium/WebDriver — command mappings, architecture changes, and incremental adoption strategies.
Test Migration
petrkindlmann/qa-skills
Migrate a test suite from one framework to another, incrementally and without losing coverage.
RStudio Selenium to Playwright Migration
rstudio/rstudio
Converts RStudio Python Selenium electron tests into TypeScript Playwright tests, checking each against a live RStudio before counting it as migrated.
Migrate
alirezarezvani/claude-skills
Migrate from Cypress or Selenium to Playwright. An agent skill from alirezarezvani/claude-skills.
Playwright Pro
alirezarezvani/claude-skills
Production-grade Playwright testing toolkit. An agent skill from alirezarezvani/claude-skills.
More from sickn33/agentic-awesome-skills
All 1,394 skills in this repoLiuguang Banlan UI
sickn33/agentic-awesome-skills
Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.
User Thoughts Memory
sickn33/agentic-awesome-skills
Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.
Using LWC Memory and Graphs
sickn33/agentic-awesome-skills
Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.
Find Complementary Founders
sickn33/agentic-awesome-skills
Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.
Whatsapp Cloud API
sickn33/agentic-awesome-skills
Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.
Cline Pilot
sickn33/agentic-awesome-skills
Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.
Related
Works with
Categories
Questions about Test Framework Migration Skill
What does Test Framework Migration Skill do?
Migrates and converts test automation scripts between Selenium, Playwright, Puppeteer, and Cypress. Test Framework Migration Skill is an agent skill from sickn33/agentic-awesome-skills. Migrates and converts test automation scripts between Selenium, Playwright, Puppeteer, and Cypress.
When should I use Test Framework Migration Skill?
Test Framework Migration Skill fits situations like: tasks that involve Browser testing; tasks that involve Code migrations; tasks that involve End-to-end testing.
How do I install Test Framework Migration Skill in Claude Code?
Run `npx skills add sickn33/agentic-awesome-skills --skill test-framework-migration-skill -a claude-code`. Or copy the skill folder (skills/test-framework-migration-skill in sickn33/agentic-awesome-skills) into .claude/skills/test-framework-migration-skill in your project. Claude Code loads it when a task matches its description.
How do I install Test Framework Migration Skill in Codex?
Run `npx skills add sickn33/agentic-awesome-skills --skill test-framework-migration-skill -a codex`. Or copy the skill folder (skills/test-framework-migration-skill in sickn33/agentic-awesome-skills) into .agents/skills/test-framework-migration-skill in your project. Codex loads it when a task matches its description.
Can I use Test Framework Migration Skill 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 sickn33/agentic-awesome-skills --skill test-framework-migration-skill -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/test-framework-migration-skill, .gemini/skills/test-framework-migration-skill, .github/skills/test-framework-migration-skill and .opencode/skills/test-framework-migration-skill in your project.
What does Test Framework Migration Skill need to run?
SKILL.md names no scripts, command-line tools or credentials: Test Framework Migration Skill is instructions for the agent only.
Does Test Framework Migration Skill access the network?
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Is Test Framework Migration Skill 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 Test Framework Migration Skill use?
Test Framework Migration Skill is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Test Framework Migration Skill use?
About 2.2k tokens (SKILL.md is roughly 8.7k 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 Test Framework Migration Skill?
Skills that share tags, products or a category with Test Framework Migration Skill: Open Browser (JasonHonKL/Openbrowser, 114 stars), Playwright Migration (zebbern/claude-code-guide, 4.6k stars), Test Migration (petrkindlmann/qa-skills, 163 stars) and RStudio Selenium to Playwright Migration (rstudio/rstudio, 5.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Test Framework Migration Skill?
sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,304 GitHub stars. The repository holds 1,394 skills in this directory. The repository was last updated on October 6, 2026.
Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.