>> Yeah. >> And and can go from there. And then like Zach was saying, like reflect on the transcripts, reflect on how you're actually using the skills and you can use that as insight to see how to improve the skills and the execution of those skills. Like for example, if somebody kicks off a skill and it's always asking questions about you know, a specific thing, maybe that's something that you can provide ahead of time. Or if you see it like, "Oh, it's going and doing like 10 tool calls." Maybe you could like condense it down to one or two tool calls and pre-provide that information so it doesn't have to do that each time. >> Yep. The plus one recommendation on the internal skill creator and then the other thing it kind of suggest I mean suggest to you to do over time is to think about the way you manage your context, even stuff that you used to think of as disposable, right? So, like in the pre-LLM era, we might have dev'd real hard at the keyboard all week, as I used to do, and then finally on Saturday, like wipe it all away so that I can GitHub for myself. Like now, all of that context is gold. Like the conversation, especially what failed, especially what didn't go well, especially what was frustrating, because now all of that is very rich context for a skill creator or refiner to mine, and then build you a bespoke tool that's going to solve that problem smoothly next week.