Loading video...
Video Failed to Load
Introducing Skill Manager. Your coding agent loads every skill's description, whether it's needed or not wasting precious context and potentially loading conflicting skills. With Skill Manager you can switch skills on and off one at a time, group them by theme either manually or by using the AI auto-group... show more
21,067 views • 6 days ago •via X (Twitter)
27 Comments

for claude code, does off mean moving the skill out of the folder? there's a middle state worth a toggle: disable-model-invocation keeps the description out of context but /name still works, and skillOverrides in settings does the same for skills you didn't write without touching their files

It moves the skill folder to a holding directory. The middle state is an interesting idea, I'll explore it! Thanks.

This is very needed

Indeed!

Context tax from unused skill descriptions is real. Being able to toggle them per session is the missing piece.

This is the bit that bites me. Half the skills never fire and they still burn context every turn.

built a manager for the skills your agent cant manage on its own, we are three layers deep now

Sadly. Yes.

turtles all the way down

Awesome domain 😅

Ah you noticed! 🤣

Nice one! Thanks for sharing!

Context bloat from skills you aren't using is so real. Does it support profiles? I'd want a writing set and a coding set I can flip between.

Yes! Though I call them groups.

do group changes take effect in an already running agent session, or does it need a fresh session?

Depends on the client, Codex automatically detects skill changes in real-time but you'll most likely need to start a new session, which is best practice when switching tasks anyway.

It’s like keeping only the tools you need on the workbench: toggling skills reduces clutter in the agent’s context and makes conflicts easier to spot.

Love the vibe colors of the website. Congratulations on the launch!!

Thanks, finally launched something. Surprisingly it was Claude Code that got me over the line, Codex just wasn't cutting it.

I would love to hear any skills used for the design / UX. I am wandering and trying out but found none to be up to mark

Honestly, none. I had Claude research first: award-winning Mac and iOS utilities (Apple Design Award winners, CleanMyMac X, SoundSource 6, Linear) plus Apple's Passwords and Reminders, written up with real screenshots. The redesign grew out of that: one library modelled on Passwords, with its own colour for every destination. For the icon I pointed Claude at Matthew Skiles' work. The skeuomorphic skill cartridge, striped in those same colours, ties the whole theme together.

Amazing. Thanks for the details.

A tool to manage the skills my agent loads unnecessarily. Now I just need a tool to manage the tools.

cool, does toggling a skill off remove it from the current session's context, or do you need to start a new session for it to take effect?

Mostly likely need to start a new session. It this is good practice anyway when changing directions.

Looks really cool! One thing I'd love: per-project skill sets, so two agents working in different repos at the same time can each have their own active group, instead of one global switch. Any plans for that?

Eager-loading every skill description is silent context tax — and conflicting skills fight for the same tokens. Selective activation beats a bigger skill folder: load what the task needs, park the rest. #ClaudeCode #DevTools


