The toughest part about building good skills and building a good operating system is trying to get everything from your brain into your system. So for example, what you're looking at here is after months and months of me building up all of the knowledge that lives inside of my AIOS.
It's basically just the idea that if everyone's using the same model, so if everyone's using Cloud Opus 4.8,
then everyone's gonna be using the same prompts and getting the same output because the model is fundamentally the same for everybody. So what really makes the difference is when you add context into that model and you give it your taste, your voice, your decisions, and that's how you get outputs that actually sound like you. But once again, the real challenge is still the extraction,
getting everything from your head into the AI system so that your skills can use it and that your context is better. And if you guys have been following me for a while and you've seen videos I've made about, like, discovery calls and and scoping out projects, that's the toughest part is especially if you're working with a client, asking them so many questions about this process to the point where they might even get annoyed because you're asking so many questions, but that's just what you have to do. It's the difference between a system that is successful 95% of the time and one that's only successful 80% of the time. So this one skill we're gonna look at today is called grill me. It basically takes what's in your head into reusable context for your AI. So what happens is all of that knowledge that's in your head that you might think, okay. I'm just gonna brain dump into clawed code for five minutes, it will be good enough. It's not ever good enough. So what this does is it basically relentlessly asks you questions. It grills you until it knows pretty much everything about the process. It'll ask you a question. You answer it, and then it basically will checkpoint, and it will write everything back to a knowledge doc, and it will just keep going over this loop endlessly until the knowledge doc is good enough and there's no gaps or holes in that knowledge. And so like I said, this results to better skills, better context, and better projects. And originally, this skill was built by Matt Pocock, and what's cool is if you look at it, it is a super simple prompt. It's like four to five sentences. Interview me relentlessly about every aspect of this plan until we reach a shared understanding.
Walk down each branch of the design tree, resolving dependencies between decisions one by one. For each question, provide your recommended answer. Ask questions one at a time. If a question can be answered by exploring the codebase, explore the codebase instead. And I like to look at that because it makes you realize that a skill doesn't have to be super complicated automation.
A skill can just be a prompt that you don't wanna have to say every single time. And, of course, naturally, what did I do? I destroyed that. I ruined the skill. I made it a little bit more complex, but I added something that I think makes it much better. So if I go into my dot Claude, I go down to my skills, and we look for the grill me right here, and I open up the skill.md,
you can see it's a little bit longer now. But, basically, what I did is I worked in that whole element of checkpointing after every single question.
Because, originally, the skill doesn't do that. And what happens is if you are talking you know, if it's grilling you for an hour plus, which sometimes it will, and that's a good thing, then as the context window starts to fill up, I started to get worried that it was gonna misremember some of my answers from earlier. So I just found myself telling it manually, hey. Write this to a doc. Write this to a doc. Checkpoint every time. And so I figured, okay. Why not just work that into the skill? So now what the skill does is it creates a folder called brainstorms,
and it does this at the root of your project. So if I go down here, you can see I've got a brainstorm file or sorry, a brainstorm folder right here with these four brainstorms. And so it will create that for you if you don't have it, but if you do have it, it will just chuck a doc in there, a markdown file right away. And so then if I open up, like, for example, this packaging one, which I was doing, it will find, like, the algorithm, the key decisions, but then it will also show you the step by step q and a log of the questions that it asked and what I answered with and the key highlights. And then as soon as we finally got to the end of that packaging grill me session, it said, hey. I noticed you have this packaging guide
and you have a packaging skill, and there's a lot of nuance here that we talked about that's not in there. So do want me to update both of those? And then I said yes, and now those skills and docs are so much better. I also did one where I said, hey. I want you to understand everything about the business, and we walked through from beginning to end all the decisions, all the processes,
and now my OS just feels like it knows even more about the way the business works. And so if you think about it like this, right, like, nothing is going to be perfect on the first try. And so let me just do a quick visualization.
This is kind of the old way when you're building a skill. Right? So we've got iterations down here. Let's say by iteration one, after you've knowledge dumped in your brain and you wanna build a skill, you maybe get somewhere, let's just say around here, where you're about, like, 70%
successful on iteration one. And then what happens is you run the skill and you make a small improvement, and now you're up about, I don't know, right here. Like, you go up from 70% to 75. And then every time you iterate, you get a little bit better with each iteration until maybe you cap at the point where you're about, like,
95%
good. And this could be 10 iterations. It could be 30 iterations. It however many it takes for your skill to feel a bit more battle tested. And, honestly, I don't think you ever get to a 100% because as your business evolves and as you evolve,
the skill keeps evolving. So, like, all my skills that I've been using for months and months,
I'm pretty much still changing a lot. But the whole idea is what if on iteration one, because you do this grill me and you spend extra time upfront, you're able to jump right up here to, like, 90 at the beginning? And, yes, it's not perfect. You're still gonna iterate a little bit, but you're just there a lot quicker, which gives you more opportunity to find better ways to iterate on it. So that's my horrible visual of why I think this is valuable. It just goes back to that whole idea of if I had six hours to chop down a tree, I would spend the first four sharpening the axe, where up front, yes, maybe it feels boring or repetitive, but that's what you need to do is get all that context in there because it helps downstream
so much more. So, anyways, if you guys wanna grab the grill me skill, you can look it up here from Matt Pocock. Or if you want my version, you can come to my free school community. The link for that is down in the description. Just join the community. Go to the classroom. Click on all YouTube resources, and it will be right in there for you to find along with all my other free resources. And then it's as simple as saying, hey. Grill me about this. Or, of course, you can invoke it with a slash command right there. You can see grill me. But I could just say something as simple as, hey. I need you to grill me about the way that I think about applying AI to my own business internally in a safe way that won't damage the business. You can see it'll obviously load up that grill me skill. We're gonna see in a second that it's going to create the capture file so nothing gets lost right there. We have applying AI internally, and this is what it looks like. It's gonna set up the discovery notes, the summary key decisions,
um, q and a log, and any open flags. And what's cool about this is it'll flag things that you need to go find. So when I was running through this funnel map, you know, there were some things going on in the business that I don't actually know super well. Like, I can't explain the same way as the actual stakeholder or operator that does that process can explain it. So it said, hey. Here's some things to flag. Go reach out to this person and have them send you an information, and then come back and drop that into me, and then we'll update this brainstorm. So that's basically how it works. It might ask you five questions. It might ask you 30. It's just gonna go until you guys feel like you have the same shared knowledge and that it is a good stopping point. And the cool thing is because these are saved as docs, you can reference them later, but you could also come back to, like, for example, packaging. Let's say I I find a major breakthrough in the way that I package my content. I would just come back to this doc and say, hey.
Grill me again. Here's some new things I found. Let's update all this information. So, anyways, I do know that this one was super quick, but I thought that, you know, there's no need to really make this video that much longer. So go grab the skill. Go start grilling yourself about different skills and processes that live in your business, and just start making your OS and your skills better. So that's gonna do it for this one. If you guys enjoyed or learned something new, please give it a like. Helps me out a ton. And as always, I appreciate you guys made it to the end of the video, and I will see you all in the next one. Thanks, guys.