If you have ever used Chrome DevTools Recorder or Selenium IDE, the hard part is already done. Drop that export in below and get back a SKILL.md your assistant can replay — in your browser, with nothing to install and no account.
Need a skill for something outside the browser? Record it once on screen and let SkillForge write the SKILL.md — desktop apps, PDFs and spreadsheets included.Drop a Chrome DevTools Recorder export or a Selenium IDE .side file below. The conversion runs entirely in your browser — the file is never sent to us, there is no account, and it works offline once this page has loaded. We verify that rather than just asserting it: a script drops a file containing a unique marker, then inspects every request the page makes — analytics and unload beacons included — to confirm the marker never leaves. It is the same code as the command-line version, generated from the same source, so the two produce byte-identical output.
Drop your recording here
Chrome Recorder JSON or Selenium IDE .side — detected automatically
.side convertersConverters for Selenium IDE projects already exist — sideconv, sel2pup, selenium-side-converter — and if what you want is code, use one of those. They are good at it. Two things are different here:
.side project into Java, Python, C# or Puppeteer, which you then run. This converts it into prose steps an assistant reads and follows. If you want a test suite in a language, you do not want this.Selenium IDE's own export already covers the language targets, so there was no point duplicating that. The gap was a conversion into something an agent can act on, without a toolchain.
npx github:ykzeng-yale/skill-md convert recording.json
It prints the SKILL.md to your terminal. Add --out SKILL.md to write a file instead. It is a zero-dependency Node script under an MIT licence — it runs on your machine, reads one local file, and sends nothing anywhere. There is no key to get and nothing to sign up for.
It accepts two formats, and works out which one you gave it by looking at the contents rather than the file extension:
.side project file.Here is a real conversion, not a mock-up. Input: an eight-step Chrome Recorder export of logging an expense. Output, verbatim:
---
name: log-expense-in-concur
description: Replay a www.concursolutions.com workflow recorded in Chrome DevTools
apps: [Chrome, www.concursolutions.com]
---
# Log expense in Concur
> Converted from a Chrome DevTools Recorder export by skill-md.
## Prerequisites
- Google Chrome
- Access to www.concursolutions.com
## Workflow Steps
### Step 1: Open www.concursolutions.com
Navigate to https://www.concursolutions.com/expense.
### Step 2: Click New Expense
Click "New Expense".
### Step 3: Fill in Expense name
Type "Client lunch" into "Expense name".
### Step 4: Fill in Amount
Type "42.50" into "Amount".
### Step 5: Click Save
Click "Save".
## Notes
3 browser-level steps (viewport, key-up, tab close) were omitted — they describe the browser rather than the task.
Eight recorded steps became five instructions. That reduction is the interesting part.
A recording stores several ways to find each element. Chrome saves an accessibility label alongside the CSS selector, so the same click is available as both aria/New Expense and #new-exp-btn. The converter prefers the label, which is why a step says Click "New Expense" and not Click #new-exp-btn.
This matters more than it looks. A skill is read by a language model and by the person maintaining it. A list of CSS selectors is neither readable nor durable — it breaks the next time a developer renames a class, and when it breaks nobody can tell what it was supposed to do. A label survives a redesign more often, and when it does break the step still says what you were trying to achieve. Selenium locators are ranked the same way: link text and field names first, CSS and XPath only as a last resort.
Both converters remove things, and always report the count in a Notes section so the omission is visible rather than silent.
assertText and friends are dropped, with a count. A test checks that something is true; a skill describes what to do. Turning an assertion into an instruction would invent a step nobody ever performed. If a check matters to you, add it back as a note in your own words.Steps are renumbered after removals, because a gap in the sequence reads to an agent as a step it failed to load.
The converter also validates its own output before writing, so it cannot emit a file that the published validator would reject. You can check any skill yourself with npx github:ykzeng-yale/skill-md validate SKILL.md, or paste it into the validator in your browser if you would rather not open a terminal. If you keep skills in a Git repo, uses: ykzeng-yale/skill-md@v1 checks them on every pull request and flags problems on the line that caused them.
Three cases where you should not use it, and what to use instead:
We sell a screen recorder, so the honest admission is that this tool competes with our own funnel: it produces a SKILL.md without us. We built it anyway, because asking someone to grant screen-capture permission to a site they met a minute ago is a large request, and plenty of people have a recording already sitting on disk. The format is open and so is the converter. If it is all you need, use it and keep nothing from us.
Want to see what you actually get? Download a complete SKILL.md — free, no account, generated from a 34-second screen recording. Hand it to your assistant, or paste it into the validator.
Do I need to install anything?
No. Drop the file on this page and the conversion happens in your browser. There is nothing to install, no account, and no API key. A command-line version exists too if you would rather script it, and both produce byte-identical output because they are generated from the same source file.
Does my recording get uploaded anywhere?
No. The browser version converts the file locally in the page, with no network call, and the command-line version is a local Node script with no network calls at all. Nothing leaves your machine either way, and there is no account.
Do I need SkillForge to use this?
No. The converter and the SKILL.md spec are both MIT-licensed and work standalone. SkillForge is useful when there is no recording to convert because the work is not confined to a browser tab.
How do I export from Chrome DevTools Recorder?
Open DevTools, choose the Recorder panel, click Create a new recording, perform your flow, then stop and use the export button to save it as a JSON file. Pass that file to the convert command.
My Selenium project has several tests. Which one is converted?
The first one, and the command tells you the names of the others. Use --test followed by the test name to convert a specific one.
Why were my assertions removed?
Because a skill is a procedure, not a test. An assertion records something you wanted to be true, not an action you performed, so emitting it as a step would describe work that never happened. The count is reported in the Notes section so you can add the important checks back in your own words.