>> Yep. And and you know, of course this works too in just a single project context with some of those files that Nick mentioned, but then again the problem is that you're still tied to that repo. Uh you need your team members to remember to pull updates to that specific project skill if if they want the context. Um there's no necessarily built-in script execution. So how do you get how do you interleave a deterministic result when you're having a non-deterministic conversation with an LLM? And eventually that starts to get pretty gross. >> Yep. >> So. >> And the there's downsides to this uh specifically these memory files where if they're tied to the repos that you're working on or you have to put them globally so it affects everything. Uh and you can't do things like uh give it like more smarts like execute this script. You can, but it's kind of not built-in so to say. Um but that's kind of like where the things that you put in there are not always like transferable or portable to other projects that you might be working on uh and so we need a better way to do that. And skills are that next step. >> Yep, indeed. >> Uh it's a way to make things more portable uh and you can use scripts to inject real data uh and you can make them composable uh so that they can be very small and very focused on exactly what you want them to do uh and that way they're they're very small like a very small footprint in your your context window, but also uh you can build them in such a way that they are only going to be applicable when you actually want to do whatever that skill is set up to do. So you're not just bloating the context with everything from the start every time like you are with a claw.md. >> Yep. And so if you haven't seen or heard of a skill before just to level set really quick. It could be as simple as a a single static markdown file without any scripts at all. Um but let's look at the difference of what might happen. Let's imagine that we're roasting a repo or onboarding a new team member. We want to make sure that, you know, they're kind of up to snuff on how things work here. Without a skill, if you're just talking to any generic agent with no specific context injected, you're going to get, "Okay, looks pretty good." It's going to be generic advice. It might find some low-hanging fruit. If you say instead as little as 30 lines of markdown specific to your use case and your conventions, your >> constraints. >> Uh you can start to get back very, very like hyper-specific feedback about "This is how we handle, you know, routing in this project. These are, um you know, we we follow semantic commits or whatever. And we've got readme drift here and that's unacceptable, right?" So, it it can take as little as 30 lines of markdown or less. And so that's the one of the first things that makes skills incredibly powerful is that it's a very minimal investment on your part and it could be as simple as a small markdown file and it becomes a composable unit of work that you can share across codebases and your team.