AI tool comparison
Skills (mattpocock) vs Yggdrasil
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
Yggdrasil
Turns your CLAUDE.md rules from suggestions into enforced constraints
75%
Panel ship
—
Community
Paid
Entry
Yggdrasil addresses a persistent problem with AI coding agents: rules files like CLAUDE.md or .cursorrules are advisory, not enforceable. Agents ignore rules roughly 30% of the time, and violations surface only during code review — if at all. Yggdrasil transforms architectural constraints into an active verification loop that runs before code reaches review. Developers define rules in plain Markdown as 'aspects' — high-level requirements like 'all payment operations must emit audit events' or 'no direct database access from the UI layer.' These capture architectural and business logic constraints that traditional linters cannot express. When an agent generates code, it runs 'yg approve,' which sends the code and relevant rules to a reviewer LLM that checks compliance and returns specific violations. The agent fixes issues and re-verifies — all autonomously. Intelligent rule scoping delivers only the 3-5 rules relevant to each file rather than overwhelming the agent with a full ruleset. CI integration via hash comparison requires no LLM calls at the gate, keeping enforcement costs low. Yggdrasil supports Cursor, Claude Code, GitHub Copilot, Cline, and RooCode, with reviewer providers including Anthropic, OpenAI, Google, and Ollama.
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.”
“CLAUDE.md files and .cursorrules are basically suggestions that agents ignore whenever they feel like it. Yggdrasil makes rules enforceable: the agent writes code, runs 'yg approve', gets specific violations back, fixes them, and re-verifies before the code ever reaches review. The intelligent scoping that shows agents only the 3-5 relevant rules per file instead of all 200 is the kind of practical detail that shows the builders understand how context windows actually work. CI integration via hash comparison (no LLM calls) means enforcement doesn't cost anything at the gate.”
“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.”
“The core pitch — 'rules files are just suggestions, we make them real' — is right. The implementation is another LLM-judges-LLM system, which means your architectural guardrails are only as reliable as your reviewer model's understanding of your codebase context. Writing 200 rules in plain Markdown sounds accessible until you realize that ambiguous natural language rules produce inconsistent enforcement, and debugging why 'yg approve' rejected code that looks fine requires reading LLM reasoning. Traditional static analysis and typed interfaces enforce constraints deterministically; this enforces them probabilistically.”
“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.”
“As teams grow their CLAUDE.md files from 50 to 500 lines trying to wrangle agent behavior, Yggdrasil represents the next evolution: from instructional to contractual. The architecture prefigures a world where codebases have machine-enforced behavioral specifications at multiple levels — security, performance, style — that any agent (or human) must pass before merging. This is what software governance looks like when AI writes most of the code.”
“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 design systems work where 'all UI components must use tokens, never raw hex values' is a rule that gets violated constantly by AI agents, having an enforcement loop that catches violations before PR review would save hours of back-and-forth every week. The natural language rule definition means designers can contribute guardrails without learning a DSL.”
Weekly AI Tool Verdicts
Get the next comparison in your inbox
New AI tools ship daily. We compare them before you waste an afternoon.