Sklm: A CLI Tool to Centralize and Sync Skills for AI Agents
Sklm is a CLI tool that centralizes management of skill files for AI agents, allowing global storage and per-project activation. It solves the tension between global availability and project scoping.
Sklm: Centralize, scope, and sync skills for every AI agent | Product Hunt
Sklm
Launching today
Centralize, scope, and sync skills for every AI agent
17 followers
Centralize, scope, and sync skills for every AI agent
17 followers
Visit website
Sklm is a CLI tool that centralizes management of skills (SKILL.md files) for your AI agents. It solves the tension between wanting skills globally available vs. per-project scoped, without polluting your agent's configuration. Multi-agent support - Global store - Registry discovery - Auto-sync
Overview
Reviews
Alternatives
Built with
Team
More
Free
Launch tags:Developer Tools•Artificial Intelligence•GitHub
Launch Team / Built With
Subscribe
Promoted
Maker
📌
Hello everyone!
I was fed up with collecting skills across all my agents, which was cluttering up my list in my projects. So I switched to installing them on a project-by-project basis, but I also got tired of having to remember which skills I’d used previously.
So I coded a tool this weekend, in the form of a CLI: Just like with skills.sh, you give the CLI the skill’s repo, and it’ll store it in a global ‘store’; then, project by project, you simply activate the skills you need – those not active in the project aren’t available in that one.
https://auran0s.github.io/Sklm/
Migration is available if you already have skills installed. 8 agents are already supported.
The whole thing is licensed under the MIT licence I’d love to hear your feedback; it’s my first personal open-source project in production.
Report
1d ago
Nice launch. The global-store vs project-scope split is exactly the tension that shows up once people collect more than a few SKILL.md files.
One thing I’d be curious about is reproducibility: can a project lock the exact skill version/source commit it activated, so another machine or teammate gets the same behavior later? For agent workflows, “which skill was active” is almost part of the build environment.
Report
2h ago
Maker
@studentzuo Thanks for your feedback!
That’s an interesting question. I haven’t looked into version management for skills yet, but it’s something I'm planning to do.
Report
1h ago