Curate a Personal Skill Fleet Instead of Bulk-Installing

# Curate a Personal Skill Fleet Instead of Bulk-Installing ## Claim When adopting third-party agent skills, maintain a small, personally-reviewed set in a single synced repository rather than installing an entire library wholesale — the value of a large public skills repo is as a menu to select from, not a package to inherit in full.  ## Evidence [[3. Resources/Literature Notes/Theo Tests Matt Pocock's Skills Repo and Potato's Pstack]] reports Theo's own practice: a personal, cross-machine repo he calls a "fleet," into which he selectively installs skills (e.g., wizard) after reading and testing them individually — demonstrated live when he installs wizard across all his machines, including a newly added Mac Mini, rather than pulling in either the ~200k-star Matt Pocock repo or Pstack in full. His closing advice generalizes this: read the markdown before installing, start with one low-risk skill (he names unslop specifically), and treat bulk import of either library as an anti-pattern. ## Scope & conditions - Holds for individual or small-team adoption of externally-sourced skills, where one person or a small group can plausibly read and vet each addition. - May need a formal review policy instead of ad hoc curation at larger organizational scale, where no single person can vet every skill entering a shared library. - Doesn't claim large public skill repos are low-value — only that consuming one in full, unread, is the anti-pattern; the repo's value is as a curated-from menu. ## Links - [[3. Resources/Permanent Notes/A Skill Can Be Evaluated by Pasting Its Text Into a Session]] — because extends: copy-paste testing is the specific low-cost mechanism that makes this kind of selective curation practical at the individual-skill level, before committing a skill to the fleet. - [[3. Resources/MOCs/Personal Knowledge Management MOC]] — because applies-in: Courtney's own routing/curation discipline for tools, subagents, and models (per the `credit-routing` skill) is the same underlying practice of maintaining a small, reviewed, personally-trusted set rather than accumulating everything available. - [[3. Resources/MOCs/AI & the Future of Knowledge Work MOC]] — because applies-in: general AI-agent-tooling adoption pattern, not WordPress-specific. ## Maintenance - Last tended: 2026-08-19 - Next review: 2026-11-19