Claude Code Skills After Three Weeks: 5 Rules That Actually Make Them Work
The gap between a useless Claude Code Skill and a precise one is entirely in the configuration the developer writes around it. A five-minute custom SKILL.md that names the project's actual stack and conventions produces more actionable output than any marketplace Skill used out of the box.
Most developers install Claude Code Skills and get back generic, unhelpful output. The problem is not the Skill but the lack of project context. A SKILL.md that specifies what to check, what conventions the project follows, and what to ignore turns a 20% useful suggestion rate into 80%.
Three well-tuned Skills outperform 20 installed ones because every Skill consumes limited context-window space. A 10-line custom Skill that names the exact tech stack — Zustand, React Query, Tailwind — beats a 500-line generic one that has to guess. The real efficiency unlock comes from chaining Skills into a workflow where each step's output feeds the next, building a continuous context chain instead of cold-starting every call.
CLAUDE.md sets global project rules, Skills define scenario-specific behavior, and .mcp.json connects external tools. Leaving out CLAUDE.md is like handing out a job manual without stating company policy; the Skill has no idea what stack or standards the project uses. Configure all three and Skills at least double in effectiveness.
The most counter-intuitive finding is that a developer's own 10-line Skill beats a community Skill with hundreds of lines, because precision comes from eliminating guesswork about the stack, not from covering more generic scenarios.
Skill effectiveness is bottlenecked by context-window economics: more Skills means less attention per Skill, so curation is a hard requirement, not a preference.
The CLAUDE.md + Skills + MCP layering maps cleanly onto how real teams already separate policy, procedure, and tool access; missing any layer breaks the model.