Video · David Ondrej ·
More skills = worse agents (do this instead)
In short
The video argues that copying large viral skill repositories can overload an AI agent’s context, waste tokens, and reduce reliability. Instead, keep only a small set of trusted, task-specific skills, create custom skills from recurring workflows, and separate global skills from project-specific ones.
Key points
- Delete roughly 80–90% of unused skills after reviewing session-usage data.
- Treat skills as agent SOPs: repeatable workflows encoded for a specific task.
- Prefer specialized project skills over vague global skills that load everywhere.
- Use external skills only when they come from a trusted expert or organization.
- Use a second frontier model to review substantial changes made by the first.
- Create skills when a workflow is recurring, specialized, or likely to be repeated.
- Share domain-specific skills through team repositories so expertise becomes reusable.
Written by an AI model from the video’s captions and description.
In this video, David Ondrej explains how he uses agent skills for development and why you should not be copying other people's skills but instead creating your own. He also goes into how to develop code using cloud agents inside of Cloudroom.
In this story
A tool or model opens in the Heidelberg AI Curriculum: what it does, what it costs, how to start. A repo opens on GitHub.



