How I Use Skills + AI Agents to Run My Life — Transcript

Full transcript

1. 0:00The people that understand how to use
2. 0:02skills, how to use plugins with code X
3. 0:04and cloud code just have this unfair
4. 0:06advantage. But there's so many questions
5. 0:08around it like, how do I use it with my
6. 0:10team? Or how do I post it on GitHub? Or
7. 0:13what are the skills I need to know? So,
8. 0:16on today's episode we break it down
9. 0:18super clearly. I brought my friend Remi
10. 0:20and he clearly explains how to use
11. 0:22skills, how to use plugins, and how he
12. 0:26runs his entire company with a bunch of
13. 0:28skills that gets him the best output out
14. 0:31of cloud code. What's really cool is
15. 0:34Remi actually drops a bunch of the
16. 0:36prompts in order to actually go and do
17. 0:38this yourself. And he basically just
18. 0:40explains exactly what you need to do in
19. 0:43order to to implement all these skill
20. 0:45chains, basically multiple skills
21. 0:47together to actually help you live a
22. 0:49more productive and hopefully revenue
23. 0:52generating life. Enjoy the episode.
24. 0:54Today's episode is brought to you by
25. 0:56Brex. My company's been on Brex for a
26. 0:58year and a half and I started because I
27. 1:00kept hearing companies like Vercel,
28. 1:02OpenAI, and Anthropic were using Brex
29. 1:04and I figured if they're using it, why
30. 1:06shouldn't I? It's been a game-changer.
31. 1:09The thing that got me is how smooth it
32. 1:11is. It's got high-limit cards. It's got
33. 1:13banking. It's got AI that handles the
34. 1:15back office busy work like expense
35. 1:17reports, which I don't want to do, on
36. 1:19its own. It's really just built for this
37. 1:21agentic world. If you're building
38. 1:23something new, it's time to get Brex.
39. 1:25Check it out at
40. 1:26brex.com/solutions/startups.
41. 1:29Link in the description.
42. 1:31>> [music]
43. 1:36[music]
44. 1:39>> I begged them to come back on AI with
45. 1:42Remi, as he's known, right?
46. 1:44>> Yes, AI with Remi.
47. 1:46>> Is here. Welcome back, Remi. By the end
48. 1:49of the episode, what are people going to
49. 1:50learn?
50. 1:51>> You're going to learn how to effectively
51. 1:54manage and distribute skills, agent
52. 1:56skills, across your entire team.
53. 1:58>> Okay, and like why why should people
54. 2:00care about that?
55. 2:01>> Cuz I think that agent skills are
56. 2:03probably like the single most important
57. 2:04concept and like agent skills are what
58. 2:07really actually save you time with AI
59. 2:09when you're trying to automate out
60. 2:10repeatable processes. And I don't feel
61. 2:12like anyone's really cracked it
62. 2:14cracked the way to properly administer
63. 2:17and share them across their team.
64. 2:19>> So, if anyone is interested in agents to
65. 2:22do tasks, and anyone's interested in
66. 2:25doing it with teams,
67. 2:27this is the episode for them.
68. 2:29>> It is. It sure is.
69. 2:30>> All right, let's dive in.
70. 2:32>> Bang bang.
71. 2:34So, before we get into it, I'm just
72. 2:35going to do a quick overview of what a
73. 2:36skill is for those people who are
74. 2:37listening who don't know. If you do,
75. 2:38which I'm imagining a lot of people
76. 2:40listening do, I'm sure Greg you'll do a
77. 2:41good job of putting timestamps down
78. 2:43below. You guys can just skip ahead.
79. 2:45But, skills are literally just SOPs for
80. 2:47AI.
81. 2:48So, without a skill, the old way is if
82. 2:50you wanted a proposal written, you would
83. 2:52have to jump into a new session or new
84. 2:54chat, ask Claude to write your proposal.
85. 2:57You would probably get a result you're
86. 2:58not happy with off the get-go. And you'd
87. 3:00have to go through and re-explain all
88. 3:02your preferences, the colors, the logo,
89. 3:04like hey, put the price at the bottom
90. 3:06instead of at the top, so on and so
91. 3:08forth.
92. 3:09And eventually, you land on a proposal
93. 3:11that you're happy with.
94. 3:12But, what happens next week when you go
95. 3:14to create another proposal?
96. 3:16It forgets everything unless you keep
97. 3:18going in the same session, which you
98. 3:19know, runs into other issues when you
99. 3:21just keep going in the same uh session
100. 3:23for too long. But, it's forgotten all
101. 3:25your preferences.
102. 3:27Whereas with a skill, it basically just
103. 3:28allows you to package up uh your entire
104. 3:31kind of way of doing things into a
105. 3:33document, a markdown file, for Claude to
106. 3:35read. It's literally just an SOP, like a
107. 3:37step-by-step guide on how to do a
108. 3:39process.
109. 3:40I literally just ran before this, uh
110. 3:42you know, before I jumped on, I ran this
111. 3:44little demo here.
112. 3:46I said, "Create a proposal for Greg
113. 3:47Eisenberg, um you know, for the startup
114. 3:49ideas to sponsor the newsletter."
115. 3:51And it just
116. 3:52it whipped out the
117. 3:54you know, the proposal generation skill
118. 3:56that I've built.
119. 3:57And then it generated this lovely
120. 3:59branded proposal here, exactly how I
121. 4:01wanted it. I didn't even have to
122. 4:03re-explain a single thing.
123. 4:05>> And most importantly, that that wasn't
124. 4:07slop. You know, I think the mistake, you
125. 4:09know, a lot of people use AI
126. 4:11and they get slop, and a big reason is
127. 4:14they don't have tight skills.
128. 4:17>> Exactly. Exactly. Like the I have a
129. 4:20really specific way I like things done,
130. 4:21and once I nail it, I'll just build a
131. 4:23really good skill for it, and then AI
132. 4:25can just like nail it one shot every
133. 4:26single time. And the way that I kind of
134. 4:28think about how the agent uses skills is
135. 4:30it's like I visualize the agent as like
136. 4:32the most capable employee you've ever
137. 4:34hired, and he's sitting at his desk, and
138. 4:36he's got his computer, which all your
139. 4:37tools like MCPs connected up. He's got
140. 4:40his instructions file that he reads
141. 4:41before every task, and then another, you
142. 4:43know, additional context if he needs it.
143. 4:45And he's got this big, you know,
144. 4:47bookshelf of SOPs, which are skills.
145. 4:49And, you know, in a skill, when you open
146. 4:51it up, it has a little name and
147. 4:52description at the top, and that's kind
148. 4:54of just what sits on the spine of all
149. 4:55the books. And then when he actually,
150. 4:57you know, decides he needs it for a
151. 4:59task, he'll pull it off the shelf and
152. 5:00then read like the full thing that'll
153. 5:02teach him exactly how to do the task.
154. 5:04So, you know, that's what a skill is.
155. 5:06They are super, super valuable. A good
156. 5:07skill can save you like literally 2
157. 5:09hours a week, and you stack those up,
158. 5:11and, you know, it's game over.
159. 5:13But the issue, like one of the issues
160. 5:14we're facing right now, is that AI is
161. 5:16very much single player. So, you know,
162. 5:18all your team members have their own
163. 5:20Claude setups on their computer or Codex
164. 5:22setups.
165. 5:23And if they build something brilliant or
166. 5:25build a great skill,
167. 5:27you know, it just lives on their
168. 5:28machine. It's very, very difficult to
169. 5:30share it properly.
170. 5:32And this is like a similar problem that
171. 5:34we saw back when personal computers
172. 5:36first came out and people were using,
173. 5:38you know, tools like Microsoft Word.
174. 5:40You'd build a doc, you'd have a document
175. 5:43you're working on, and it was just like
176. 5:44on your computer. And, you know, when
177. 5:46you wanted to actually send it over, you
178. 5:48would have to just, you know, like mail
179. 5:49it, export it and then mail it. And you
180. 5:51have a bunch of different copies
181. 5:52floating around and no actual
182. 5:54central source of truth.
183. 5:56And then Google Docs thankfully solved
184. 5:58that. You just have like one doc that
185. 5:59lives in Google Drive and everyone can
186. 6:01kind of be in there collaborating and
187. 6:02it's just like one central source of
188. 6:03truth.
189. 6:05We're kind of in our Microsoft Word era
190. 6:07of skills at the moment. Everyone's just
191. 6:08creating skills. They're super valuable,
192. 6:10but they just live on everyone's
193. 6:12machines and then sharing them around
194. 6:14and actually managing them across a team
195. 6:16is really, really difficult. So yeah,
196. 6:17we're here right now in this Microsoft
197. 6:20Word era of skills. So like I'm saying,
198. 6:22you've built a great skill.
199. 6:25Now what? Like what do you do? How do
200. 6:27you share it with your team? Some quick
201. 6:28examples of some that I've literally
202. 6:30built just this week that have been like
203. 6:31game-changers that I wanted my team to
204. 6:33have
205. 6:34is a Notion formatting skill.
206. 6:36So if I open up like this was a little
207. 6:38doc where I was prepping before the pod
208. 6:40and I
209. 6:41like all my Notion docs formatted a
210. 6:43certain way. I I like lots of white
211. 6:45space, so it's super readable, lots of
212. 6:47divider lines,
213. 6:48little blue highlights for elements.
214. 6:50And you know, if you just like Claude
215. 6:51like go and build your Notion doc, it's
216. 6:53a mess. Like all the text is crammed
217. 6:54together. It's not readable at all. So I
218. 6:56have a specific way that I've taught
219. 6:58Claude how I want all of my Notion docs
220. 7:01to be formatted. And I've just packaged
221. 7:03up that up as a skill. So every time I
222. 7:04ask Claude to build something in Notion,
223. 7:06it pulls his like Notion formatting
224. 7:08skill off the shelf, his SOP, and reads
225. 7:10it, so he knows what to do.
226. 7:12So that's one that I want all my team to
227. 7:13be using so that whenever they're
228. 7:14building stuff in Notion, it all looks
229. 7:16the same and looks nice. Another one is
230. 7:18my brand voice. So AI with Remi brand
231. 7:20voice for all like the, you know, email
232. 7:22assets and landing page copy, etc.
233. 7:25So I built out a skill for that. Another
234. 7:27one's email formatting. So I use Resend
235. 7:30as one of my ESPs and I have like a, you
236. 7:33know, nice kind of email format that I
237. 7:34like to use with highlights, similar to
238. 7:37Notion doc, like lots of white space,
239. 7:39and like the blue buttons and then the
240. 7:41little signature at the bottom. As well
241. 7:43as the logo up at top here, too.
242. 7:46So, I basically told Claude exactly how
243. 7:48I liked emails formatted once, saved it
244. 7:50as a skill, and now I want all my team
245. 7:53to have that exact same skill for when
246. 7:55they're, you know, building notification
247. 7:57emails to go out or marketing emails,
248. 7:59etc.
249. 8:00So, there are some examples of skills I
250. 8:01built just this week that I would want
251. 8:03all my team to be able to have access to
252. 8:05and be using on like a daily basis. So,
253. 8:08how do you actually go about sharing the
254. 8:10skills? Well, originally, like one way
255. 8:12was you know, you would just save it as
256. 8:15a dot skill file or a zip file, and
257. 8:17you'd send it to them on Slack or email,
258. 8:18and they would just upload it into their
259. 8:20setups, and now they've got it. It kind
260. 8:22of worked, but then you run into this
261. 8:24nightmare of as soon as you make a
262. 8:26change, their file doesn't auto change.
263. 8:28It's a duplicate. And if they make a
264. 8:30change, you don't receive that as well.
265. 8:32And if you share that out to the team,
266. 8:33everyone's kind of improving on skills
267. 8:35as you should always be looking to
268. 8:36improve them, you end up with like 10
269. 8:38different copies and like no central
270. 8:40source of truth.
271. 8:41One of the other ways that I originally
272. 8:44used to share this across the team was
273. 8:45with like Drive or Dropbox or Obsidian,
274. 8:47as well.
275. 8:48So, you know, if you download like the
276. 8:50Google Drive desktop app or the Dropbox
277. 8:51desktop app, you can see them show up in
278. 8:54your file system, and you can like
279. 8:55basically open that folder up in Claude.
280. 8:58So, you could create like theoretically
281. 8:59create a skills folder, have them all
282. 9:01live in there.
283. 9:02Uh but, first issue is that Claude does
284. 9:04not read from a skills folder in Google
285. 9:06Drive. It has to read from its special
286. 9:08like dot Claude/skills folder. So, in
287. 9:11order to actually get Claude to even
288. 9:12read this, you need to like simlink it
289. 9:15in and make do like basically just do a
290. 9:17bunch of like hacky stuff to get it to
291. 9:19work.
292. 9:20And this
293. 9:22you can get away with this if you've got
294. 9:23a small team and you're all like
295. 9:24technically savvy enough to understand
296. 9:26like folder structures in Claude and
297. 9:28agents,
298. 9:29but the minute, you know, you bring on
299. 9:31like a junior or someone in marketing
300. 9:32who's not super tech savvy or AI native,
301. 9:35and you want them to be able to use a
302. 9:36skill and use your skills.
303. 9:38Like things just break all the time.
304. 9:40People don't really understand what
305. 9:41they've done. People don't understand
306. 9:42like how to set it up properly. And it's
307. 9:44just like not the most efficient way at
308. 9:45all. And if you wanted to use Obsidian,
309. 9:47same deal applies as Google Drive and
310. 9:49Dropbox, except now everyone has to set
311. 9:51up and install Obsidian, too, which is a
312. 9:53pain in the ass.
313. 9:55So,
314. 9:57drum roll, please. How do we share
315. 9:59skills across the team?
316. 10:01The best way that I've found
317. 10:04is by putting them all in a GitHub
318. 10:06repository
319. 10:07and making it a plugin. It sounds
320. 10:09simple, but it it it's so so effective.
321. 10:12So, essentially, like all all it is,
322. 10:13most of the viewers already understand
323. 10:15this, but GitHub is just like you can
324. 10:16give it as a Google Drive for code. So,
325. 10:18it's like just like you share files and
326. 10:20videos and images across your team with
327. 10:22Google Drive,
328. 10:23GitHub is just that, but for sharing
329. 10:24code. So, the simplest way to do this is
330. 10:27to just push all your skills into a
331. 10:29repository.
332. 10:30So, I have this one here called team
333. 10:31skills, where I've got them all kind of
334. 10:33separated by department, and then you
335. 10:35can see the skills live in here. So, for
336. 10:37the brand section, I've got these two
337. 10:39skills in there.
338. 10:40And you know, the rest of the other
339. 10:42departments have their various skills in
340. 10:44there, too.
341. 10:46And this, you know, straight away, now
342. 10:48you've got your central source of truth,
343. 10:49your one place where all of your skills
344. 10:51live.
345. 10:52But then the plugin part is how you make
346. 10:54it like easy for Claude to access it.
347. 10:56>> And Remy, a lot of people hear repo and
348. 11:00plugin, making it code, and if you're
349. 11:03non-technical,
350. 11:04you kind of get scared, but it's like if
351. 11:07you're non-technical, it's not it's not
352. 11:09hard to do.
353. 11:10>> It's not hard at all. I've actually I'm
354. 11:12glad you said that, Greg, cuz I've
355. 11:14prepared a prompt that we can give to
356. 11:17the viewer after the episode,
357. 11:19and that will basically turn their
358. 11:20existing skill folders into this exact
359. 11:23repo and plugin setup for them. But to
360. 11:25be honest, like it's pretty simple. I
361. 11:27don't have a development background at
362. 11:28all.
363. 11:29Um as long as you can understand that
364. 11:30GitHub is just a place to store your
365. 11:32files on the cloud, and then a plug-in
366. 11:34is just a way for Cloud to access them.
367. 11:36That's pretty much all you need to know.
368. 11:38>> [snorts]
369. 11:38>> All right, cool. So, quick one about
370. 11:41what a plug-in is. So, a plug-in is
371. 11:43literally just a bundle of skills, MCPs,
372. 11:46and hooks. You don't even have to bundle
373. 11:48in MCPs and hooks. You can just have a
374. 11:50plug-in with skills or just one with
375. 11:51MCPs or any combination of them. But,
376. 11:54our specific one is a bundle of skills
377. 11:56in the plug-in.
378. 11:58And it's super super easy to install it.
379. 12:00I'm going to just open up the
380. 12:03terminal for a moment.
381. 12:05So, if we open up trusty Cloud Code
382. 12:07here,
383. 12:09if we type {slash} plug-in here,
384. 12:12it will bring up, you know, this simple
385. 12:14little menu here where we can manage and
386. 12:15install our plug-ins.
387. 12:17So, if we head over to marketplaces,
388. 12:19this is where you add in your repo as a
389. 12:23marketplace. So, it's literally as
390. 12:25simple as just going add marketplace
391. 12:27and then copying the link
392. 12:31for your repository. Let me just go back
393. 12:33to like the the main one.
394. 12:35And then pasting this straight in here.
395. 12:38And then I've already got it because it
396. 12:40uh exists
397. 12:42in my in my system already. Like, I've
398. 12:43already got this repo installed as a
399. 12:45plug-in, but it's literally just as
400. 12:46simple as entering your GitHub repo URL
401. 12:49as a marketplace. And then, if we go
402. 12:51back out, you can see that my team
403. 12:53skills
404. 12:55now show up here. And then, the
405. 12:57marketplaces kind of like the app store
406. 12:59you're installing, and then the plug-ins
407. 13:01in themselves are kind of like the apps.
408. 13:03So, I've broken down all of my skills by
409. 13:06department, and then they kind of have
410. 13:08their own plug-ins here.
411. 13:09So, for example, like
412. 13:11one of my guys that helps with
413. 13:12copywriting, I probably wouldn't have
414. 13:14him install the finance skills plug-in.
415. 13:18So, you can kind of like get some
416. 13:19separation there by department, which is
417. 13:21super super cool. And if we click in, we
418. 13:23can see,
419. 13:25for example, if we go down to my sort of
420. 13:28bundle of newsletter skills,
421. 13:29we have, you know, weekly research, the
422. 13:32intake, the writing one, the stories,
423. 13:34the TLDR, etc., etc., etc. And um
424. 13:39it's super, super simple. Now you've got
425. 13:40it installed, one thing that's really,
426. 13:42really important to note is that you
427. 13:44need to have
428. 13:45uh everyone that installs it needs to
429. 13:48have auto update enabled. So I've got it
430. 13:50here, you can see now it's like giving
431. 13:51me the option to disable it cuz I've got
432. 13:53it enabled. But that's going to allow it
433. 13:55to, you know, you the skills to update
434. 13:58on your machine if someone else makes a
435. 13:59change to them.
436. 14:01But now with that installed,
437. 14:02if I head out of there and I type like
438. 14:05newsletter, for example, you can see
439. 14:07they belong to this newsletter plugin,
440. 14:09and then I can just use all the skills
441. 14:11exactly like you would in your regular,
442. 14:13you know, personal AI setup.
443. 14:15>> And this isn't unique to Claude Code.
444. 14:18Like if people are using Code X, Chat
445. 14:20GPT,
446. 14:21um they could they could use this, too,
447. 14:25right?
448. 14:25>> Same thing, exactly. Like I've tested
449. 14:28this with I use it in Code X and Claude.
450. 14:30I haven't really tested other harnesses
451. 14:32with it yet, but I imagine that they
452. 14:33would have a very, very similar
453. 14:35functionality. So, you know, I've got
454. 14:37that installed here in Code X as a
455. 14:39plugin, as well, with all of my like
456. 14:41team skills, and then you can click in
457. 14:42and and see them all here, too. And it
458. 14:45works
459. 14:46just the same in Code X. If I whip up a
460. 14:48new chat and we go newsletter, you can
461. 14:51see I have all the skills here to use,
462. 14:53as well. So yeah, you're 100% right. You
463. 14:54can use it across multiple harnesses, as
464. 14:57well, which is super, super cool.
465. 14:59What makes a plugin a plugin? It's so
466. 15:01you've got you literally your GitHub
467. 15:02repo where you've just dumped in all
468. 15:04your skills. And then there's just a
469. 15:06couple of little JSON files that Claude
470. 15:08read and Code X read that actually like
471. 15:10turn it into a plugin.
472. 15:12I don't have a clue at all how it works.
473. 15:14I don't need to. I just got Claude to
474. 15:16set it up for me. So, um you know, I
475. 15:18built this like lovely prompt here that
476. 15:20will get Claude to build that out for
477. 15:21you, which will get in your hands.
478. 15:24They'll be somewhere in the description,
479. 15:25right, Greg?
480. 15:26>> Mhm.
481. 15:27>> Wonderful.
482. 15:29And
483. 15:30now that this is set up, you essentially
484. 15:32just get everyone on your team to
485. 15:34install the plugin on their Claude's and
486. 15:36their Codexes. And then now you have
487. 15:38like skills in one central source of
488. 15:40truth that are distributed across your
489. 15:43entire team for them to use. And you
490. 15:45also have version control. So if, you
491. 15:47know, one of your team members makes a
492. 15:49change to the skill and like completely
493. 15:51ruins it, you can also go back and
494. 15:53revert to like older versions as well,
495. 15:55which I think is super super cool.
496. 15:57So now when I build something brilliant
497. 15:58like my Notion formatting skill and I
498. 16:01want my entire team to be using it, I
499. 16:03just add it into the the the
500. 16:05marketplace, the plugin, the Git repo,
501. 16:08and then it's distributed if as long as
502. 16:09I have auto update enabled, it's just
503. 16:11distributed onto everyone's Claude and
504. 16:14and Codex accounts, which is super super
505. 16:16neat.
506. 16:17>> Yeah, and the other
507. 16:18cool thing about it is there's a lot of
508. 16:21good skills that you can download. Like
509. 16:23I noticed you had Corey Haines's
510. 16:25marketing skill.
511. 16:26>> shout out Corey. They're they're
512. 16:27incredible.
513. 16:28>> Yeah, I know
514. 16:30um
515. 16:31you know, the Boring Marketer has his
516. 16:33Boring Marketing skills. Like there's
517. 16:35trusted creators and people who have
518. 16:38skills on the internet that you know,
519. 16:40you don't need to start from scratch.
520. 16:43>> Yeah.
521. 16:43>> So you can basically download some of
522. 16:45these skills, have that as your
523. 16:47foundation, start adding skills based
524. 16:49on, you know,
525. 16:53the type of business that you have and
526. 16:54what you want. And then all of a sudden
527. 16:56your team has access to that, too.
528. 16:58>> Exactly. And one thing that I do, too,
529. 16:59which is probably important to mention,
530. 17:01is I have a separate repo called Remy
531. 17:03skills. And these are just like my
532. 17:05personal ones. So these are just ones
533. 17:07that I
534. 17:08don't want my team to have for whatever
535. 17:09reason. Or maybe they're just ones like
536. 17:11you said I've downloaded off the
537. 17:12internet and I'm not ready to like roll
538. 17:13them out to the team. I'm just like
539. 17:15playing around with stuff. It's kind of
540. 17:16like my personal sandbox, if you will.
541. 17:19Um, and also like personal skills, for
542. 17:20example, like I've got an inbox triage
543. 17:22skill, which teaches Claude like how I
544. 17:24want my emails to be handled. I also
545. 17:26have a morning brief, which is very,
546. 17:27very specific to my apps and how I want
547. 17:29to operate. So, those ones it wouldn't
548. 17:31make sense to roll them out to the team.
549. 17:33Everyone kind of needs to build their
550. 17:34own versions of those. So, I just have
551. 17:36like this Remy skills repo as well,
552. 17:39which, you know, you can guess is also
553. 17:41set up as a plugin in itself.
554. 17:44If we go into the plugins again,
555. 17:47I have that installed here as a separate
556. 17:50plugin. And I just have that installed
557. 17:52on mine, my team doesn't. So, that's
558. 17:53kind of where I keep track of all my own
559. 17:55personal skills, as well.
560. 17:57>> But, like why even have that, you know,
561. 17:59like if you're not sharing it with
562. 18:01teammates, like why? Is it because, you
563. 18:03know, version control or like why why
564. 18:06why do it?
565. 18:08>> Uh, I just like having them in one
566. 18:10source of truth. I also like I'd rather
567. 18:13them be somewhere on the cloud. So, if
568. 18:15I'm running like a home easy agent on a
569. 18:16VPS or some sort of cloud agents, they
570. 18:19have a method to access my skills,
571. 18:21rather than them sit like all locally on
572. 18:22my file system.
573. 18:24And version control's cool. And um, I
574. 18:26guess those two are probably the main
575. 18:28reasons.
576. 18:29>> Cool. Yeah, I mean, it makes sense. Like
577. 18:31also, something on your local computer
578. 18:33can get compromised.
579. 18:35>> Yeah.
580. 18:36>> Like it's in the cloud now.
581. 18:40Um,
582. 18:40Greg, it's also
583. 18:44>> I
584. 18:44>> Oh, yeah.
585. 18:45>> I remember it was about 2 months ago,
586. 18:49Claude deleted my .Claude folder with
587. 18:52150 skills with like probably 500 plus
588. 18:55hours of work into it. And I had no
589. 18:57backups.
590. 18:59And um, that was pretty that sucked. So,
591. 19:02that's kind of also a defense against
592. 19:04that.
593. 19:04>> PTSD. So, you have a little bit of PTSD.
594. 19:07So, you're basically saying like, don't
595. 19:09be like Remy from 2 months ago, be like
596. 19:11Remy of today.
597. 19:12>> Yep, exactly. I It was probably like the
598. 19:14It was so stupid that I didn't have
599. 19:16backups, but I just like, I don't know.
600. 19:18>> No, I get it. It's It's sort of like
601. 19:21we're all moving at blazing speed right
602. 19:23now. We're all trying to figure out how
603. 19:25we can get the most from AI. And And And
604. 19:27we all want to build stuff because we
605. 19:29see a lot of opportunities. Sometimes,
606. 19:31what ends up happening is by going so
607. 19:34fast, you know, you're kind of you're
608. 19:36missing the mark on certain things.
609. 19:38Security is one big thing. Yeah. Backups
610. 19:41is another big thing. So, I'm happy
611. 19:42you're going through it.
612. 19:44>> Yeah. So, having that little personal
613. 19:46skills repo works nicely for me as well.
614. 19:49Once again, like, take this with a grain
615. 19:50of salt. You know, just If If you've got
616. 19:52a setup that you've already built that
617. 19:54works for you, hey, keep doing it. But,
618. 19:55this is just how I've been operating,
619. 19:58and I've found it to just be so so
620. 19:59effective that I really really want to
621. 20:00share it with you guys.
622. 20:02Uh one final thing to touch on is
623. 20:05you know, now you've got your team
624. 20:07skills repo, right? And also, too, one
625. 20:09thing to note is I
626. 20:11I don't know about you, Greg, but I
627. 20:11genuinely believe that like skills,
628. 20:13maybe not yet, but at some stage, I
629. 20:15think they're here to stay, and I think
630. 20:17that they're literally going to add like
631. 20:18enterprise value to companies cuz it's
632. 20:20just like the same way you have SOPs to
633. 20:22train employees to do tasks. It's like
634. 20:24if you build good skills to train agents
635. 20:25on how to do like real economically
636. 20:27valuable tasks in the business.
637. 20:29Um those are just like a super super
638. 20:32valuable.
639. 20:33And uh
640. 20:35so, this kind of gives you a nice
641. 20:37central place where you as the company
642. 20:39have ownership of the skills. This is
643. 20:41built out within my like GitHub
644. 20:42organization. So, that way, too, if like
645. 20:45I have employees that are working for
646. 20:46me, and they build some really really
647. 20:47cool skills that are super valuable, and
648. 20:50they're on their computers, if they
649. 20:51leave, I kind of can keep, you know,
650. 20:54ownership and control over those skills.
651. 20:56So, I think that's uh a really cool sort
652. 20:58of byproduct of this system as well.
653. 21:00And one other thing is I have built this
654. 21:03nice like UI to go over the top of my
655. 21:06skills. So,
656. 21:08I don't know, before you think like,
657. 21:09"Oh, here we go. Here's another Obsidian
658. 21:11graph." This one is uh this one's pretty
659. 21:13cool. So, I have all of these skills in
660. 21:16my GitHub repo. The same way you have
661. 21:18like a Superbase back-end for an app
662. 21:20that houses all the data, this that Team
663. 21:22Skills GitHub repo is the back-end for
664. 21:24this web app. So, every skill you see
665. 21:27here is pulling live from that Team
666. 21:30Skills repository. And I have a lot of
667. 21:32skills that call on other skills. For
668. 21:33example, like my YouTube publish
669. 21:35workflow.
670. 21:36I run that one skill, and it's like an
671. 21:38orchestrator skill that then runs the,
672. 21:40you know, the titles, thumbnails, and
673. 21:42descriptions in sequence. So, it will
674. 21:44show you like how these skills link
675. 21:46together and what they call on.
676. 21:48And I can click in here and view, you
677. 21:50know, the connections in and out from
678. 21:52different skills and and view the entire
679. 21:54like
680. 21:55uh skill file in here. And one thing,
681. 21:57too, is
682. 21:59I'm starting to to find that um as you
683. 22:02onboard like new team members who aren't
684. 22:04like super clued in with AI, uh this is
685. 22:06just like a really nice way for them to
686. 22:08be able to visualize all these AI SOPs
687. 22:11that you've built. And I've even added
688. 22:12this little ask button down below. So, I
689. 22:15mean, this is one I did before. I'm
690. 22:16like, "What are the best skills for
691. 22:17decision-making?" And it will just
692. 22:19search across your private database,
693. 22:21your company's skills library. And it's
694. 22:23told me here like, "All right, these are
695. 22:25the best skills to use for
696. 22:26decision-making." You've got the LLM
697. 22:27Council here. You've got Matt Pocock's
698. 22:30Grill Me skill. Um another one from
699. 22:32Corey Haines, too. But if we said in
700. 22:34here, it's like um
701. 22:37"I've done the weekly research for the
702. 22:40newsletter. Uh what skills should I run
703. 22:43next?"
704. 22:45And this will tell us
705. 22:48all of the newsletter skills that we
706. 22:49have available. And, you know,
707. 22:52"You've just run weekly AI research.
708. 22:54Next, run this skill. And then after
709. 22:56you've done that, run this."
710. 22:58So, I feel like this is just a a nice
711. 22:59little skills assistant to help with
712. 23:01like your team members that maybe aren't
713. 23:03as clued in with AI or even sometimes if
714. 23:05you build so many skills you lose track
715. 23:07of of what you've even got. This can be
716. 23:09handy, too.
717. 23:10So, um this I feel like is a really,
718. 23:12really nice addition on top of this
719. 23:14repository. And one other thing, too, I
720. 23:17just added this feature in today, so
721. 23:18it's brand new, but I added in this
722. 23:20usage bar. So, what it's done is in the
723. 23:23plugin, it's got a hook. So, every time
724. 23:25Claude uses a skill, it it triggers a
725. 23:27hook that, you know, tallies it.
726. 23:29And um
727. 23:31it basically tracks how many times
728. 23:32you're using skills. And also tracks by
729. 23:34team member what skills they're using
730. 23:36and how many times as well.
731. 23:37And my thought process behind this was
732. 23:40I don't know, maybe I could build like a
733. 23:41little Spotify wrapped at the end of the
734. 23:42year that's like, "You used your
735. 23:44proposal skill 56 times." But also on
736. 23:47top of that, I'm thinking
737. 23:49I want to see the skills that I never
738. 23:51use. Like after 6 months, like show me
739. 23:52all the skills that I haven't touched
740. 23:53once, and they can probably go. And you
741. 23:55can kind of like be able to keep track
742. 23:57and and cull down your stack so it
743. 23:59doesn't get too bloated. So, I feel like
744. 24:00that's a a super nice touch on top as
745. 24:02well.
746. 24:03>> Also, show me the skills that I'm not
747. 24:06using that should be using.
748. 24:08>> Yeah, yeah, yeah, yeah. Exactly, that
749. 24:09could be a little question for the
750. 24:11skills assistant.
751. 24:12>> Yeah.
752. 24:14>> But um that is that is pretty much it.
753. 24:16Uh we've got the skills repo now built
754. 24:18out with like the one central source of
755. 24:20truth for the company skills.
756. 24:22Everyone adds it as a plugin into their
757. 24:24Claude. One little thing, too, is if
758. 24:25you're on a Claude enterprise account,
759. 24:27you can have like organization plugins.
760. 24:29So, you can build this out as like the
761. 24:30technical founder or get your CTO to
762. 24:32build it out and then have it baked into
763. 24:35everyone's Claude accounts or Codex
764. 24:36accounts so that your, you know,
765. 24:38lower-level non-technical employees just
766. 24:40have to, you know, they don't have to
767. 24:42even enter the terminal and and run a
768. 24:44slash command. So, that's a cool way to
769. 24:45to to do it, too.
770. 24:47>> How should people think about how many
771. 24:49skills they should be creating? So, on
772. 24:51here I see like you have different
773. 24:52departments, brand, content, newsletter,
774. 24:54marketing, general. Like is the way to
775. 24:56think about skills, just think about
776. 24:58what are the jobs that you're doing and
777. 25:01and how and
778. 25:03how are you using LLMs to complete them
779. 25:05and then create skills? Like what's the
780. 25:06general framework for thinking about how
781. 25:08to how to design skills and how many
782. 25:11skills you should be creating?
783. 25:13>> So, I generally if I have a task, like
784. 25:17I'm under the firm belief that you can
785. 25:18pretty much automate any process within
786. 25:20the company as long as it's not physical
787. 25:22like washing dishes. Uh you can pretty
788. 25:24much automate any online process with a
789. 25:26really good skill or series of skills
790. 25:28that are chained together.
791. 25:29So, in my mind just like any repeatable
792. 25:31task that I do on a day-to-day basis,
793. 25:33I'm like, let's get this down to a
794. 25:35skill. I don't want to touch this
795. 25:36anymore. And um I have some workflows
796. 25:39too where it's like a process like the
797. 25:41YouTube one that's broken down into
798. 25:44you know, three skills that are running
799. 25:45a sequence.
800. 25:47So, um the way I kind of think about
801. 25:48those skill chains as well is if I have
802. 25:51a larger process like taking an edited
803. 25:53video and getting it onto YouTube.
804. 25:55Uh
805. 25:56that could just be one skill in itself.
806. 25:58But the way I think about it is it is
807. 26:00if as part of a larger process I'm ever
808. 26:02going to want to run some of the sub
809. 26:04processes on their own,
810. 26:06I will just turn into a skill chain. So,
811. 26:08for the YouTube one, great example. It's
812. 26:09like there will be times when I just
813. 26:10want thumbnails or times when I just
814. 26:12want titles or just want descriptions.
815. 26:14So, for me that in my mind makes sense
816. 26:16to have that as a chain rather than one
817. 26:18skill.
818. 26:19But um the way I think about it is like
819. 26:20anytime I I I kind of sit in Claude or
820. 26:22sit in Codex to complete my work day. I
821. 26:25don't really open front ends of apps
822. 26:26anymore. I'll just tell Claude what I
823. 26:28want it to do and it will go into the
824. 26:29apps and do the tasks for me. And
825. 26:31anytime I'm I've done a task with Claude
826. 26:33and I know I'm going to need to do it
827. 26:34again, I'll just tell Claude like, hey,
828. 26:36turn this into a skill. And that's kind
829. 26:38of how I've ended up with so many.
830. 26:41>> I guess the other thing you can do
831. 26:43assuming the memory is good is to is to
832. 26:45tell Claude or Codex, be like, anytime I
833. 26:48have
834. 26:49uh I asking you to repeat something.
835. 26:53Um.
836. 26:54>> Yeah.
837. 26:55>> Make it into a skill. The other thing, I
838. 26:56guess the way to do that might be to put
839. 26:58it in an MD file.
840. 27:01>> Well, I've actually It's funny you say
841. 27:02that. Like one little thing I've
842. 27:04recently added, um,
843. 27:06I'm actually not sure if it's on every
844. 27:08skill cuz it is pretty new. Let's try
845. 27:10like Notion format if you have it. By
846. 27:11the way, I've also got this live review
847. 27:13where you can view all the skills, you
848. 27:14know, in this nicer space here. And, uh,
849. 27:17you can edit them as well. So,
850. 27:20let's find an example of like a skill I
851. 27:21probably created recently.
852. 27:24Um.
853. 27:26Proposal. Cool.
854. 27:28So, if we go into here, you should have
855. 27:30at the bottom this self-improvement
856. 27:31loop. So, I have this added into all the
857. 27:33bottom of my skill.md files. It
858. 27:35basically says like at the every at the
859. 27:37end of every run of this skill before
860. 27:39ending it,
861. 27:40you know, review. Did any step fail or
862. 27:42need a work around? Um, did the user
863. 27:44correct, reject, you know, anything
864. 27:46meaningful? And did you discover
865. 27:47something a future run might need? And
866. 27:49then, um, only propose the change if
867. 27:52like it's an adequate enough change. And
868. 27:54then at the end of every skill run I do,
869. 27:56it will usually give me like maybe one
870. 27:58or two things, like, um,
871. 28:00suggested improvements to the skill. And
872. 28:02I'll either just say like, "No, not
873. 28:03needed." Or like, "Yeah, great idea.
874. 28:05Like, run it." And then it will update
875. 28:07the skill. So, that's like a little
876. 28:08self-improvement loop that I've put into
877. 28:10the bottom uh, bottom of all my skills,
878. 28:11which has been like super handy.
879. 28:14>> Yeah, that's really smart. Cool.
880. 28:16>> Sweet.
881. 28:17>> Anything else people should know about
882. 28:19skills in general before we head out?
883. 28:23>> I think that's pretty much it. I I I
884. 28:24would just say like, um,
885. 28:26I don't think people uh, building enough
886. 28:29skills and enough good quality skills. I
887. 28:32think that
888. 28:32>> maxy.
889. 28:33>> Yeah. I I'm big like the same as like
890. 28:35Russ Max says it. I'm like, "Thin
891. 28:37agents, thick skills." So, like, you
892. 28:40know, I I, um, keep everything like
893. 28:42pretty lean in terms of like my agent
894. 28:44instruction files. And then make those
895. 28:47skills super fat and super detailed and
896. 28:50then the agents, you know, are kind of
897. 28:52um as long as they can just execute on
898. 28:54those skills, the skills have all the
899. 28:56context and the enough step-by-step
900. 28:59instructions that you can kind of just
901. 29:00open up any harness, run the skill and
902. 29:02it should be able to do the task how you
903. 29:03want it to.
904. 29:04>> Yeah, in a way you're kind of like
905. 29:06outsourcing some of the
906. 29:09uh
907. 29:10some of the strategy to the to the
908. 29:12skills and you're kind of saying like,
909. 29:14"Hey,
910. 29:15um for example, YouTube thumbnails,
911. 29:17like, "Hey, I know what good looks like
912. 29:19and I'm going to break it down or I know
913. 29:21what, you know, in the example you used
914. 29:23around Notion docs or or emails, like, I
915. 29:26know what good looks like to me, here it
916. 29:28is."
917. 29:29Um
918. 29:31and that way every time you don't need a
919. 29:34basically say say these instructions
920. 29:37over and over again and it's a win-win
921. 29:39for everyone cuz you end up getting
922. 29:41better output. Uh you do you end up not
923. 29:45having to repeat yourself.
924. 29:47Um the LM does what it's good at, which
925. 29:49is following orders and and they're able
926. 29:52to check again basically check that this
927. 29:55is what you asked for, so it's just a
928. 29:57win-win all around.
929. 29:58>> Exactly. I mean, even today like with
930. 30:00this system in place like um one of my
931. 30:03team members, Harold,
932. 30:05was like building a new email out in
933. 30:07Resend and it had some images that
934. 30:08needed to go into the email. So, he's
935. 30:10using like the
936. 30:11uh
937. 30:13email formatting skill that basically
938. 30:15like stages them in in Resend. And uh
939. 30:18the like he encountered this this error
940. 30:21with uploading the images and he found a
941. 30:22workaround that eventually got Claude to
942. 30:23work out how to do it properly. So, he
943. 30:26updated the skill and then now I
944. 30:27received that update, too. And now the
945. 30:29entire like the AI process has improved
946. 30:32and gotten better from one of the other
947. 30:34team members and now we all kind of
948. 30:36receive that improvement when we next
949. 30:38run the skill, which is super super
950. 30:39neat.
951. 30:40>> So, people go out there, make some
952. 30:42skills, put you know
953. 30:45go
954. 30:46>> build your company.
955. 30:47>> Build your company.
956. 30:49>> Get it as a plugin.
957. 30:50>> Yeah, create a repo. Uh
958. 30:52and and you'll be surprised, you know,
959. 30:56at the output you're going to get. I
960. 30:58think like I said in the beginning, a
961. 30:59lot of people try a lot of these AI
962. 31:02tools and they get frustrated because
963. 31:05uh the output isn't exactly what they
964. 31:07want.
965. 31:08>> Yeah.
966. 31:08>> And I agree with you around the
967. 31:12opportunity around multiplayer AI versus
968. 31:15single-player AI. You know, in software
969. 31:18in general, it always starts single
970. 31:19player because um like the example you
971. 31:22used, Microsoft Docs or Excel or
972. 31:25something like that. As software
973. 31:27builders, we have to
974. 31:28try to understand if people actually
975. 31:31want the product. So, Figma, for
976. 31:34example, wouldn't have you know, which
977. 31:36is a collaboration design tool, wouldn't
978. 31:39have worked. Like we needed we needed
979. 31:41Photoshop first before we did Figma.
980. 31:44>> Yeah.
981. 31:45>> It feels like we're entering multiplayer
982. 31:47AI land. Um you're and I appreciate you
983. 31:50kind of like clearly breaking down
984. 31:53uh what's happening, why it's happening,
985. 31:55how to take advantage of it, where it's
986. 31:57going.
987. 31:58Um I learned a lot, so thank you, Remy.
988. 32:01>> I appreciate it, Greg. Thank you so much
989. 32:02for having me on.
990. 32:03>> I'll include links for where to follow
991. 32:05AI with Remy in the show notes, in the
992. 32:07description.
993. 32:09Um check them out there and
994. 32:11>> As well as that prompt, we'll get that
995. 32:13prompt in your guys' hands so you can
996. 32:14basically just give that to Claude and
997. 32:16it will take your existing skill folders
998. 32:17and just build the plugin out for you uh
999. 32:19in GitHub that will work in Codex and
1000. 32:21Claude Code.
1001. 32:23>> There you go. There you have it. Thanks,
1002. 32:24Remy.
1003. 32:25>> Thank you, Greg.