Ask HN on managing skills files draws 144 comments and a clear practitioner consensus: git repo plus symlinks, evals as integration tests, and automated drift checks
The thread posted 2026-09-06 reached 169 points and 144 comments, and the answers converge on a pattern nobody has written up as a standard: keep skills in one version-controlled repo (or dotfiles via chezmoi/guix home), symlink into every harness's skills directory, and let frontmatter progressive disclosure handle selection. Several people go further, running AI evals against skills as behavioural integration tests, and one team runs a biweekly agentic workflow that diffs skill content against the docs and opens PRs when they drift. Named tooling in the thread includes vercel-labs/skills (30,587 stars, MIT, pushed 2026-09-06), genged/capshelf, skillcatalog.dev, Microsoft's APM, and a proposed mise standard for shipping skills alongside CLI tools; a visible minority argues skills are redundant now that agents read repos and AGENTS.md well enough.
Source
↳ Follow the thread