Skill Runner

Get started

Search for the job in plain words, open a matching skill, then paste input and run. This page teaches that loop so you can try it without pinging whoever invited you.

How it works

Three chapters. Seek any one; the summary stays visible if you skip ahead.

  1. Search — describe the job in the Catalog search box.
  2. Open a skill — pick a match and read how it fits.
  3. Try a run — paste input and run (add an API key in Settings first if needed).

Chapter 1 of 3

Search

In Catalog, type the job in plain words — “roast my landing page”, “what’s broken in production” — not the skill’s name.

Example jobs

Each link opens Catalog with that search already filled in. Prefer the roasting example for your first try.

FAQ

How do I run a skill?
Open Settings, paste an OpenRouter API key from openrouter.ai/settings/keys, then pick a skill and run. This page is not an installer — just a pointer to Settings.
What do Adapted vs Local mean?
  • Full — Runs end to end from what you paste here.
  • Adapted — Parts of this skill expect files, a shell, or a browser. It works from your input and returns any files inline.
  • Local — Built for a local coding agent (filesystem, shell, browser). Here it produces a plan or dry run; run it locally for the real thing.
Where is history?
Off. Set DATABASE_URL to a Neon connection string and run npm run db:push to turn it on. Open history. After Settings, Catalog’s Get started opens the skills map; from there you can pick a job stage, then continue here for the search → skill → try loop.
Why might I see a password screen?
Some shared instances are password-protected. Enter the password you were given once, then continue to the Catalog or Settings.
Whose API key pays for a run?
Runs use the OpenRouter key you add in Settings and are billed to you. There is no host key. Your key is stored in a cookie in your browser. See Settings for details.