> "Skills" as developer macros can be useful, but at most those are things shared with the team (in the repo), not something you download from the internet. If

> "Skills" as developer macros can be useful, but at most those are things shared with the team (in the repo), not something you download from the internet. If you have so many skills that you feel the need to manage them, that's a code smell. I have three development machines. You kinda need something like git to keep everyone in sync! And there's still value in encoding a process in a skill - it's way more token efficient to tell the model what but also HOW to do something. Otherwise, it just spends a lot of tokens figuring out something that they previously did already.