Skills are quietly becoming the unit of agent knowledge
8 points
1 day ago
| 3 comments
| HN
In the last few months agent skills went from a niche Claude Code feature to something every major runtime supports. Anthropic has an official skills repo. OpenAI shipped skills in Codex with a built-in skill-creator. Karpathy talks about "everything is skill issue" and describes writing skills as curricula for agents [1]. The format is converging: a folder with a SKILL.md, optional scripts, optional reference files.

What changed is that the models got good enough to follow written instructions reliably. A skill is just a tested workflow in markdown that the agent reads and follows instead of improvising. You can also bundle scripts that the agent runs during the workflow, which covers what most people use lightweight MCP servers for, except the agent can read the script source and extend it.

Karpathy talks about an "economy of agents" and says we should stop writing HTML docs for humans and start writing markdown docs for agents [1]. Anthropic just shipped a skill-creator that benchmarks whether a skill still works after model updates. There are already tens of thousands of community skills on GitHub.

Distribution still feels early. Most useful skills are tiny. A markdown file, maybe one script. Useful enough to keep reusing, but not something anyone turns into a proper GitHub repo with a README and install instructions. So they stay on one machine.

I have been writing skills for my own agents for a while and I keep running into this. The format works. Moving them between machines or handing one to someone else does not.

Curious if others are hitting the same wall or if there are approaches I am missing.

[1] https://www.youtube.com/watch?v=kwSVtQ7dziU (Karpathy on No Briars podcast, skills discussion around 1:03:40)

rbitr
4 hours ago
[-]
Will skills replace MCP servers eventually?
reply
manzanarama
15 hours ago
[-]
What do you think about checking the skills directly into the repo where they are useful?
reply
latand6
13 hours ago
[-]
Yeah, that's the default way to approach it, but the cognitive load is still a problem. Manually reviewing every single skill I might need just for one task is tedious. GitHub stars won't give you any useful signal. I actually started building a product that solves this.
reply
moomoo11
3 hours ago
[-]
How are skills different from Having the agent create todo-the-ticket.md (with me) that contain the work scope and steps.

That’s what I do for each ticket.

reply