Cleo is a dependency manager for Claude Code. One manifest pulls rules, skills, agents, commands, hooks, and MCP configs from any git repo. cleo install gives your whole team the same setup. cleo update keeps it current. cleo.lock pins exact versions and commit SHAs — reproducible and auditable. No registry, no signup — vendor/name resolves to GitHub automatically. Every install validates paths, refs, manifest shape, and hook sizes. Works as a Claude Code plugin or standalone CLI via pip.

Framer — Launch websites with enterprise needs at startup speeds.

Launch websites with enterprise needs at startup speeds.

Hey Product Hunt! I'm Erik, the maker of Cleo. I built Cleo because managing Claude Code configurations across multiple repos and team members was becoming painful. Everyone was copy-pasting skills and rules manually, with no way to version, update, or share them consistently. Cleo solves this with a familiar mental model — it works exactly like npm, pip, or Composer, but for everything in your .claude/ directory: cleo require Surt/cleo-plan-then-doc # install a package cleo install # reproducible team setup cleo update # stay current Key things that make it different: Zero infrastructure — packages are just git repos with semver tags. No registry, no signup, no central server. Security-first — every install validates paths, refs, manifest shape, and hook sizes before writing anything. Three scopes — team (committed), local (gitignored), global (~/.claude/) — so you can keep personal customizations separate. The project is GPL-3.0, 100% open source, and has no runtime deps beyond Python 3.9+ and git. I'd love your feedback! What other package management features would be useful for the Claude ecosystem?

Framer — Launch websites with enterprise needs at startup speeds.

Launch websites with enterprise needs at startup speeds.

Cleo

The dependency manager for Claude Code

The dependency manager for Claude Code