Top
Best
New

Posted by imadtaieber 1 day ago

Ask HN: How do you manage skills files?

How do you find skills, keep them organized, and make sure they actually work? Do you keep improving them over time?

I believe skills will eventually be eating by model capabilities, but until then I'm just looking for a better way to manage things.

269 points | 249 commentspage 14
suemto 8 hours ago|
[dead]
hoffiez 8 hours ago||
[dead]
dstracted 11 hours ago||
[dead]
rsingh888 9 hours ago||
[dead]
rsingh888 9 hours ago||
[dead]
DarmokTanagra 11 hours ago||
[dead]
adastra22 15 hours ago||
Skills are no longer useful.
prettyblocks 15 hours ago|
I find them very useful.
adastra22 15 hours ago||
I have been finding them decreasing in the effectiveness with each model release. We got rid of skills and built a determinist harness around the agent instead.
prettyblocks 3 hours ago||
I use skills to automate non-development workflows, like for malware analysis, etc.
mercurialsolo 15 hours ago||
One of the engineers I know is building this product called SkillEd for just this. Lemme know if you need an invite
jiaosdjf 10 hours ago|
WTF is a "skill"? I really think people are getting ahead of themselves here.

You wrote some bullet points so your agent harness doesn't keep making builds in the wrong environment? You have a very specific debugging setup? Your agent doesn't understand when to rebase?

README is where you should be writing anything specific to your project, and if you're worried about context size then your README is too long, it should be just enough information for any competent dev or agent to get the gist of how you do things around here and where to look for deeper answers.

If your particular harness / orchestrator is just not pushing back enough or can't seem to solve certain problems then thats a tool issue, either edit the tool system prompts or move to better tools or models.

Calling this 'skills' is disingenuous, this word was chosen by marketers and implies some kind of deeper learning. I'm not saying there's no value in tuning prompts, but your 'skills' should be managed in only 2 ways: 1. It's specific to your project, it's a README, or 2. It's specific to your tooling, it's part of config, system prompts etc.

8note 2 hours ago||
a skill gets injected into context in a certain way, and behaves in certain ways with respect to things like compaction.

the readme and agent.md are not the right places to put long workflows worth of llm instructions, and also isnt the right place to put global details.

skills also get a piece of text injected into context all the time, so the agent gets a hint to go read and follow the whole thing, without needing to embed the whole definition into context all of the time.

invaliduser 9 hours ago||
I mainly use them as macros. Not even an advanced and smart macro system, just plain basic macros to avoid copy-pasting recurrent prompts. Is there more to them?