Agent Skills
AnthropicThe reference collection: document, spreadsheet, and slide skills from the team that defined the format.
Every entry is checked against the vendor's own documentation, dated, and given a one-line verdict on who it actually suits. No scraped blurbs, no dead links, no "top 100" padding.
A set of product-specific servers from Cloudflare covering observability, DNS, Workers, and account configuration. They are hosted, so there is no local process to k…
Searches and reads Confluence pages and spaces through the API. The value is retrieval: the answer to a process question usually exists in a page nobody searches by …
An official server exposing ElevenLabs text-to-speech, voice listing, and audio generation as tools. The useful pattern is narration inside a content pipeline: scrip…
Gives an agent scoped read, write, and search access to directories you explicitly allow. It is the reference implementation for local file work: you pass one or mor…
Reads and writes spreadsheet ranges through a sheet-scoped grant: list sheets, read a range, append rows, update cells. It is the fastest way to give an agent a huma…
The reference collection: document, spreadsheet, and slide skills from the team that defined the format.
Official skill for generating art as code — procedural patterns instead of image prompts.
Derive contract tests from an API description, not from the implementation.

The problem the protocol solves, in terms of the alternative you were probably using: custom integrations per client.

The config file, the three values that actually matter, and how to know it worked.

A folder with a SKILL.md the agent loads on demand — closer to a training manual than a plugin.

Bluesky and Mastodon are readable at scale and postable with one call. The gap between those two facts is a policy, not a permission…

Pipedrive, Attio, and Clay each hold a different slice of the same account. The useful output is one page before the call. The pre-call…

Loom, Miro, and Confluence hold the work a team did but never wrote down. Three servers, one job: extract it before it decays. Async…
Slack is where work conversations live; Discord is where communities do. The agent follows the people.
Tavily returns answers with sources; Firecrawl returns pages as clean text.
Redis answers in microseconds; Postgres answers questions. An agent needs to know which it is asking.
Every entry is dated. Reviewed entries were read by a person; the rest are compiled from the npm registry and labelled. How verification works →