So What? Growing Prompts into AI Skills

Well, hey everyone, happy Thursday. Welcome to So What the Marketing Analytics and Insights Live Show. I'm Katie, joined by Chris and John. Hello, fellas. This week we are talking about growing prompts into AI skills.

So three-ish plus years ago, when generative AI hit the public market for the general consumer, everyone was struggling to try to figure out how to prompt correctly, prompt effectively, prompt efficiently. So that's where things like the Trust Insights Repel framework were born. So sort of the the transition was so you build a custom GPT or a gem or a project, depending on the system that you're in every time. And those have your prompts baked in so you don't have to copy and paste them over and over again. So now the next evolution of that is how do you take that custom thing and make it a skill that you can apply across anything that you're doing.

So you don't just have to work within that custom gem or that custom GPT or that project. And that's what Chris is going to walk us through today. And by us, I mean me and John, and then whoever's watching. So it let's start with a bit of table setting on skills. Skills is a specific term, skills with a capital S.

This is a data format that Anthropic, uh, the makers of Claude originally came up with for Claude its ecosystem. Uh it is the best way to think about it is kind of like a GPT or a gem that you can move anywhere. So one of the biggest criticisms is things like custom GPTs was okay, you have to use chat GPT with it, right? Or if you have a gem, you have to use Gemini with it. A skill is portable, it is effectively a prompt or a set of prompts that is bundled together, and then you can move it to any system that supports skills.

And then Anthropic made it a public good. They open sourced it and they said anyone can use the skills format. Uh and in fact, there is a whole website uh called agentskills.io that is anthropic's official. This is the definition of the skills format. So this is how you use it.

And there's um, they have this, they have like a 32-page slide deck that explains what goes into making a good skill and things like that. Skills are supported by Clawed Code, Claude co-work, Google Anti-Gravity, OpenAI Codex, Quencode, Open Co-work, uh, Claude Co-work, uh, and pretty much most agentic frameworks now because they're so dang useful. One of the things that I want to take a step back on is a skill is because it's essentially a GPT that you can move anywhere, it fits in kind of in an uh a specific place in the evolution of AI. So I want to talk about this briefly. This is something that a Trust Insights we've been working on for quite some time.

Um, originally derived from product market fit, it's now sort of evolved onto its own thing. And there's five levels. A lot of value there. Learn how to do prompting, right? Uh, we've talked about that for as Katie said, three years.

Second level, done with you. These are gems and GPTs. Effectively, what you're doing is you're building in a standard operating procedure into one of these things, so that you have your uh 90s uh cus uh song lyrics generator as an example of uh of a standard operating procedure at the agent level. Now you're doing project planning. So I think it was on the podcast we talked about this where we said, you know, the hottest programming language of 2026 is project management.

If you're good at project management, so that is project plans. That's what you get. You do get there. Today, you now have fully autonomous or mostly autonomous systems like OpenClaw. Uh, and the brand new as of yesterday, Claude Managed Agents uh that are built right into the cloud ecosystem.

So what do you suppose that uh input is for that? For level managed agents, yeah. Oh, um, I would assume all of your skills and plugins and your project plans. Yep. Well, and so, and as I'm saying it, I realize like these each build on each other.

So in phase one, you start with the prompts, in phase two, you have prompts plus, in phase three, you have plus and plus, and so you don't just do something brand new in each of these levels, you build on what you did in the previous level. So you still have to master level one, level two, level three. I would say I'm squarely in level three with like a little bit of dabbling in level four. You're gonna you're gonna uh call yourself wrong in just a moment, um, because you you already have the skills, Katie, um, to do levels four and five. Um I mean you may not know it, but you do.

And here's why. At level four, when you're building something like an open claw, you're providing a job description. A job description is a bundle of project plans plus skills, plus plugins, plus all that stuff. Yeah, you say, agent, you're you're my stockbroker, go off and do it, right? So it effectively, as that point, is like a full employee that you just go off.

