kitrovepreview Get Kitrove
RC4.1 · Guided setup is here

Try the next tool.
Take your
skills with you.

That skill you found. The instructions you refined. Collect them with Kitrove, then choose what to bring to another agent tool or computer.

Open source. Local-first. You review the changes.

YOUR PORTABLE COLLECTION01 / KITROVE
My everyday kit
A little less starting over.Keep the skills you want to use again.
Code reviewCatch the things you care about
skill
Writing voiceThe edits that make it sound like you
skill
Project conventionsA familiar way to work
skill
Collect → Review → Apply
Another tool Another computer
Illustrated collection. Compatibility depends on the skill and destination.

Built for people who
try more than one agent.

Discover what you haveKeep native detailsChoose where it goes

A collection you control

Keep what works.
Decide what travels.

Kitrove starts with the skills already on your computer. The walkthrough takes you through each choice, with a preview before you confirm.

  1. 01

    Find your skills

    Scan user-level skills and see their names and source tools. Pick from a readable list, without copying long IDs.

  2. 02

    Build your collection

    Choose which skills to adopt. Review each plan. Kitrove keeps the original files in place.

  3. 03

    Apply where you choose

    Select a destination and review what transfers. If a destination has an unmanaged file in the way, Kitrove stops instead of overwriting it.

Laptop, desktop, next computer

Your next setup
has a head start.

Run the walkthrough on a second computer and choose how much of your collection to bring. Each computer keeps its own identity and destinations.

Set up another computer

Connect the whole collection

Review a two-way sync through a Kitrove snapshot backend.

Combine what you have

Connect first, collect local skills, then review publishing the additions.

Bring selected items

Import specific assets or packs once, without changing the remote.

Start here

Install. Then let
Kitrove walk you through.

Kitrove is a release candidate. Start with a small collection and review each change.

macOS · Apple Silicon

Available

Install the preview with Homebrew, then open the guided setup.

brew install --cask kapital-labs/tap/kitrove-rc
kitrove init

Requires Homebrew. The cask currently supports Apple Silicon Macs only.

Already installed the preview?
brew update
brew upgrade --cask kapital-labs/tap/kitrove-rc
kitrove configure

Homebrew updates the binary. Your collection and setup are separate.

Windows

Manual preview

Windows x86_64 release artifacts are available. We have not published a WinGet or Chocolatey package.

Use the release verification instructions before running a download. Windows lifecycle acceptance remains open.

Read the manual release guide →

Linux

Manual preview

Linux x86_64 release artifacts are available. We have not published APT, DNF, or other Linux package-manager installs.

Use the release verification instructions before running a download. Native lifecycle testing is separate from building the archive.

Read the manual release guide →

Know what moves

Portable doesn't mean
identical everywhere.

Agent tools have different capabilities. Kitrove preserves native details and reports transfer fidelity so you can decide what to apply.

Credentials, accounts, trust decisions, and machine-specific paths stay outside collection sync. You still install and authorize each agent tool on each computer.

Read the boundaries →

Before you start

A few useful answers.

Does init create a folder?

Yes, after you confirm the plan. The walkthrough suggests ~/Kitrove for your collection and shows a separate machine-local state location. You can choose another collection location.

Does Kitrove sync in the background?

No. You start a sync operation and review the plan. Full sync can publish local additions as well as bring remote changes back.

Will it replace my existing skills?

Adoption leaves source files in place. Applying is a separate confirmation. Kitrove refuses unmanaged destination conflicts rather than overwriting them.

Is this a stable release?

No. RC4.1 is a prerelease. Clean-Mac online/offline first-launch testing, other native target coverage, and real two-machine acceptance remain separate open gates.