AI tool comparison
Matt Pocock's Skills vs Rubber Duck
Which one should you ship with? Here is the side-by-side panel verdict, pricing read, reviewer split, and community vote comparison.
Developer Tools
Matt Pocock's Skills
Reusable Claude agent skills that fix AI coding's biggest failure modes
75%
Panel ship
—
Community
Free
Entry
Matt Pocock — the TypeScript educator behind Total TypeScript — dropped a GitHub repo that's currently the #2 trending project on all of GitHub with 7,300+ stars in a single day. It's a curated collection of reusable agent skills for Claude Code and other coding agents, installable with one line: `npx skills@latest add mattpocock/skills`. The skills tackle the four canonical failure modes of AI-assisted development: misalignment (agents build the wrong thing), verbosity (context windows bloated with unnecessary tokens), broken code (no feedback loops), and poor design (architecture degrades over time). Each skill is a focused slash command — `/grill-me`, `/tdd`, `/diagnose`, `/improve-codebase-architecture` — that guides agents through professional engineering practices rather than just writing code. What makes this land differently is Pocock's framing: he argues software engineering fundamentals matter more than ever in the agent era, not less. The repo is built around the insight that agents need structured methodology, not just raw capability. With over 3,200 forks in 24 hours and widespread adoption reports, this is shaping up to be the de facto starting point for anyone building a serious `.claude` directory.
Developer Tools
Rubber Duck
A second AI model reviews your Copilot agent's plan before it ships code
75%
Panel ship
—
Community
Paid
Entry
Rubber Duck is a new capability in the GitHub Copilot CLI agent workflow that introduces cross-model code review. When Copilot's primary agent generates a plan or implementation, Rubber Duck routes that output to a second AI model from a different provider family for an independent review — catching architectural mistakes, edge cases, and logic errors before any code is committed. The name is a nod to rubber duck debugging, but the mechanism is more like adversarial collaboration: the reviewing model has no stake in the primary model's plan and no context about why certain decisions were made. It approaches the output fresh, which is precisely where different models excel — a model that didn't generate a plan is much better at finding its flaws than the model that created it. This is a meaningful shift in how AI-assisted development works. Most AI coding tools use a single model throughout the entire workflow. Rubber Duck introduces model diversity as a quality-control mechanism, acknowledging that no single AI has perfect judgment and that cross-checking is standard practice in human code review for good reason. It's available now as part of GitHub Copilot CLI.
Reviewer scorecard
“This is the missing manual for working with coding agents. The /tdd and /grill-me skills alone have already changed how I approach agent sessions — I actually get working code on the first pass now instead of a beautiful-looking mess that fails every test.”
“The insight here is sharp: models are worst at finding their own mistakes. Using a second model as an independent reviewer is the right call, and it mirrors how good human code review actually works. I want to know which model pairs GitHub is using — the quality of the adversarial check will depend heavily on choosing models with genuinely different failure modes.”
“Slash commands in a shell script repo going viral is classic GitHub hype. These are just prompts dressed up as methodology — any senior engineer could write these in an afternoon, and half your team will ignore them after week two. The stars reflect Pocock's brand, not necessarily the utility.”
“This doubles your inference cost for every agentic operation, and GitHub hasn't published latency numbers. If the cross-model review adds 10-15 seconds to every agent step, it'll be disabled by most developers within a week. Catch rates vs. latency overhead is the key tradeoff and it hasn't been benchmarked publicly yet.”
“We're watching the emergence of a skills economy for AI agents. Pocock's repo is an early proof-of-concept that reusable, composable agent skills are a real category — the npm of agent methodology. Whoever wins this space wins a huge chunk of the developer toolchain.”
“Model ensembling for quality control is the obvious next step in agentic AI workflows, and GitHub shipping it in Copilot normalizes the pattern. In two years, single-model agent pipelines will feel as naive as shipping code without CI. Rubber Duck is the CI layer for agentic code generation.”
“The /caveman ultra-compressed mode is genuinely clever for large codebases where token limits bite. As someone who spends half my life fighting context windows, the CONTEXT.md shared domain language approach deserves its own talk at every dev conference this year.”
“Honestly, I'd love this for writing. Having a second AI with a completely different perspective review a draft before it goes out catches things the primary model is blind to — that's just good editing practice. The name 'Rubber Duck' is perfectly chosen; it captures the spirit of the feature better than any technical description could.”
Weekly AI Tool Verdicts
Get the next comparison in your inbox
New AI tools ship daily. We compare them before you waste an afternoon.