Greg Isenberg

Right.

It's in every single turn.

But this is where the beauty of skills come.

I'll show my screen here.

Your skill, again, this is not like word for word how it looks, but a skill basically looks like this.

There is a name.

There is a description.

And then underneath is a bunch of information.

I'm going to put a bunch of info.

When you create a skill.md file, what gets added into the context is actually just the name and the description.

Right.

The bunch of info doesn't get added.

So imagine you have two sentences versus an agent on MD that has like a thousand lines that get added into the context.

We're talking thousands of tokens compared to a couple hundred.

And the agent only gets the bunch of info when it realizes it needs this skill.

So if I have, let's say, a certain way of generating a report, a certain way of structuring my code.

Why would I put that in the agent.md file when I can have the agent call on it progressively when it needs it, right?

So this is why skills are honestly like I'm a shill, I'm a maxi, but people do it wrong.

And I'm going to share the right way on how do we create skills.

So, so far we have the system prompt, the agent.md, the skills, and then we have the tools, right?