You Need to Be Skillsmaxxing

Skills Are SOPs That Make AI Repeatable
- A skill is an SOP for AI: a markdown file that teaches an agent exactly how you want a repeatable task done.
- Remy explains skills stop re-explaining preferences each session and produce one-shot, consistent outputs like branded proposals. (Time 0:02:32)
We’re In A Single‑Player Era For AI Skills
- AI tooling today is largely single-player: good skills often live only on an individual’s machine.
- Remy compares the current era to early Microsoft Word times where files proliferated locally without a shared source of truth. (Time 0:05:12)
Turn Repeated Outputs Into Formatting Skills
- Do convert frequent outputs into skills (Notion formatting, brand voice, email templates) so every team member gets consistent, readable results.
- Remy built Notion and email formatting skills so Claude produces white-space‑heavy, branded docs and Resend emails automatically. (Time 0:06:08)
Host Team Skills In A GitHub Repo Plugin
- Do host team skills in a GitHub repo and expose it as a Claude/Codex plugin so everyone has a single source of truth.
- Remy keeps a TeamSkills repo separated by department and installs it as a marketplace plugin for automatic access. (Time 0:09:58)
Enable Auto Updates And Use Version Control
- Enable auto-update for the plugin so skill edits propagate automatically to everyone’s Claude/Codex and you keep version control.
- Remy highlights reverting broken edits and distributing improvements instantly when auto-update is on. (Time 0:13:40)
Keep A Personal Skills Repo For Sandbox Work
- Keep a separate personal skills repo for private or experimental skills you don’t want to push to the team.
- Remy uses RemySkills as a sandbox for inbox triage, morning brief, and other personal automations installed only on his account. (Time 0:16:58)
Claude Deleted 150 Skills And Cost Me Hundreds Of Hours
- Remy lost his local .claude folder that contained 150 skills and 500+ hours of work when Claude deleted it, which motivated central backups.
- He now keeps skills in GitHub to avoid single-point failure and local loss. (Time 0:18:30)
Skills Repo Can Be A Backend For A Skills Web App
- Treat a skills repo as a backend: build a web UI that visualizes skills, chains, and usage so nontechnical teammates can discover and run workflows.
- Remy’s app shows skill connections and recommends next steps for newsletter workflows. (Time 0:21:06)
Add A Self‑Improvement Loop To Every Skill
- Add a self-improvement loop at the end of each skill: have the agent propose edits after each run when steps fail or the user rejects output.
- Remy’s skill footer prompts the agent to suggest changes, then auto-update the skill after review. (Time 0:27:26)