AI Summary
5 min readRemy, host of AI with Remy, joined Greg to explain how companies can move beyond single-player AI setups and start managing agent skills across entire teams. The episode centers on a practical infrastructure problem: once you've built great skills (SOPs for AI), how do you share them, version them, and keep them from rotting on individual machines?
What a skill actually is
A skill is a markdown file that functions as a standard operating procedure for an AI agent. Without one, every time you ask Claude to write a proposal, format a Notion doc, or draft an email, you have to re-explain your preferences — colors, logo placement, spacing, tone. With a skill, you package all of that once. As Remy puts it, "The old way, you would jump into a new session, ask AI to write your proposal, get a result you're not happy with, and go through re-explain everything." A skill eliminates that loop.
Remy visualizes the agent as "the most capable employee you've ever hired." It sits at a desk with tools connected (MCPs), reads instructions before every task, and has a bookshelf of SOPs — the skills. When it needs one, it pulls the book off the shelf and reads the full thing. A good skill can save two hours a week. Stack several, and "it's game over."
The Microsoft Word era of skills
Continue reading the full summary in the app — free to try.
Read Full Summary →Free • No credit card required
Never miss an episode of The Startup Ideas Podcast
Get every new episode summarized in your inbox — free, ~5 minutes to read.
No spam. Unsubscribe anytime.
What you'll learn
- 1 (00:00) **Introduction: The Unfair Advantage of Skills** - Remy introduces the core problem: most people don't know how to effectively use skills, plugins, and team-wide AI workflows.
- 2 (02:33) **What Is a Skill? The SOP for AI** - A clear, simple definition of an "agent skill" for listeners unfamiliar with the concept.
- 3 (05:13) **The Big Problem: AI Is Still Single-Player** - Explains the current pain point: skills are valuable but stuck on individual machines.
- 4 (09:58) **The Solution: GitHub Repo as a Plugin** - The best method found for sharing skills across a team is putting them in a GitHub repository and making it a plugin.
- 5 (12:50) **Organizing Skills by Department & Auto-Updates** - How to structure the plugin for team use and keep everyone in sync.
- 6 (14:59) **Making a Plugin (No Coding Required)** - Reassures non-technical listeners that setting this up is easy.
- 7 (16:58) **Personal vs. Team Skills Repos** - Why you should maintain separate repos for personal and shared skills.
+ Full timestamped outline available in the app
Show Notes
Get Your Complete Financial OS at https://startup-ideas-pod.link/brex_SIP
I talk with Remy, known online as AI with Remy, about agent skills and how to share them across a whole team. Remy explains that a skill is an SOP for AI: a markdown file that teaches Claude your exact way to do a task. He then shows his system. He keeps his team skills in one GitHub repository, and he installs that repository as a plugin in Claude Code and Codex. The result is one source of truth, automatic updates for everyone, version control, and company ownership of the work. Listen to this episode if you run daily tasks with agents and you want your whole team to get the same quality of output.
Remy’s prompt + skill setup: https://startup-ideas-pod.link/Remy-skills
Timestamps
00:00 – Intro
02:33 – Skills as SOPs for AI
04:27 – How the agent uses skills
05:13 – AI is single player
06:21 – Example Skills: Notion, Brand Voice, Email
08:07 – How to share skills
11:40 – What is a Plugin?
14:58 – Anatomy of a Plugin
15:30 – Version Control and Rollback
16:58 – A Second Repo for Personal Skills
18:29 – The Day Claude Deleted 150 Skills
20:02 – Skills as Company Assets
21:00 – A Web App on Top of the Repo
24:46 – How Many Skills to Build
27:00 – The Self-Improvement Loop
28:15 – Skill Maxxing
30:40 – Closing Thoughts
Key Points
- A skill is a markdown SOP that teaches an agent your exact way to do a task.
- Most skills sit on one laptop, so a great process stays with one person.
- A GitHub repo plus a plugin gives the team one source of truth for every skill.
- Auto-update sends each skill edit to every teammate in Claude Code and Codex.
- A company-owned repo keeps the skills when a teammate moves on.
- Remy builds thin agents and thick skills, so any harness can run the same process.
LCA helps Fortune 500s and fast-growing startups build their future - from Warner Music to Fortnite to Dropbox. We turn 'what if' into reality with AI, apps, and next-gen products More from this podcast