AI Agent 技能管理：团队级 Skills 分发与复用指南

The people that understand how to use skills, how to use plugins with codecs and claude code just have this unfair advantage. But there's so many questions around it, like how do I use it with my team or how do I post it on GitHub or what are the skills I need to know? So on today's episode, we break it down super clearly. I brought my friend Remy and he clearly explains how to use skills, how to use plugins, and how he runs his entire company with a bunch of skills that gets him the best output out of Claude Code.

What's really cool is Remy actually drops a bunch of the prompts in order to actually go and do this yourself. and he basically just explains exactly what you need to do in order to to implement all these skill chains. Basically, multiple skills together to actually help you live a more productive and hopefully revenue generating life. Enjoy the episode. Today's episode is brought to you by Brex. My company's been on Brex for a year and a half, and I started because I kept hearing companies like Verscell, OpenAI, Anthropic were using Brex, and I figured if they're using it, why shouldn't I?

It's been a gamecher. The thing that got me is how smooth it is. It's got high limit cards. It's got banking. It's got AI that handles the back office busy work like expense reports, which I don't want to do on its own. It's really just built for this agentic world. If you're building something new, it's time to get B. Check it out at brex.com/solutions/artups. Link in the description. [music]

[music]

I begged him to come back on AI with Remy as he's known, right?

Yes. AI with Remy

is here. Welcome back, Remy. By the end of the episode, what are people going to learn?

You're going to learn how to effectively manage and distribute skills, agent skills across your entire team.

Okay. And like why why should people care about that? Because I think that agent skills are probably like the single most important concept and like agent skills are what really actually save you time with AI when you're trying to automate out repeatable processes and I don't feel like anyone's really cracked it cracked the way to properly administer and share them across their team. So if anyone is interested in agents to do tasks and anyone's interested in doing it with teams, this is the episode for them.

It is. It sure is. All right, let's dive in.

Bang bang. So, before we get into it, I'm just going to do a quick overview on what a skill is for those people who are listening who don't know. If you do, which I'm imagining a lot of people listening do, I'm sure Greg you'll do a good job of putting timestamps down below. You guys can just skip ahead. But skills are literally just SOPs for AI. So, without a skill, the old way is if you wanted a proposal written, you would have to jump into a new session or a new chat, ask Claude to write your proposal.

You would probably get a result you're not happy with off the get- go and you have to go through and reexlain all your preferences, the colors, the logo, like, hey, put the price at the bottom instead of at the top, so on and so forth. And eventually you land on a proposal that you're happy with. But what happens next week when you go to create another proposal? It forgets everything unless you keep going in the same session, which you know runs into other issues when you just keep going in the same uh session for too long.

But it's forgotten all your preferences. Whereas with a skill, it basically just allows you to package up uh your entire kind of way of doing things into a document, a markdown file for Claude to read. It's literally just an SOP, like a step-by-step guide on how to do a process. I literally just ran before this uh you know, before I jumped on, I ran this little demo here. I said, "Create a proposal for Greg Eisenberg, you know, for the startup ideas to sponsor the newsletter." and it just oneshot it.

It whipped out the, you know, the proposal generation skill that I've built and then it generated this lovely branded proposal here exactly how I wanted it. I didn't even have to reexlain a single thing.

And most importantly, that that wasn't slop. You know, I think the mistake, you know, a lot of people use AI and they get slop and a big reason is they don't have tight skills.

Exactly. Exactly. like the I have a really specific way I like things done and once I nail it, I'll just build a really good skill for it and then I can just like nail it one shot every single time. And the way that I kind of think about how the agent uses skills is it's like I visualize the agent as like the most capable employee you've ever hired and he's sitting in his desk and he's got his computer which all your tools like MCPs connected up.

He's got his instructions file that he reads before every task and then another, you know, additional context if he needs it. And he's got this big, you know, bookshelf of SOPs, which is skills. And, you know, in his skill, when you open it up, it has a little name and description at the top. And that's kind of just what sits on the spine of all the books. And then when he actually, you know, decides he needs it for a task, he'll pull it off the shelf and then read like the full thing that'll teach him exactly how to do the task.

So, you know, that's what a skill is. They are super super valuable. A good skill can save you like literally 2 hours a week and you stack those up and you know it's game over. But the issue like one of the issues we're facing right now is that AI is very much single player. So you know all your team members have their own claude setups on their computer or codec setups and if they build something brilliant or build a great skill you know it just lives on their machine.

It's very very difficult to share it properly. And this is like a similar problem that we saw back when personal computers first came out and people were using, you know, tools like Microsoft Word. You'd build a doc, you'd have a document you're working on and it was just like on your computer and, you know, when you wanted to actually send it over, you would have to just, you know, like mail it, export it, and then mail it.

And you'd have a bunch of different copies floating around and no actual uh central source of truth. And then Google Docs thankfully solved that. you just have like one doc that lives in Google Drive and everyone can kind of be in there collaborating and it's just like one central source of truth. We're kind of in our Microsoft Word era of skills at the moment. Everyone's just creating skills. They're super valuable, but they just live on everyone's machines and then sharing them around and actually managing them across a team is really really difficult.

So yeah, we're here right now in this uh Microsoft Word era of skills. So like I'm saying, you've built a great skill. Now what like what do you do? How do you share it with your team? Some quick examples of some that I've literally built just this week that have been like game changers that I've wanted my team to have is a notion formatting skill. So, if I open up like this was a little doc where I was prepping before the pod and I like all my notion docs formatted a certain way.

I I like lots of white space so it's super readable. Lots of divider lines, little blue highlights for elements. And you know, if you just let Claude like go and build you a notion doc, it's a mess. Like all the text is crammed together. It's not readable at all. So, I have a specific way that I've taught Claude how I want all of my notion docs to be formatted. And I've just packaged up that up as a skill. So, every time I ask Claude to build something in Notion, it pulls his like notion formatting skill off the shelf, his SOP, and reads it so he knows what to do.

So, that's one that I want all my team to be using so that whenever they're building stuff in notion, it all looks the same and looks nice. Another one is my b