You’ve just deployed Claude Code inside VS Code. Now the real question: which skill should you install first?
The community has converged on a clear answer. Start with find-skills and Superpowers.
This guide explains why, gives you a battle‑tested priority list, and shows the exact commands to get productive in minutes.
Why these two come first
find-skills is the only skill you need to discover every other skill.
It turns hours of searching into a single natural‑language query. With over 200,000 skills in the ecosystem,
you don’t want to guess — you want a map. That’s find‑skills.
Superpowers (also known as the “Anthropic‑style plugin”) is not one skill but a complete
engineering methodology. It forces Claude to follow a disciplined workflow: planning, test‑driven development,
quality checks, and safe refactoring. It turns the assistant into a junior engineer you can trust with complex tasks.
Quick install (copy‑paste these)
npx skills add https://github.com/vercel-labs/skills --skill find-skills
💬 Inside Claude Code (VS Code chat)
/plugin install superpowers-skills@anthropics-claude-code
/reload-plugins
(Optional Chinese‑optimised version: /plugin install superpowers-zh@jnMetaCode)
📋 The complete priority list (next skills to add)
| Skill name | Core value | When you need it |
|---|---|---|
| caveman | Drastically compresses prompts → lower token cost | You pay per token or hit rate limits often |
| everything-claude-code | All‑in‑one agent framework (safety rails, TDD, memory) | You want a professional, production‑grade setup |
| andrej-karpathy-skills | Stops over‑engineering, respects minimal diffs | Claude keeps rewriting too much code |
| frontend-design | High‑quality UI components (no generic “AI slop”) | You build user interfaces or design systems |
| agent-browser | Headless browser automation (E2E tests, scraping) | You need UI validation or web data extraction |
| skill-creator | Official meta‑skill to create your own skills | You have a team‑specific workflow to codify |
Smart stacking: from solo dev to enterprise
Not every project needs all skills. Use these battle‑proven stacks to avoid bloat:
- Minimal stack (scripts, single‑file edits):
find-skills + caveman - Standard stack (full development loop): Minimal +
Superpowers + claude-mem - Full‑stack stack (complex web apps): Standard +
frontend-design + agent-browser
The golden rule: inspect any skill’s SKILL.md before installing. Prefer skills that are single‑purpose,
clearly described, and lightweight.
1️⃣ Install
find-skills first — it’s your navigation system.2️⃣ Install
Superpowers second — it enforces engineering discipline.3️⃣ Use the official marketplaces: claude.com/marketplace and skillsmp.com.
4️⃣ Create a custom skill when you repeat the same manual steps three times.
5️⃣ Avoid “star chasing” — a skill with 10 stars but a tight
SKILL.md beats a vague 1000‑star skill.
What about making your own skill?
The skill-creator skill (official from Anthropic) turns your internal playbooks into reusable AI workflows.
Create a folder under .claude/skills/your-skill-name/, write a SKILL.md with YAML frontmatter and markdown instructions,
then reload. Within minutes, Claude Code will follow your team’s exact linting, review checklist, or deployment ritual.
References & further reading
- Official Claude Code Skill Marketplace
- Community‑driven skillsmp.com
- Claude Code Best Practices (Vibecoding.channel)
- Context Engineering for AI Agents – fix quality issues
- Agentic Engineering Patterns – from prototype to production
before running in production environments.
Leave a Reply