Level five is an organizational division, so strategic charter where you would have a swarm of agents with a supervisor agent running them. And so someone like you, Katie, who has built multi-million dollar teams and manage teams of people, you have all the skills you need to be able to create a strategic charter for an organizational unit, like a division of a company instead of just a single employee. And you could send that division off and say, This is my marketing division. I've got an SEO agent, I've got a PPC agent, I've got an email agent, I've got a marketing manager agent. And you, as that strategic charter would provide all the job descriptions and all the skills and all the plugins and things like that.

And this, the agent swarm goes off and does those things and comes back to you once a month and says, Hey, Katie, the uh the uh virtual marketing department did all these things for you. Hmm. Having worked with humans, my guess is that you know, if they only check in once a month and I look at the report, I'm like, that's not what I asked you to do. Why didn't you do the things I wanted you to do? What the heck?

You spent all this money, like, no, but I mean, I can definitely see the potential in that. And so, with that extra description, that I would say, yeah, I'm I'm not squarely in number three, I'm squarely in number four at the moment, as of today, but I can certainly see your point about uh getting into number five. As I as a human, I'm not totally comfortable being hands off like that, but you know, that's a that's a me problem. So, with that understanding, then where do skills fall in? Skills fall in at level two.

Skills are essentially SOPs. Right. And you can take any any prompt or conversation or raw materials from level one and bring it up into a system and turn it into level two. And here's the thing there's so many tools that do this right now. If you use, for example, Claude Code, Claude Code has a plugin builder and a skill builder.

Uh Claude Cowork has a plugin builder and a skill builder. And the ones that come in the package are pretty good. They're not great. And so that's what I wanted to talk through today is how I built one for myself. Um that we actually put in the brand new uh Trust Insights prompt playbook, which is a monthly uh monthly subscription.

But the first lesson is literally the plugin. Um because the existing ones operate on a presumption that what you're putting in was good to begin with. That's not always the case. Well, the other thing too, so like these these are what the out-of-the-box skills that you can so the they're good to start with, but they're generic. So there's no customization, there's no tailoring towards what you as a human do or what your team does or what your organization does.

So I would, you know, and we've talked about this on previous live streams. So like John can use the legal plugin or the sales plugin, but he's gonna have to customize a lot of the instructions based on, you know, the kinds of terms that we look for in contracts or the things that need to be called out, you know, in an MSA, or you know, the way that we do our sales cycle, which there's a lot of standardization, but our clients don't look the same as other clients, so we need to sort of work with them and not force them into a certain process. So there, you know, for John, like the sales and the legal skills are good starts, but they're not going to get him all of the way into just doing it for me. There's still so much work. So, you know, for someone like him, it's probably easier just to build his own skill for the trust to insight sales process for the trust insights legal documentation review versus using what's out of the box.

That's probably true for most people. Exactly. Yeah. So how do we do this? The completely uh non-surprising answer is that if you want a good standard operating procedure, you should have some kind of framework that governs that procedure.

Um now we obviously go ahead. Go ahead. Can I can I guess go ahead. Well, no, so it is the 5P framework, and that is the basis of the prompt to skill plugin that we built, which uh which basically takes the existing prompt you have and puts it through the five Ps. And what you end up with when you run it is you end up with the skill that gets auto-installed into your your clawed environment, but you also get an understanding, and this is the part that is missing in most skill builders.

You do it it has an eval section that looks at whether or not the skill should fire or not. And this is the this is the big thing. Like if you've been using skills for a hot minute, you know that if you have similarly named skills, the triggering section, which is the YAML front matter of the skill, is what determines when the skill runs or not. And if it's badly written, uh your skill will fire at the most inopportune times and screw everything up. Um, so part of good skill building is that.

So the first thing you need to do is take your prompt and put it through the five Ps. The thing you want to turn into a skill. Why are we doing this? What are we doing? Uh you know, who's gonna do it?

Who's impacted by it? How do you do it? Do you need any supplementary tools, any things like MCPs or web searches and things? And then the critical part that is not in any of the other skill builders is the performance, the evals to say, does this skill work as intended? A well-structured SOP covers all of these pieces.

