Most sites put tutorials in a blog and hope they rank. Ours are structured as a curriculum, and the structure is the point: every lesson ends at a tool or a comparison, because the questions a tutorial answers are the questions that make someone open a listing.
Four tracks, ordered by level
**Using agents** — for people who have used a chat window and want to delegate something. **MCP servers** — install, debug, evaluate, and eventually write one. **Skills and prompts** — authoring instructions that change behaviour. **Running agents in production** — cost, evaluation, and guardrails.
The levels are not decoration. A level 1 lesson assumes you have never configured a JSON file; a level 3 lesson assumes you are shipping to people who are not you.
Why each lesson ends with a next step
A summary is where reading stops. Every lesson here ends with the next lesson or a tool page, because the goal is not completion — it is the next question.
The lessons we will not write
**'10 prompts that will change your life.'** Prompt lists without a constraint are entertainment; ours carry the rules that make them work and the line to change.
**Model benchmarks.** By the time a comparison is written the models have moved.
**Anything that requires a product we do not cover.** A tutorial that ends in an affiliate link is the pattern this site exists to avoid.
The measure we care about
Not completion rate. Whether someone who read the MCP install lesson then opened an MCP server page — because that is the moment the directory was useful rather than decorative.