How I manage 40+ skills across Claude Code, Codex, and .agents folders
The article discusses the author's experience managing over forty skills across various AI tools. It highlights the challenges faced due to skill accumulation, including latency and incorrect suggestions. The author shares attempts to streamline the management of these skills, ultimately leading to the development of a small Go CLI tool.
- ▪The author started with three skills and accumulated over forty within a year.
- ▪Each session loaded all skills, leading to issues like incorrect suggestions and increased latency.
- ▪Various attempts to manage skills included moving files, using shell aliases, and writing a bash script with symlinks.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3951692) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } BSO Posted on May 26 How I manage 40+ skills across Claude Code, Codex, and .agents folders #claude #ai #cli #productivity I started with three skills. A year later I had forty-something. Every Claude Code session loaded all of them. Every Codex run loaded all of them. Every .agents-based tool I tried loaded all of them. The folders are global. The work isn't.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).