Um, so if you have well-structured SOPs, then you're already in good shape. If you don't, um, so I always, you know, tell the story. Uh the first time I walked into the agency to manage the team that Chris had hired me to manage. The first question I said was, all right, let's take a look at the SOPs. And they all look at me like I had eight heads.

And I was like, standard operating procedures, uh instructions for how you do things. Oh, yeah, no, we don't have that. And I was like, okay, that's number one thing we're gonna start. And you know, so uh, as Chris mentioned at the top, sort of with the strategic charter, like there's no real secret to building teams and growing teams. A lot of it is just good structure and SOPs, and those are the things that I'm really, really skilled at.

So therefore, having good SOPs is gonna help you move more quickly through these five levels. Exactly. So with that in mind, let me see if I can get the prompt to skill skill installed in my Claude co-work. Oh, that did not work. So I'm just going to use cloud code.

Let's walk through what happens in this thing because I think it's a useful exercise. So in our skill, let's go look at prompt to skill. Make this just a bit bigger so we can see it. Every skill at a minimum has to have a skill.md file and a folder that it's in it. And every skill that you build, um, and again, the skill builders will do this for you to a degree.

Um, will tell you, let's make this bigger so that we're not straining our eyes and give ourselves migraines. Um the description tells you when to fire. When should this this thing uh work? And so this one is convert any existing prompt workflow or set instructions to a proper structured clawed skill with the skill MD scripts, references, and assets. This is another part that again, I feel like some of the skill builders out there kind of miss.

It doesn't have to just be prompts. Inside of a skill, you can have things like Python scripts. Now, obviously, if you're going to be running Python scripts, be a hundred percent sure you trust the where the script came from, because there's obviously a lot of bad players out there. Um then you have the invocations and then trigger and ask to make a persistent thing attempts to do these things. What happens in this flow?

You get the extraction, you run the five Ps and say, what is this prompt trying to do? Um, why, you know, why would the user do this? Who's doing it? Who's impacted by it? Um, what is the step-by-step process?

Was what tools, data sources, MCPs and things does it need? And then the performance. How do you know that it works? It has to write down its analysis first, because we would never ever let any agent system do work in memory because the moment you quit that session, it's gone. So it always has to take notes.

Then determine the skill category, build the skill name, write the front matter, which has the triggering capabilities, build the skill body with the corrected structure, identify and include the bundled resources. This is now the fifth P of the five Ps. Generate test cases. So it has to, when you're doing a skill building, you have to test your skill. And if you build as part of a skill builder, you can run test cases and then and then look at the evals.

Inside the plugin, uh is the eval. So this is an example of does the tool know when to fire? And so there's five different scenarios that can test and say, should this skill fire? Someone says, What's the capital of France? The skill should not fire, right?

So that's a clear evaluate case of evaluating and saying, yeah, this skill, if the skill did fire, something's gone wrong in it. And so that's the process of we baked this thing for ourselves, and it's in the prompt playbook, um, so that you don't have to walk through and do this by yourself, but that is the overall process. You need a framework. You need to take the prompt, rebuild it through that framework. And the magic phrase is that I would use if you wanted to build this on your own is upstream and downstream.

No prompt exists in a vacuum. It has to be in the context of something else that you're doing. So a critical question to ask, and it's built into this the skill builder is what are the upstream and downstream things around this prompt? And these tools, particularly a model like Opus, smart enough to go, well, you know, John just gave me a uh Motown lyrics prompt uh to to do some to infer some song building. So upstream, uh, I need knowledge of what good Motown songs are.

And downstream, I'm gonna guess that John's probably gonna use this in a tool like Suno to generate uh a song, which means that in addition to the lyrics, I should probably create a a uh music composition prompt to go with it. So what you're describing is the basics of software development as well. Um, you know, and I think that that's something that you know, a lot of people stayed away from generative AX, like, oh, I'm not a developer, I can't code. So now, you know, we, the general we, we're calling these things, oh, you're not coding, it's a skill. You're building a plug-in, you're not coding, you're not developing software.

