I Stopped Installing Claude Skills. Here's What I Do Instead.

YouTube/Substack · YouTube · Read

• Core argument: installing a community AI skill imports “somebody else’s set of decisions about the job — which tools to use, which shortcuts were fine, what counted as a good result” without review; a recommended design skill kept producing the same narrow aesthetic (terracotta, maroon, rounded rectangles) regardless of what the user actually wanted.
• Technical constraint cited: both Codex and Claude Code cap how many skills a model can draw on at once — beyond roughly 25 skills, “your agent is averaging out their conflicts and handing you duller work than it did at five.”
• Introduces the “one-job test” framework: run one real job through a new skill and score the result against your own standards, yielding one of three verdicts — keep it, fork it (rebuild around your own judgment), or delete it.
• Distinguishes skill types: narrow, mechanical tasks from trusted sources “travel well” as-is; skills carrying taste or business rules need validation before being trusted.
• Practical takeaway: adding more skills to fix bad output is a feedback loop that tends to make things worse, not better — audit before you accumulate.