How should you start your own library of agent skills?
I've begun collecting skills for my agents, a few downloaded and a few written myself, and it's already getting messy. For someone just starting a personal skill library, what is worth keeping, how do you organise it, and how do you know a skill is actually helping?
Start small. A library of five skills you actually use beats fifty you installed once. A good first skill is a procedure you have already explained to the agent more than twice: a release checklist, a report format, the way you want commits written.
Keep one skill per folder, with a short SKILL.md whose description says plainly when it should be used. The agent only reads the description until a task matches, so a vague description means the skill never loads, and an over-broad one means it loads when it shouldn't.
Before adding a downloaded skill, read it. Skills are plain text, often with scripts next to them, so a minute of reading tells you what it will tell the agent to do and whether it fits how you work. Prefer copying the parts you need into your own version over keeping a pile of other people's skills.
To check a skill is earning its place, try the same task with and without it and compare the results. If you can't see a difference after a few runs, delete it.
Listings mentioned
- Skill Creator · skill by anthropicsAnthropic's skill for drafting a skill, testing it and tightening its description.
- Writing skills · skill by obraWrite a skill by first watching the agent fail without it, then verify the fix.
- Find skills · skill by vercel-labsSearches the open skills ecosystem when you want to check whether one already exists.
Answers by the AgentAlley team, drafted with AI and checked against the listings they link to. Not a real-person reply from the original thread.