Guess what? You're developing software, you just don't know it. Um, and so, you know, we talk about the 5P framework as the good framework for structuring the information, but really the other framework that you need to be leaning on is the software development lifecycle. We didn't create it, we just use it. So the software development lifecycle, the SDLC, you know, you start with your requirements.

That's where the 5P framework comes in. Then you have design, develop, you know, test, deploy, and then do it all over again. Those are the basic um the basic stages of the software development cycle. What Chris was talking about in terms of performance and the unit testing and the extraction and making sure that it's working correctly and you have those triggers. That's that's you testing the software that you've built.

Um, if you are not testing things as you're building it, you're doing it wrong. There's no two ways about it. You have to be testing as you go. Do not leave it up to chance. Even if you're using systems like Claude Code or co-work or something, they can still hallucinate.

They can still bring in things you didn't mean them to bring in, they can still make mistakes. You can make mistakes when you're writing the skill. Make sure there is some kind of test, some sort of validation, call it whatever you want at the end of every skill to make sure it's doing what it's expected, especially as you know. So you might build a skill today, and then three months down the road, you're like, hey, I'm doing this project. Let me pull in this skill, and it's a mismatch.

But you might just because of what you've called it, you think it's working. But if there's no testing or validation built in, you could be basically taking all of your results and going sideways with it. So test everything. Be disciplined and strict about that. Yep, exactly.

So let's put this to work. Let's uh do this. One of the reasons, by the way, that I keep mentioning the prop playbook, in addition to being a narcissistic maniac, is that all of the prompts that are in it, you can drop into the plugin and generate the skill. So if you'd like a prompt for because it comes out every Tuesday and Friday. If you'd like a prompt from that week, like, oh, this means this was a skill, now just drop it in and say turn this into a skill.

Um, I'm gonna pick something that is uh not under NDA. Uh and I'm gonna pick me appreciate that. Yes. Our prompt are our old gem from our Google gem uh gems pile of generating um music uh stuff specifically for Suno, the music composition tool. So I've got a uh uh a gem in the set of instructions here.

I'm gonna copy and paste this, and right inside of Claude, we're gonna say, let's turn this Suno Music Generation prompt into a skill. Uh and then I'll put it, I'll just put in three hashes there. Whoops. And we'll put in our prompt from Gemini. So if you've got Chat GPT gems and the instructions laying around, if you've got Google gems and things like that, um, you can get this to do a really good job.

If you're in Claude Code uh or a similar style of system, anti-gravity codex, etc. Go with plan mode first, always for anything like this. Um, and if you're using Claude code, go to use the opus plan model, which does planning and opus and then does implementation and sonnet saves you a lot of money, which goes back to last week's uh live stream about how do we um how do we manage AI limits? So this is going to fire up the prompt skill skill because it correctly identified. I turned I said I want to turn this prompt into a skill, and now it's gonna look through and try and figure out how to do this.

When it's done, what it will do is it will say, I've tried I've essentially figured out this skill, and now I'm gonna build it for you and I'm gonna install it for you. Uh so you really have to do very, very little beyond that. But again, it sort of reinforces making sure that your plan up front is as thorough and detailed as possible because if it's building it and installing it for you, but it's wrong. Like, what if you accidentally program in, hey, so install this skill, and every time this skill runs, delete my hard drive. That I mean, I don't know about you, John, but that seems like a really bad day.

Yeah, that's a heavy load. You don't want to get caught wrong end of that. Yeah, which reminds me, by the way, um, it it couldn't find it because I didn't clearly denote that. So let's try that again. Um, let's give it the prompt up front.

Turn this prompt into a skill. And we're gonna use XML tags here because uh Claude in particular really needs things spelled out sometimes. I mean, I think we all do. I think it's helpful just to sort of you know operate that way. Um I appreciate more detail.

I don't know, I think John does as well. Yeah, it's just been funny because so many of the projects and things that we've been working on, you know, I the skills just show up in the interface. And I know that you know there's been work done, there's magic, but I didn't even realize that there's stock stuff too that you can go grab out there. Like we I've been working with custom tools that have been handcrafted, and I didn't realize there was generic junk out there for the rest of the world. It's like John, John.

