Features

Everything you need to manage AI skills

Create, version, share, and sync — from solo projects to large teams.

Create Version Sync Share Agents Registry

Create skills from scratch or import existing ones

Already have instructions scattered across CLAUDE.md and .cursorrules? Import them. Starting fresh? The editor opens automatically.

# Create a new skill from scratch
$ skill new deploy-checklist
  ✓ Created deploy-checklist v1.0.0
  ✓ Opening in editor...

# Import existing agent instructions
$ skill import
  Found 3 instruction files:
    CLAUDE.md → claude-setup
    .cursorrules → cursor-config
    codex.md → codex-rules
  ✓ Imported 3 skills

# Create from a file
$ skill new api-guide --content ./API_RULES.md

Semantic versioning with lockfiles

Every edit creates a new version. Lockfiles pin exact versions and content hashes so your whole team stays in sync.

# Publish a new version
$ skill publish code-review --minor
  ✓ Published code-review v1.1.0

# Pin versions in your project
# .skills.yaml
skills:
  - slug: code-review
    version: "^1.0.0"     # latest compatible
  - slug: deploy-checklist
    version: "2.1.0"      # exact

# .skills.lock (auto-generated)
skills:
  - slug: code-review
    version: "1.1.0"
    sha256: "a1b2c3..."

One command installs everything

skill sync reads your config, resolves versions, installs skill files, and auto-wires agent configs. Every agent discovers skills immediately.

$ skill sync

  ✓ Resolved 4 skills
  ✓ Installed code-review@1.1.0
  ✓ Installed deploy-checklist@2.1.0
  ✓ Installed api-standards@1.0.0
  ✓ Installed testing-guide@3.2.1
  ✓ Updated CLAUDE.md
  ✓ Updated AGENTS.md
  ✓ Updated .cursor/rules/overskill.mdc
  ✓ Generated SKILLS_INDEX.md

Cloud registries for teams

Push skills to a shared registry. Teammates add them to their projects. Role-based access controls who can read, contribute, and administrate.

# Push a skill to your personal registry
$ skill push code-review --create

# Create an org registry
$ skill registry create acme-inc \
    --name "Acme Engineering"

# Invite teammates
$ skill registry invite acme-inc \
    --email dev@acme.com \
    --role contributor

# List all registries you have access to
$ skill registry list
  personal   jake         admin
  org        acme-inc     contributor

Every agent, zero configuration

Overskill automatically updates CLAUDE.md for Claude Code, AGENTS.md for Codex, and .cursor/rules/ for Cursor. Skills just work.

# After sync, your project has:

CLAUDE.md          ← managed section added
AGENTS.md          ← managed section added
.cursor/rules/
  overskill.mdc    ← auto-generated

.skills/
  SKILLS_INDEX.md  ← agent reads this first
  code-review/
    SKILL.md       ← full instructions
    meta.yaml      ← version, tags, compat
  deploy-checklist/
    SKILL.md
    meta.yaml

Content-addressed local storage

Skills are stored by SHA256 hash. Same content is never stored twice. Integrity is verified on every read. All writes are atomic.

~/.overskill/registry/
  objects/
    a1b2c3...    # raw SKILL.md content
    d4e5f6...    # deduplicated by hash
  skills/
    code-review/
      meta.yaml       # name, description, tags
      versions.yaml   # all versions + provenance
    deploy-checklist/
      meta.yaml
      versions.yaml

Ready to try it?

$npm install -g overskill

Quick start guide