What specific automation does this skill provide for test migrations?

The skill converts .robot files into idiomatic Playwright TypeScript code, automatically mapping syntax, BDD structures, and library calls (like SeleniumLibrary) into modern Playwright assertions.

How does the skill handle different Robot Framework libraries?

The converter handles standard Robot Framework libraries like SeleniumLibrary, Browser Library, and RequestsLibrary, translating their logic into native Playwright and Axios-style requests.

What happens if I have custom Python keywords or complex third-party libraries?

While it attempts to map custom keyword logic, complex Python-based libraries it cannot resolve are marked with clear // TODO comments so you can manually finalize the transition.

Will my original test structure and BDD styles be preserved after conversion?

Yes, the skill is designed to recognize and preserve BDD (Given/When/Then) structures, converting them into organized Playwright test blocks or descriptive comments to maintain readability.

What files will I receive at the end of the conversion process?

The output is a set of production-ready .spec.ts files, along with necessary scaffolding like playwright.config.ts and package.json to help you get your new suite running immediately.

How are updates and new Playwright version support handled?

Updates to the conversion logic are provided periodically to support the latest Playwright features and Robot Framework keyword updates; these are automatically available through your AI agent interface.

Works with the AI tools you already use

+20 more

+17 agents

Robot to Playwright Converter

Most 'migrations' rewrite your tests from scratch. This one maps your existing keywords and locators automatically.

Free

3 installsSecurity scanned

robot-to-playwright-converter

Example session with this skill installed

Convert login_tests.robot to a Playwright spec. Use BDD comments for the steps. The original test goes to /login, fills 'admin' into Username, and checks if the URL contains 'dashboard'.

Read your context and instructions
Compiled the robot-to-playwright-converter

test('User can login', async ({ page }) => {
// Given user is on login page
await page.goto('/login');
// When user enters credentials

  await page.getByLabel('Username').fill('admin');
  await page.getByRole('button', { name: 'Sign in' }).click();

// Then dashboard is visible

  await expect(page).toHaveURL(/.*dashboard/);
});

Connects securely to your tools. The creator never sees your data.

About this skill

Migrate from Robot Framework to Playwright with Intelligence

Moving a legacy test suite from Robot Framework to Playwright is a massive undertaking. This skill automates the heavy lifting by converting .robot files into idiomatic, high-quality Playwright TypeScript. It doesn't just swap syntax; it understands test intent, preserves BDD structures, and maps complex Robot keywords to web-first Playwright assertions.

What it does

Converts Robot Framework test cases and keywords into modern Playwright specs.
Intelligently handles SeleniumLibrary, Browser Library, and RequestsLibrary mappings.
Detects and preserves original test styles, whether they are BDD (Given/When/Then) or procedural.
Translates Robot's complex variable syntax and control flows (FOR, IF, WHILE) into clean TypeScript.
Generates necessary scaffolding including playwright.config.ts and package.json if missing.

Why developers use this skill

Unlike basic search-and-replace scripts, this skill acts like an experienced QA engineer. It prioritizes "web-first" assertions that reduce flakiness and automatically identifies opportunities for Page Object Models. It handles the nuances of the Playwright lifecycle, such as ensuring browser contexts are managed correctly in suite setups, preventing common migration pitfalls like SecurityError in teardowns.

Output format

The result is a set of compilable .spec.ts files. Any custom Python libraries or ambiguous locators that cannot be safely converted are automatically flagged with // TODO comments, allowing you to finalize the migration without losing context.

How to install

Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

~30 seconds

1
Download the ZIP
Free skills download straight away. Paid skills unlock right after purchase.
2
Unzip into your skills folder
Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.
3
Ask your agent to use it
Restart the agent if it was already running. It picks the skill up automatically - no config needed.

Skills folder by agent

Click the path to copy it. Create the folder if it does not exist yet.

Reviews

No reviews yet

Be one of the first to try it. Every listed skill passes our trust checks below.

Security scanned

Passed our 8-point scan before listing

3 installs

Downloaded by developers to date

Free forever

No account required to browse

Trust & safety