When you say the magic, like so Chris and I are the magicians behind the scenes building the things, you're like, Hey, this is new. Look at that. And we're just like toiling away making the stuff. See, we'd have to use five rounds of errors and lost stuff. By the time it gets to you, it's been thoroughly tested.

Yeah, road tested. Yes. John just enjoys this golden land of uh perfected AI. Exactly. Beautiful countryside.

Whereas Chris and I are like, what does it happen? Ever. Um while that's running. I just want to take a brief pause to introduce a new little toy feature that StreamYard has allowed us. Uh StreamYard now allows polls.

Now they're a little janky, but you know, in case you guys, you know, who are all watching wanted to respond to the poll. Apparently, you can't interact with it on screen, but you can type into the chat what your response is to our very scientific uh poll. So just you know, while this is running, we thought it would be a good time to just run a quick poll just to see if anyone had any thoughts. Um, Chris, how are we doing on this? Uh good.

So it just um it just finished its plan. So it says convert the Suno V5 prompt guide into a skill. Uh it does the 5P analysis. What is the purpose? Um, who are the people involved?

Um apparently overwhelmingly, John is our favorite host. And you know, I can't be mad at that because everybody loves John. I don't know. Um we'll question the uh process later. I was gonna say I question the statistical validity of this.

All right. Let's move forward. Yes. Uh the platform performance, and then it builds here. We have the prompt architect skill, it correctly evaluates what the the file structure should be.

The references. So what are the formulas, the keyword dictionaries, uh necessary meta tags, anti-patterns and stuff like that, gathers up the musical intent, selects the formula based on a decision tree, builds the style prompt, builds the lyrics meta tag structure, does an anti-pattern check, and then it creates the thing. And so a planning process has gone through and figured out not only should I do I just want to turn this into a skill, but I think this part in particular is really important is figuring out what it is that we're trying to do and who's going to use it. So like AI music producers, content creators, hobbyists. When you're building skills, you have to infer those upstream and downstream uses.

Because if you if you do, then it becomes easier in the five piece to say this is the expected performance. And you know, what's interesting is that it's inferring the end users. Like we can give it some information, but I I appreciate that it's written out in such a way that it's like, oh, these are the people who are actually going to be using this thing. You know, because we've talked about in previous podcasts and live streams where you know we're not short on ideas and things that we want to build, but we don't always have a clear vision of who's going to use it, who's going to benefit from it. So I really like that addition.

Yep. It says here the references are separate because the source prompt is 4,000 word prompt. Um the skill budget is 500 lines. And so all these other details are going to get moved into a reference folder that it will then understand uh and know what it's supposed to be doing. So here it is is now going into create the actual skill itself.

So let's take a look where are you putting this? You are okay. You're writing you actually, it's writing it straight into my Claude folder. Great. So I'm going to have a Suno music generator very shortly.

Thanks, Claude. We do have a quick question. Someone's asking Do you have a resource on the ideal folder structure strategy? Yes.il website that I referenced earlier. That website contains the specs for agent skills and for how to lay out stuff in it.

It is cross-platform compatible. That is the canonical source that you should use. And you can either export that, give the tool of your choice a um uh the URL to point to, or uh on Anthropics website is the complete guide to building Claude skills. This is a 33-page PDF that contains all of the uh requisite information, including things like your file structure. It's is just defined in there.

This document is handy to have around. It's actually good for humans to read too to understand it, but that would be my recommendation. Um so now it's going through and building the keyword dictionaries, the meta tags, and these are all things that the skill will pull together as it's trying to create um stuff for Suno. So let's say, for example, you had a skill or you had a prompt like, I want to talk to my ideal customer profile. You could give that chat conversation, that prompt, or that YouTube video transcript for all that matters, along with your ICP, put it into a system like this, a plugin like this, and it'll reformat and break all the knowledge into pieces so that it's able to identify what to do, what not to do.

This part here, I did not see in any of the skill builders, which is anti-patterns. Anti-patterns is a one of those magic words that AI loves and knows what it means. And the rest of us are like, that's a weird word. An anti-pattern is the opposite of a design pattern. And so these are the critical mistakes that the system needs to be told, don't do this.

