Curated tools, libraries and resources worth remembering. Read the one file that fits the question, not the whole set.
By kind — the default home for an entry:
| File | What's in it |
|---|---|
| mcp-servers.md | MCP servers — capabilities Claude Code lacks natively |
| plugins.md | Claude Code plugins from the official marketplace |
| skills.md | Standalone agent skills |
| libraries.md | Code libraries, UI ecosystems, browser automation |
| apps.md | Desktop and productivity apps |
By domain — when a cluster outgrows the kind files:
| File | What's in it |
|---|---|
| video.md | Making, cutting and understanding video |
Where does a new entry go? Kind at the file level, domain at the section level —
skills.mdgroups UI/design and SEO internally rather than splitting. A domain only graduates to its own file when its tools span several kinds and substitute for each other, so no kind file can hold the comparison. Video qualified: a skill, three plugins, a CLI and a library all doing overlapping jobs. Most things won't.
Snapshot: mid-2026. This ecosystem churns fast — check a repo's recent activity before installing, especially community entries. Treat every MCP server and skill as executable code you're granting access to: skim the source and scope credentials tightly.