skael

skael is the private control plane for your team’s AI agent skills. Your SKILL.md files stop living in scattered home directories and half-synced repos. You publish once, and skael:

• versions every skill (immutable, content-addressable),
• scans it for secrets, prompt injection, and exfiltration on publish,
• governs it — holds a change to a namespace until someone who owns it says yes,
• measures whether it actually works, by running it against real tasks,
• syncs it to Claude Code, Cursor, Codex, and OpenCode on every developer’s machine,
• and shows you which skills actually fire — by which agent, how often.

Self-hosted and open source.

Where to go next

• Quickstart — get the platform and CLI running in a couple of minutes.
• Core concepts — skills, versions, selective sync, auto-sync, scanning, ownership, quality, activations.
• Skill ownership — who may publish to a name, and why an upgrade changes nothing until you write a rule.
• CLI reference — every skael command.
• whetstone — the authoring CLI: draft, lint, and score a skill before you publish it.
• Self-hosting — run the platform on your own infrastructure.
• Why not just git? — how skael differs from a shared repo or native agent sharing.