AI tool comparison
Skills (mattpocock) vs Vera
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
Vera
A programming language designed for machines, not humans
50%
Panel ship
—
Community
Paid
Entry
Vera is a programming language built from the ground up for LLMs to write — not humans. Named after the Latin word for truth, it compiles to WebAssembly and runs in both the CLI and browser. Its most radical design choice: it eliminates variable names entirely, replacing them with typed De Bruijn structural references (like `@Int.0` for the most recent integer binding). Research suggests naming confusion is one of the biggest failure modes in AI-generated code — Vera removes the problem at the language level. Every function in Vera must declare `requires()` preconditions, `ensures()` postconditions, and `effects()` side-effect declarations. The compiler uses Z3 formal verification to check contracts at every call site, meaning the AI can't ship code that violates its own preconditions. Error messages are structured JSON with stable codes — written as instructions for AI systems to parse and fix, not human developers to read. Benchmark results are striking: on VeraBench, Kimi K2.5 achieves 100% correctness writing Vera code, outperforming both Python (86%) and TypeScript (91%) implementations. At v0.0.127 with 810+ commits, 127 releases, 3,638 tests, and a 13-chapter spec, this is a serious project — not a weekend experiment. If AI is going to write most of our code, perhaps the code should be designed for AI to write.
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.”
“The contracts-first approach is genuinely compelling — I've spent too many hours debugging AI-generated code that violated implicit invariants. Having the compiler enforce preconditions at every call site is the kind of guardrail I'd actually trust. The WASM compilation target means you can run this anywhere, and 3,638 tests suggests this isn't vaporware.”
“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.”
“A language with no variable names sounds like an academic exercise, not something that'll ship real software. Even if LLMs do great on VeraBench, the ecosystem is zero — no libraries, no community, no integrations. You'd be asking your team to maintain code written in a language nobody else on Earth can read. That's a hard sell even if the AI loves it.”
“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.”
“Vera represents a fundamental rethink: what if programming languages were designed for their actual authors in 2026 — which are predominantly AI systems? The formal verification backbone means AI-generated code carries a proof of correctness, not just a vibe. This is early, but the trajectory points to a world where AI writes formally verified software by default.”
“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.”
“I love the philosophical angle — a language where the 'author' is the machine. But until there's a visual toolchain, a debugger humans can read, and something I can demo to a client, this lives in research territory. The JSON error messages designed for AI systems are clever but leave human reviewers completely out of the loop.”
Weekly AI Tool Verdicts
Get the next comparison in your inbox
New AI tools ship daily. We compare them before you waste an afternoon.