If uh, you know, it's example, you would define as people have, you know, using an M dash is an anti-pattern. I would I have a whole rant about that, but that's for another show. That's for a different show. Um, well, you know, so what's interesting. So, like if you're just going through step by step with something like a Claude Coworker, a Claude Code, and you're saying, I want to build my uh brand tone, you know, skill so I can reuse it, it will ask you in you know, simple terms, it'll be like, okay, and what should we not say?

What should we not use? What are phrases that you don't want to see? But that's it's building that database or or that you know, list of things that go into its anti pattern section. But it's asking you, so if you think about like if you've, you know, a lot of us have tried to build uh, you know, write in Katie style or writing Chris Penn style. We find ourselves going back, like, okay, don't say this every other sentence.

Don't use this phrase. I don't say these things, those are your anti pattern. That's just the phrases, but also think about it in terms of, you know, don't ever uh reference John Wall ever. He will not enjoy it, and he will, you know, go all, you know, sumo wrestler on you or something like that. Like, whatever it is that you just don't want it to do, make sure that you're thinking about those things as well.

We often think about what we want it to do. Uh, it's the same as sort of putting like in scope and out of scope. So, what's in scope, what's out of scope? What's out of scope is all of these extra stuff. So, like, make sure you're noting that as well.

Mm-hmm. Now, I'm gonna so in our analogs for marketer Slack community. One we were talking about this is today's question of the day. How are you gonna do this? I want to put something to our our friends in that community because if you've been following our advice, and a lot of people have for the last three years, you have or you should have a prompt library, right?

You have something in Joplin or SharePoint or whatever. I hope that it is apparent through the use of a plugin like this that you do not convert those prompts one at a time. That's a terrible idea. What you should do is put the prompts as text files in a folder on your computer and prompt it to say inside of a system like Claude Code, here's a folder full of prompts. Use the prompt to plot to skill skill, process every one of the files with its own agent and put it in the output folder.

Remember a few shows back, we talked about how do you get started with clawed code. Clawed code can directly interact with your hard drive, it can directly interact with a project folder. So you have an input folder of all of your prompts for the last three years. You have an output folder that you define, you have a skill to make skills, and you can say, just go do this. And as long as the the skill builder itself is solid, like we've seen ours that it took you know six and a half minutes to think through and and perfect this skill, you set that up.

You you set it up before you go to bed one night, uh, and then you come back the next morning, and all of your prompts that you love the most are now skills and they're ready to go, ready to be deployed. Uh, and you don't have to sit there and babysit it because you've used clawed code or a similar system, anti-gravity will do this, codex will do this, etc. To mass convert your data. Do not be that person doing it one at a time. Remember where we started this episode.

We started this episode here. If you are saying one at a time and convert this prompt, you're still doing level one stuff, even with a level three tool like clawed code, you are still behaving as though it's a level one tool. If you say, Here's your project plan, here are the skills which you built as a level two thing, SOPs are skills, then your project plan is convert all these prompts to skills, and you come back and the work is done. So you keep talking about Claude Code. Can you use Claude Co-Work and not use Claude Code to do the same thing?

Uh, you're shaking your head, yes, which is good news because I'm already doing that. Well, no, because though I have, and I think I talked about this on last week's live stream. I have a whole folder of folders on my desktop that are specifically for Claude. And I actually had Claude organize the folders and rename folders and create folders where they needed to be created because a lot of the work I do, it's not, I don't have client work on my desktop, it's all related to the business. So it can all be referenced, you know, if it wants to, but I have the skill builder, I have, you know, the different skills.

Like I can enact, you know, the hey, have the focus group duke it out and let me know what they say. Um, I actually used that set of skills last week when we were trying to come up with the name for something Chris and I were working on. And I was like, I don't know, I don't think that's a great name. But what does our, you know, panel of voice of customer or ICPs have to think about it? And they just duped it out and let me know what they thought, which is still sort of weird and mind-boggling to me.

