Turning Claude into a Productivity Beast: My Take on mattpocock/skills

I’ll be honest — I never took Claude Code’s Skills feature seriously. I figured it was just saving a few prompt templates, how useful could that really be? Then I stumbled across mattpocock/skills on GitHub Trending with over 61,000 stars and thought, okay, what’s the deal here?

Turns out Matt Pocock — yeah, the Total TypeScript guy — open-sourced his entire .claude directory. We’re talking real workflows he actually uses, not some generic AI tips you can find on Reddit. That got my attention.

What I actually tried from the productivity skill

The repo organizes skills by scenario. I dug into the productivity folder, which packs three mini-tools:

caveman — Ultra-compressed communication. The idea is simple: make Claude drop all filler and get straight to the point, cutting token usage by roughly 75%. I asked it to review some code I wrote. Normally Claude starts with “This is an excellent question, let me analyze…” but with caveman enabled it just spat out: “Line 14 closure leak, switch to const.” Honestly? Kind of refreshing. But also a bit dry — it works best when you already know the context and just need quick confirmation.

grill-me — This one’s my favorite. You feed Claude a plan or design doc, and it interviews you relentlessly until every branch of the decision tree is resolved. I tested it with a technical proposal, and it fired off seven or eight questions, a few of which I genuinely hadn’t considered. “What’s your fallback if the third-party API times out?” — yeah, that wasn’t in my draft. I see this as a perfect pre-meeting sanity check before sending anything to leadership.

write-a-skill — Scaffolds new skills with proper structure, progressive disclosure, and bundled resources. Probably the most practically useful of the three, since writing good skill files has a learning curve and this just gives you the template.

How to set it up

Clone the repo and copy whatever skill directories you want into your project’s .claude/ folder. Claude Code picks them up automatically on startup. Each skill has a SKILL.md with usage examples.

git clone https://github.com/mattpocock/skills.git
cp -r skills/skills/productivity ~/.claude/skills/

MIT licensed, so use it however you want.

The honest pros and cons

What I liked:

• These aren’t generic prompts — they’re battle-tested workflows
• caveman genuinely saves tokens, and I noticed the difference on longer sessions
• grill-me asks smart questions, not the template-style “please elaborate”
• Clean repo structure, easy to reference when writing your own skills

What I didn’t love:

• Only makes sense if you’re already using Claude Code — Cursor and Copilot users are out of luck
• caveman’s high information density can feel stripped of context sometimes
• Some skills assume specific project structures, so you’ll need to adapt them

Who’s this for?

If you’re already living in Claude Code day-to-day, this repo is pretty much a no-brainer. caveman saves you money, grill-me catches your blind spots. If you haven’t tried Claude Code yet, 61k stars probably won’t convince you — this is more like upgrading to a better engine, not teaching someone to drive.

I browsed the other directories too — code-quality, testing, and more. Planning to try them out over the next couple weeks. If anything stands out, I’ll write about it.

---

About the Author

Liudingyu is a full-stack developer and heavy GitHub user. With 900+ starred repos over the past 3 years, this site only covers tools I’ve actually used or deeply researched.

📧 Found a great tool to recommend? Email [email protected]