AI tool comparison
Matt Pocock Skills vs Skrun
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 Skills
21+ battle-tested Claude agent skills from TypeScript's top educator
75%
Panel ship
—
Community
Free
Entry
Matt Pocock — known for Total TypeScript and beloved among frontend developers — has published his personal directory of Claude agent skills straight from his own `.claude` directory. The repository contains 21+ modular skills organized across four areas: Planning & Design (to-prd, to-issues, grill-me), Development (tdd, triage-issue, improve-codebase-architecture), Tooling (setup-pre-commit, git-guardrails-claude-code), and Writing & Knowledge (edit-article, ubiquitous-language, obsidian-vault). Installation is a single command — `npx skills@latest add mattpocock/skills/[skill-name]` — and each skill is a self-contained module that plugs into Claude Code or similar agent runners. The repository blew up on GitHub trending today with 857 stars, reflecting how hungry developers are for curated, production-tested skill templates from people who actually use them daily. What makes this different from generic awesome-lists is the editorial voice — these are skills Pocock actually uses in his content production workflow. The `edit-article` skill, `write-a-skill` meta-skill, and `obsidian-vault` integration reflect real non-code use cases that most developer-focused skill repos ignore entirely. MIT licensed.
Developer Tools
Skrun
Deploy any agent skill as a production REST API in one command
50%
Panel ship
—
Community
Paid
Entry
Skrun is an open-source tool that wraps agentic skills — the discrete, reusable capabilities you build for AI agents (web search, data extraction, file transformation, API calls) — into deployable REST APIs with a single command. The idea is that skills you build for one agent context shouldn't be locked to that agent's runtime. With Skrun, you define a skill once with a standard function signature, and get a hosted endpoint with automatic request validation, retry logic, rate limiting, and an OpenAPI spec generated automatically. The project addresses a real architectural tension in the current AI tools ecosystem: agent skills are written in a dozen different formats (LangChain tools, MCP tools, function call JSON, OpenAI tool specs) and are essentially stranded assets — they only work within their specific orchestration framework. Skrun normalizes this by wrapping any skill definition format and exposing it as a framework-agnostic HTTP endpoint that any agent or pipeline can call. This appeared on Hacker News with a small but thoughtful discussion focused on the "skills as microservices" architectural pattern. Critics noted that adding HTTP round-trips to every tool call introduces latency; proponents argued that the composability and reusability benefits outweigh the cost. The early version focuses on stateless skills; stateful/conversational skill deployment is on the roadmap.
Reviewer scorecard
“The TDD skill and git-guardrails-claude-code alone are worth the install. Pocock's skills reflect how a TypeScript professional actually works — not generic demo code. The npx install pattern is elegant and composable.”
“The framework portability angle is the real value prop — I have dozens of custom tools built for Claude that I can't reuse in other contexts without rebuilding them. If Skrun actually normalizes this cleanly across tool formats, that's a genuine pain solver.”
“This is one person's personal workflow, not a maintained framework. Skills will drift as Claude updates and Pocock's priorities shift. You're better off building your own SKILL.md files once you understand the pattern.”
“Wrapping every agent skill in an HTTP call is a latency antipattern — a skill that takes 50ms locally becomes 120ms+ through a hosted endpoint with cold starts. For skills called hundreds of times per agent run, this adds up fast. I'd want colocation support before using this in production.”
“When influential developers publish their agent workflows publicly it accelerates the entire ecosystem's skill vocabulary. This is how best practices emerge — through high-signal personal repos from trusted practitioners.”
“Skills-as-services is the right architectural direction as agent ecosystems mature. The future is marketplaces of composable agent capabilities that any orchestrator can call — Skrun is early infrastructure for that world.”
“The edit-article and ubiquitous-language skills are gems for anyone who writes documentation or content alongside code. Having a creator's perspective embedded in a developer's skill repo is refreshingly rare.”
“Too deep in infrastructure for my workflow, but the auto-generated OpenAPI spec is a nice touch for anyone who needs to share custom skills with a team without writing documentation manually.”
Weekly AI Tool Verdicts
Get the next comparison in your inbox
New AI tools ship daily. We compare them before you waste an afternoon.