Um, but you know, it's it works. But I bring it up because, you know, Chris, you're talking about Claude Code, but for those of us who aren't as comfortable in the coding environment, you can do the same nearly identical stuff in Cloud Co-Work. Yes. Now, the one thing you can't do in co-work that you can encode is easily run command line tools. And there are two tools that I think again, if you've been following us for a number of years now, uh, you know that uh we've been advising hey, you should be putting your prompt library on SharePoint or OneDrive or Google Keep or whatever, right?

Well, guess what? Google Keep has a command Google Workspace, all of Google Workspace has a command line tool that runs on your computer that can connect to all of Google Workspace, Google Calendar, Gmail, Google Docs, Google Sheets, Google Slides, etc. Now you may or may not want to use this because you're typing in a terminal like it's 1983, but critically, your AI can do this. So you one of the things that we could do, Katie, as as a Google shop. I could open up Claude Code, use the GWS command line tool and say, hey, Claude, reach into our Google Keep and pull out our company prompt library entirely and convert it all to skills.

And then and amazingly, boom, there it is. If you are a Microsoft shop and you are using OneDrive or SharePoint, there's a Microsoft CLI. You install that, and suddenly you can access anything in the three in your 365 environment that you're authorized to access. So you have that SharePoint prompt library. Guess what?

You set you install this, you tell Claude Code, hey, I installed this. Here's the manual. Go and find my prompt library, grab the whole thing out of SharePoint, convert it into skills, and we're ready to go. Having a good solid prompt library is what table stakes? You would want it.

That's your basic foundation. So, you know, we always say, like, if you don't have it, start there. Start there. It is still useful. So building all the skills in Claude co-work code, whatever is great.

Do not get rid of your prompt library. Do not suddenly decide that it doesn't need updating, that it doesn't need to be maintained, that you shouldn't still keep stuff there. Not to sort of sort of play the Debbie Downer, but these tools change. These tools go away. These tools suddenly implode, or you change your mind and no longer want to partner with certain companies for whatever reason.

You got to get that data somewhere. So do not skip making sure that your prompt library is being kept up to date just because you can build skills in these systems. Your prompt library is your foundation. Just like you want to have your documented SOPs, just because you've automated things, you still need the documentation in case the automation breaks down and you want to know, well, where in the process did it break? Well, it's a good thing I have all this really clear documentation that I can just look at.

You know, John, you do sales for Trust Insights, but we still have a sales playbook, you know, to reference, not because you know you yourself are not a good wealth of knowledge, but you're only one person. Yeah, well, and you've got to remember everything, right? Like that's the key, is that we don't have the capacity to take all this stuff. Um, I did want to ask about how has it worked so far? So the idea is that you know, this is a protocol, and so that these can go cross-platform all over the place.

How does it behave in the in real world though? Like, I mean, can you are you grabbing your skills and throwing them over into other tools and they're still working just as well? Or like how is how's the reality of that gone? Uh, for example, I use Quencode, which is the Alibaba Quen's coding tool, which is very similar to Cloud Code. I use open code, I use open co-work, uh, open work, and the skills perform flawlessly because they are they follow the standard.

They follow their the protocol has a clearly defined standard. And as long as you write to that, it is it, it is literally drag and drop. You just drag your, you can drag your clawed skills straight into Quencode and it works a perfect handoff. Um question that I think is worth pointing out to centralize the knowledge for skills and plugins. At a minimum, you know, you can have a shared resource.

What the best practice is to have a private company GitHub repository that is like basically a skills marketplace for your company, and you put in your company's skills in there. And here's why this is the best practice. Over time, as Katie said, things change. You will adapt stuff, you will get better at prompting, you will get better at using, you know, new models come out and things. If you use GitHub, a private company GitHub as your repository, then when you make changes, claw this is especially for Claude Code and Claude Cowork, because it's syncing with the marketplace.

When you make changes to the repository, all the Claude instances in your company that have downloaded that skill through the marketplace, auto-update. And so you don't have to go computer by computer anymore. You can now just update the marketplace, centralized. And if anti-gravity is using it, if codecs is using it, if Claude is using it, they all sync at the same time. And at a very small scale, I know that that's something that we've struggled with, just you know, so you know, we built a brand skill for the Trust Insights brand.

