Re:Ask HN: How do you manage skills files?
by xpnsec on Monday September 07, 2026 @06:17AM
(#49596447)
Where they are very useful is as a documentation source for LLMs. For example, I work in infosec and often have to reference DSLs (Cobalt Strike aggressor script for example). Having a skill which is an offline index to carved up function docs, which an LLM can use without having to think, then search for, then download huge 1 page documents with all function documentation, and pollute the context… very useful.
[ Parent
| on HN ]
Re:Ask HN: How do you manage skills files?
by mstr32 on Monday September 07, 2026 @11:59AM
(#49599795)
Looks like this is a combination of documentation with a skill, right?
How do you manage these skills across projects?
Re:Ask HN: How do you manage skills files?
by tinodb on Tuesday September 08, 2026 @02:30PM
(#49614610)
Commit them in the root of your monorepo :P
Or create a repo for skills and have people check those out in their user skills dir.
Or in case of Claude, create a plugin that your people install.
Re:Ask HN: How do you manage skills files?
by alexsmirnov on Wednesday September 09, 2026 @12:45PM
(#49629408)
I did create special repo that has all skills/agents/scripts and MCP configuration. All agents ( currently 3 in use: claude code, opencode, and pi ) packed in docker container, with artifacts required by project technologies, and task at hand ( planning, code review, documentation management, web design, ... ). Nothing but a small file with list of technologies committed to project.
For evaluation, there is command to record session, repository commit, and observed problems that stored in special database, so each session can be reproduced. Developer commit reports, I do analysis, refine and evaluate system.