Skip to main content
A skill is a short document written for an agent rather than a person: what a system is, how to authenticate, the handful of calls that matter, the encodings that trip agents up, and the guardrails to keep. An agent that has read the skill can use the system without having read the reference. Every skill page here is also published as plain Markdown at the same path with a .md extension, which is the form an agent should fetch:

The skills

Loading a skill

Each skill opens with YAML frontmatter — name, description — so a harness that indexes skills by description can pick the right one from the task alone.

Skills and MCP servers

A skill tells an agent how to think about a system; an MCP server gives it tools to act on one. They pair: the skill names which tools to prefer, which to preview before running, and which take an idempotency key. Load the skill, connect the server.

Writing your own

The skills above share a shape worth copying: what the system is in two sentences, how to connect, the two or three calls that cover most work, the encodings that break, the rule to keep. Under a hundred and fifty lines. A skill that tries to be the reference is one the agent will not finish reading.