I read somewhere that Boris (created Claude Code) recommends deleting skills, and hooks every so often and then observe how the LLM performs without them. Maybe better to periodically prune: tweak some skills, shorten some, delete some.
Ask HN: How do you manage skills files?
271–280 of 317 posts
Re: Ask HN: How do you manage skills files?
#272Re: Ask HN: How do you manage skills files?
#273Earlier quoted context omitted.
How do you actually measure the token savings? Do you compare the same task with and without the skill, or is it more of a noticeable difference over time?
Both, in a way. In order to be sure it's the skill reducing token usage, you measure it with and without the skill, and then you do that periodically to account for all the other variables. Alternatively, you pick a belief based on prior evidence from either approach you mentioned, which is the natural thing that many of us do.
But what about "I"?
Re: Ask HN: How do you manage skills files?
#274I built Skill Grill, an open-source directory and community trust layer for AI agent skills.
Its live now at https://skillgrill.dev
I'm not sure about posting links in threads but this project needs community backing in order to work and its free :)
Its still in MVP stage, but feedback is welcome
Re: Ask HN: How do you manage skills files?
#275I ideally want to have a single place I store my skills with an easy way to make them available to my repos, Amp and ChatGPT desktop/iOS, Grok web but can’t see a way
Re: Ask HN: How do you manage skills files?
#276Then, I use this tool:
https://github.com/a1st-dev/aix
to keep my Claude, Codex, and OpenCode in sync with my config.
The major benefits are that my adoption/deletion of skills, rules, hooks, MCP servers, etc. are deliberate, versioned, and shareable.
And since aix allows you to create extensible configs, that aix-config public GitHub repo is my base set of rules, and my internal/employer-specific rules are just a small layer on top of that.
It also makes trying out different subscriptions easy: you define your config in one place (one source of truth), and write to Claude, Codex, Devin, etc. with one command.
Re: Ask HN: How do you manage skills files?
#277Re: Ask HN: How do you manage skills files?
#278Anyone got a good flow for sharing their skills across their various repos and apps? I ideally want to have a single place I store my skills with an easy way to make them available to my repos, Amp and ChatGPT desktop/iOS, Grok web but can’t see a way
Though it does not support ChatGPT (just the Codex part inside of the ChatGPT app), or Grok web (yet).
But it does encourage you to keep versioned config in one spot. You can also commit repo-specific config to any project that has specific needs, and translate that config into . That can be helpful when working with a team or an open source project that needs to support a variety of agents/tools.
It currently supports 8 editors/agents: https://aix.a1st.dev/editors/supported-editors/
Re: Ask HN: How do you manage skills files?
#279I've put mine inside `~/.agents/skills` and `ln`ed all `skills` folders that I could to point to them. It only doesn't work for Claude Desktop. But it works for grok, antigravity and cc CLIs (for some, at least partially).
I've been using this heavily the past 6 months to solve exactly this problem: https://github.com/a1st-dev/aix It doesn't support Grok (yet) though.
Re: Ask HN: How do you manage skills files?
#280I commit my standard set of agent configuration (including Skills) to this repo, similar to how many people have a "dotfiles" repo: https://github.com/yokuze/aix-config Then, I use this tool: https://github.com/a1st-dev/aix to keep my Claude, Codex, and OpenCode in sync with my config. The major benefits are that my adoption/deletion of skills, rules, hooks, MCP servers, etc. are deliberate, versioned, and shareable.…