Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →rome-os/import-skill
Import a Rome skill from a URL, a pasted SKILL.md, or a plain-language description — validate it against Rome's frontmatter parser, preview the final file, and install it into the user-skills carrier app after the guardian confirms.
Passed 17 of 22 test cases with the skill, and 7 of 22 without it.
and 12 more in the full report
11 fixed6 passed either way4 still failing1 broke4 errored
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
I added the directory `skills/docker-cleaner` with a valid `SKILL.md` inside `user-skills`. What update is required in `user-skills/app.yaml` before committing?
| Checked | Without skill | With skill |
|---|---|---|
| Appends skills/docker-cleaner to the skills array in app.yaml | Missed | Passed |
The instructions your model reads when the skill loads.
Turn what the guardian brings you into something installed — a URL to an existing skill, a pasted SKILL.md, or a description of one they wish existed. Brainstorm with them: propose, listen, revise. Don't install anything without getting a clear go-ahead.
Most of what you're handed is a plain skill for the user-skills carrier. The involved ones — a setup step, real interaction, a multi-step process — are better off as their own app. Sorting which is which, with the guardian, is part of the job: see "Skill, or a dedicated app?" before you install.
github.com/<owner>/<repo>/blob/<ref>/<path> → fetch the raw form
https://raw.githubusercontent.com/<owner>/<repo>/<ref>/<path>.github.com/<owner>/<repo>/tree/<ref>/<dir> → list it via
https://api.github.com/repos/<owner>/<repo>/contents/<dir>?ref=<ref> and
download the SKILL.md plus its auxiliary files.SKILL.md at the root, then under skills/.If the source holds more than one skill (several SKILL.md under skills/, a
repo of them, a page linking many), don't pick for the guardian: list each one
you found — path, name, and description — and ask which to import. They may
choose one, some, or all; import each as its own pass through the rest of this
flow (validate → preview → install), so every skill gets its own confirmation.
On a network error or 404, say so and ask for a corrected link.
test cases passed, vs 7 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.