Theo front-loads the video with the meta-lesson, because he expects viewers to reflexively install everything.

Rule 1 — Blind copying gets you nothing

  • "You do not get anything out of blindly copying other people's setups." Treat these repos as information to consider while building your own system, not as a set of steps to follow (3:14).
  • The analogy he uses: copy-pasting his codebase and tweaking it makes you a bad engineer; using it as a reference point to build your own makes you a good one. Blindly installing someone's exact setup is "like paying a bunch of money for a code template" (3:39).

Rule 2 — Audit the skills against your own usage

Theo's actual entry point was a prompt, not an install command (4:04):

  • Ask the agent to audit your usage across your machines (his: MacBook, "Leftbook", and BB1) (4:24).
  • Compare that history against the skills in the collection.
  • Ask for a ranked list of all skills by fit and by expected benefit, each with a brief "why".
  • Instruct it to pull history first, then fan out sub-agents to do the auditing (he ran it all on Opus 5 because he had usage to burn) (4:24).

The output was a document ranking every skill. The top hits for his work: interrogate, blast radius, technical writing, arena, prove it (4:45). He later repeated the exact same exercise pointed at Matt Pocock's repo (13:07).

flowchart LR
    A[Point agent at a skills repo] --> B[Audit your own history<br/>across machines]
    B --> C[Sub-agents rank each skill<br/>by fit + benefit]
    C --> D[Read the markdown yourself]
    D --> E[Copy-paste test the ones<br/>you're unsure about]
    E --> F[Install only the keepers<br/>into your own skills repo]

Rule 3 — Test a skill before installing it

  • The easiest way to evaluate a skill is not to install it and hope. Copy the markdown text, paste it into your agent, and ask for the behavior (14:08, 15:53).
  • He demonstrates this live: he pastes the grilling skill's text into an agent and gets the full behavior with nothing installed (16:19).
  • Caveat: this won't work for skills that ship scripts or other assets — but you can copy the script over, or just tell the model where to find and download it (16:19, 16:53).

Rule 4 — Manage your skills in one place

  • Theo keeps all of his skill files in a personal repo called fleet, and does his skill work in a thread inside it (21:50).
  • Rather than installing whole collections, his habit is to tell the agent to rip out the parts he wants and keep them in fleet (23:56).
  • The payoff is fleet-wide propagation: one instruction installed the wizard skill on all of his machines, including a newly added Mac Mini he mentioned in passing in the prompt (22:20, 27:52).