Manage Cline skills for your team
Approve a skill once and it lands in Cline on every developer's machine, at the approved version. Ban one and it's removed everywhere. Every run is recorded in a tamper-evident audit log.
- Skills, every project
- ~/.cline/skills
- Skills, in a repository
- .cline/skills .clinerules/skills
- Also installed
- Skills only
- Blocks at invocation
- No hook to refuse a skill; banned skills are removed
Cline reads repository skills from both .cline/skills and .clinerules/skills.
Set it up
Paste this into Cline. It reads the setup guide, installs what it needs and asks you to sign in once:
Or by hand, from a terminal:
Questions
- Where does Cline look for skills?
- For every project: ~/.cline/skills. Inside a repository: .cline/skills and .clinerules/skills.
- Can skillsvault block a skill in Cline?
- skillsvault removes banned skills from Cline's folders on every machine and never installs them. Cline has no hook that can refuse a skill at the moment it runs, so a skill someone copies in by hand isn't stopped at invocation; skillsvault's scan reports it.
- What does skillsvault install into Cline?
- Your organisation's approved skills, each at the version the registry approves.
- Is it free?
- Free for one developer. Teams pay per member: €20 a month on Team, €40 on Business.
One registry for all of them
The same approved list reaches every agent your team uses.
Start with the skills you already have
skillsvault scan lists every skill on this machine across all your agents and flags the risky ones. It runs locally, with no account.