Skills 101 — why a skill pack beats a pasted prompt

Everyone who works with agents ends up with a prompt file. The one that finally got the research summary right. The one that makes the model stop writing like a press release. It lives in a scratch document, gets pasted at the top of a session, and slowly rots as the tools around it change.

A skill pack is that file, except your agent picks it up itself and the tools it depends on are guaranteed to be there.

What is actually in one

A pack is three things:

A procedure. Written in plain language, as steps — not a personality prompt. "Search these sources, discard anything older than a week, extract the claim and the link, write it up in this shape." The kind of thing you would hand a competent new hire.

A declared tool list. The pack says which Router9 tools it calls — image.generate, web.search, the memory tools. This is not documentation. It is what makes the pack safe to follow: an agent that cannot reach a required tool is never shown the pack, so it can never be told to call something that answers "tool not found".

Supporting files. Templates, reference material, occasionally a script. Shipped as a signed archive with a digest, so you can check what you downloaded is what was published.

Why not just paste the prompt

Three reasons, in the order they start to hurt.

A pasted prompt has no tools behind it. "Search the web and cite your sources" is a sentence, not a capability. The pack version arrives with web.search already reachable through the same key.

A pasted prompt is a copy. When you improve it, every copy in every scratch file is now the old version. Packs are versioned — each revision is a distinct published thing, and the one you download tells you which it is.

A pasted prompt is one you have to remember to paste. This is the real one. The value of a good procedure is highest exactly when you have forgotten it exists.

Installing one

Two steps, and the second is the one people skip.

Download the pack from its page on /skills into your agent's skills directory. Each pack ships as a skill.zip with a manifest listing every file and its digest.

Point the same agent at Router9 over MCP, so the tools the pack calls are actually there when it follows the steps:

{
  "mcpServers": {
    "router9": {
      "type": "http",
      "url": "https://api.router9.com/v1/mcp",
      "headers": {
        "Authorization": "Bearer sk-r9k-..."
      }
    }
  }
}

A pack installed without the second step will read correctly and then fail at the first tool call. If a skill seems to "not work", check this first.

Two to start with

Agent Memory KitGive your agent a memory worth reading back.

Memory is the one that changes how a session feels. Without it every conversation starts from nothing; with it, the agent knows what you decided last week and why.

Research BriefSearch the live web, read what it turns up, publish a cited brief.

The best demonstration of why the tool list matters. It is not a prompt asking the model to recall things — it searches, reads, and cites, because the tools to do that are reachable.

The full catalog has ten, filed by the job they do.

Writing your own

Nothing about the format is proprietary. A pack is a procedure, a tool list, and some files. If you have a prompt that has earned its place in your workflow, it is most of a pack already — the work is writing down the steps you have been holding in your head, and naming the tools they depend on.