And there was a couple of things I wanted to change about it. I only changed it on my machine. The changes did not, you know, go into effect on Chris's machine. So that is why it's very important to make sure you have a way to centralize these. Because other like we're a small company.

I can just tell Chris, here's the changes I made, please go implement them. But that's not true of most companies. Exactly. So you will probably, if you're particularly at a large company, you'll probably want to ask, hey, can you know, do we have a company GitHub account in Canada? Can we have a section of repositories for just the folks who are using Claude Cowork so that you're not going to blow up, you know, your production, your software tree.

Uh, and then have users authorized and set up the marketplace internally inside GitHub that will then allow you to centralize and control your your plugins and your skills. And if you want to learn more about how all that works, you can subscribe to our new prompt playbook. It's a monthly subscription. Uh we drop two new prompts every single week, every Tuesday and Friday. You can go to trustinsights.ai/slash prompt playbook.

Um, we did our best to keep it low cost, effective, and uh, you know, accessible to anyone. So check it out. Uh, you can get those there and use the five Ps to get started to structure things. Go to TrustInsights.ai slash five Pramework. Um, and we covered a lot of those systems that Chris was talking about.

So Quen, um open open co open work and open code. Uh yeah. Yes. We covered all of those on last week's live stream. So you can go to trustinsights.ai/slash YouTube, go to the so what playlist, and that lives there.

Um, and then our very scientific poll has John in the lead of 100%. He is hands down the favorite host of this show. Congratulations, John, you get bragging rights. I may or may not have voted for myself. I will say that.

I mean, there's no rules against it. Yeah, I mean, I didn't vote for anyone, so that's my bad. So I'm going to now stop this poll. And it is official. John is the winner.

Excellent. I should also say too, you can do all this work or be like me and hire some people, have some people around who can do all this stuff for you and save yourself the work. There we go. You can go to the hands-down fan favorite live stream host, John Wall, and he will get you set up. So this is going to be part of your title.

Like he is the fan favorite. So if you want to work with Trust Insights, you get to talk to John. What a day. All right. I think on that note.

Any final thoughts about turning prompts into skills? Because the next evolution after this is you start building project plans composed in part of skills. I mean, the final thought is if this still feels overwhelming, then start with your standard operating procedures. How are you performing and completing any given task and start documenting that? That is a great place to start.

Make sure those things are getting into a central repository, and then you can start turning them into skills. Yep. Oh, one other thing I forgot to mention. I don't know if folks know this, but this is a super nerd thing. Um, clawed code is capable of running headless.

Not like a chicken. Um, but it means you don't have to be typing in clawed code. So you could actually create that prompt, like convert all my prompts into skills, um, with the appropriate skills, and just run it as a command line command, which means that you could schedule it. So on a monthly basis, if you have Google Keep or SharePoint or whatever, and you have all the utilities, you could have a monthly rescheduled task running on some computer somewhere in your company that automatically converts and publishes and runs the whole workflow. Um and and move your company up to level three very, very quickly.

Uh, you can do the same in co-work. So again, it and I and I bring that up because if you're not comfortable in code, you can also. I have I think two schedule tasks that are set to run now on a regular basis in co-work. And then I ran a whole scheduled four-part project a few weeks ago uh that I put about on LinkedIn that all just ran overnight to sort of again uh work out the sort of usage limits. So you can you have options for those schedules, but take advantage of them.

Yep. Is that correct? I think that's level five or level eight, which has yet to be defined. I don't know. I'm just better that John won, so I have to put myself at like level 10.

All right, that's gonna do it for this week, folks. Thanks for tuning in. Talk to you on the next one. Thanks for watching today. Be sure to subscribe to our show wherever you're watching it for more resources and to learn more, check out the Trust Insights Podcast at TrustInsights.ai slash Ti podcast at a weekly email newsletter at trustInsights.ai slash newsletter.

Got questions about what you saw in today's episode? Join our free Analytics for Marketers Slack group at trustInsights.ai slash analytics for marketers. See you next time.