AI tool comparison
Skills (mattpocock) vs tldr MCP Gateway
Which one should you ship with? Here is the side-by-side panel verdict, pricing read, reviewer split, and community vote comparison.
Developer Tools
Skills (mattpocock)
Real-world agent skills for engineers — install via npm, not vibes
75%
Panel ship
—
Community
Free
Entry
Skills is a curated library of AI agent prompts and workflows for real software engineering, created by TypeScript educator Matt Pocock. The project trended to 28,000 GitHub stars with its blunt tagline: "Agent skills for real engineers — not vibe coding." It's a deliberate pushback against chaos-first AI coding in favor of structured, methodical engineering. The library organizes into four categories: Planning & Design (to-prd for converting conversations into PRDs, grill-me for stress-testing plans), Development (tdd for test-driven AI assistance, triage-issue for bug investigation), Tooling & Setup (pre-commit hooks, git safety guards), and Writing & Knowledge (documentation utilities, Obsidian integration). Each skill installs with a single npx command — npx skills@latest add mattpocock/skills/tdd — and plugs into Claude agent setups. With 28,000 stars and 2,200 forks after trending on GitHub on April 27, 2026, Skills has clearly struck a nerve. It's as much a cultural statement as a product: AI coding tools should be used deliberately, with tests, with planning, and with guardrails. The TDD and triage-issue skills address real gaps in how current AI coding agents handle existing codebases rather than greenfield projects.
Developer Tools
tldr MCP Gateway
Shrink 41+ MCP tool schemas by 86% before they hit your model
75%
Panel ship
—
Community
Paid
Entry
tldr is a local proxy that sits between your AI coding harness and upstream MCP servers, solving one of the most underappreciated problems in agentic workflows: context bloat from tool schema proliferation. When you connect GitHub MCP, filesystem MCP, and a few others, you can easily be sending 24,000+ tokens of tool schemas to the model before any work begins. Instead of passing all those schemas directly, tldr exposes exactly five wrapper tools to the model: search_tools, execute_plan, call_raw, inspect_tool, and get_result. The model learns which underlying tools exist on-demand through search_tools, then calls them through the proxy. GitHub MCP's 24,473-token schema surface compresses to 3,482 tokens — an 86% reduction. Output responses are further compressed through field stripping, a 4,096-token cap, and a 64KB byte limit. This is a genuinely practical solution for power users running multi-MCP setups who've noticed degraded performance as their tool count grows. The tradeoff is one extra hop of indirection, but the token savings pay for themselves in improved model attention and lower API costs.
Reviewer scorecard
“The tdd skill alone is worth the install. Watching a Claude agent plan tests before writing implementation is exactly how I want AI to assist me. Matt's framing of 'real engineering vs. vibe coding' is the right cultural correction for 2026.”
“This solves a real problem I've hit personally — when you connect enough MCP servers, you're wasting a quarter of your context window on tool definitions before a single line of code is written. The five-wrapper-tool approach is elegant and the compression numbers are concrete and reproducible.”
“These are sophisticated markdown prompts, not magic. If you're already a disciplined engineer, the skills add ceremony without much acceleration. The 28K stars partly reflect Matt's Twitter following — evaluate the actual skills before star-chasing.”
“This is a workaround for a problem that MCP server authors and model providers should fix natively. Adding another proxy layer to your local development setup increases debugging complexity, and the 4,096-token output cap could silently truncate important data from tool responses.”
“Community-curated skill libraries installed via package managers will become standard infrastructure — as natural as installing a linting config. Skills is the early prototype of a skills ecosystem that will matter at scale.”
“Schema proliferation is becoming a real scalability ceiling for agentic systems. tldr's dynamic tool discovery approach — where the model learns which tools exist on-demand — hints at how future agent routing layers will work at scale across hundreds of specialized MCP endpoints.”
“The writing and knowledge skills are underrated. The article-editing and Obsidian integration skills bring structured AI assistance to documentation workflows that most agent tools ignore entirely. Install even if you're not primarily a developer.”
“For anyone using AI agents to manage creative workflows across multiple platforms, the context savings translate directly to more coherent, focused outputs. Less schema bloat means the model spends more attention on your actual task.”
Weekly AI Tool Verdicts
Get the next comparison in your inbox
New AI tools ship daily. We compare them before you waste an afternoon.