>> Yep. >> Uh so moving on to the next section, we're going to make that skill smarter. So the first thing that you can do to make your skill smart is by providing more information to it. But this gets into the problem of the claw.md where you can be extremely verbose in there and give it so much information about your repo and you're just bloating the context window cuz it doesn't really matter. Well, you can do the same thing in skills, but you can do it in a better way. And that is specifically with progressive disclosure. And I guess you could do this in a claw.md as well. But all it is is just saying like, "Hey, if you're thinking about doing testing for Excuse me, for example, and read through it." And you just give it like a path like a local path to testing.md. Or whatever. And that way it's only going to load that if it's actually doing like a testing skill or testing task as part of the skill run. If it's not, it'll skip that. And so you can specifically tell it like, "Oh, in in this example, if you're doing like a scoring like if you're if this is a run where it's doing scoring, run the scoring launch load the scoring rubric and read through that so we explain to you how to score things properly. If we're not doing scoring, you don't have to load that and we don't have to fill up the context window with all of that blow." >> Yep. This also gets back to that gentleman's question in the back too of like you can imagine this pattern really scaling out. So the way that it actually did scale out even in our public work OS skills repo you can go and check out. We have multiple migration guys that we publish for various folks. So like if you're coming from off zero, we'll happily help you move off off zero to get to work OS. And then there's N number of you know competitors essentially that we've got migration scripts for. And so in this case you could say here's the migration skill and the migration skill is a pointer to the specific reference. So you're not bloating your context window. It's just loading the two markdown files it needs. >> Yep. And if you look at the work OS skill like it we literally call it skill router in there and it just has like a reference map. So if you're going to install off kit into next JS, you should probably load the work OS off kit next JS.md file from from And so if you're not working with next JS, we don't want to we don't want to load that and bloat that. We only load it when you need it for all of those. And so, this file is just filled with uh