kitter README

The project's README from github.com/what1f/kitter. As one markdown file: README.md.

Kitter — one skill library where every project gets only what it needs

简体中文

Apache-2.0 license macOS, Windows, and Linux desktop app Built with Rust

One skill library. Every project gets only what it needs.

Kitter is a desktop app and CLI for managing Agent Skills across projects. Keep your skills in one library, install the right combination for each project, and update them in one place.

Built entirely in Rust with GPUI, Kitter pairs a straightforward interface with a small footprint and smooth native performance.

Kitter maintains one skill library and links selected skills to projects and user-level installations

Why Kitter

Working across projects often means maintaining several copies of the same skill and keeping track of what each agent can use. Kitter keeps those connections visible:

Install Kitter

Download the app for your platform from GitHub Releases.

Kitter is not yet signed with an Apple Developer ID. If macOS blocks the first launch, confirm that you downloaded it from the official release, then go to System Settings → Privacy & Security → Open Anyway and follow the prompts. See Apple’s instructions.

You can also run the following command, then open Kitter again:

xattr -dr com.apple.quarantine /Applications/Kitter.app

The desktop app and CLI are separate release artifacts built on the same core. Standalone CLI packages for macOS, Windows, and Linux are available from GitHub Releases. The built-in Kitter skill resolves that standalone CLI and guides you through downloading it when needed.

Manage your skills with Kitter

1. Build one library

Use + to add skills from a local folder, GitHub or a skills.sh-compatible source, or a Claude plugin source. If skills are already scattered across projects, choose Existing installations to inspect and adopt them without moving their source directories.

Kitter keeps one maintained source for each skill. Open its Installs tab to immediately see every project using it, every installation location, and the agents that can discover it.

Kitter skill library showing one managed skill installed across several projects

2. Install only where needed

Select a skill, choose a project, then install it into the shared .agents/skills directory or an agent-specific directory. Kitter creates managed links instead of independent copies, so projects can use different combinations without creating update drift.

Kitter installation dialog for selecting a project and agent targets

Skills you use across all projects can also be installed at the user level.

3. Verify what is actually active

Open Projects to see the complete effective skill set for every agent—not just installations managed by Kitter. The view discovers project, parent, user-level, built-in, and plugin-provided capabilities, then shows where each one came from.

The per-agent token estimate helps you spot skills that add unnecessary context overhead.

Kitter project view showing managed and unmanaged effective skills, plugins, agents, and estimated context cost

4. Update once

Run Check for updates from the desktop app or use kitter check and kitter update. Every managed project continues to use the same maintained source.

The equivalent CLI workflow is intentionally small:

kitter add npx https://github.com/owner/repository --skill skill-a
kitter install skill-a --project /path/to/project --target universal
kitter project /path/to/project
kitter update skill-a

Standalone CLI and agent skill

You do not need the desktop app to use Kitter. Download the standalone CLI from GitHub Releases, put kitter on your PATH, and install the $kitter skill directly:

npx skills add what1f/kitter --skill kitter

The skill lets an agent inspect the current machine, add or adopt skill sources, install the right project combination, and verify the result through the standalone kitter CLI. If the CLI is missing, the skill can guide you through downloading it from an official Release.

Build from source 
git clone https://github.com/what1f/kitter.git
cd kitter
cargo run --release --locked --features desktop --bin kitter-desktop

Platform status

Local data

Kitter stores configuration and source records in the operating system's application-data directory. Skill contents live in the library directory:

Platform Default skill library
macOS ~/Library/Application Support/Kitter/skills
Windows %LOCALAPPDATA%\Kitter\skills
Linux $XDG_DATA_HOME/Kitter/skills or ~/.local/share/Kitter/skills

View or change the location with kitter library and kitter library --set /absolute/path.

Contributing

Issues and pull requests are welcome. Please open an issue before starting a large behavioral or UI change so the scope can be aligned first.

If Kitter makes your skill setup calmer, consider starring the repository. It helps more multi-project developers find it.

License

Kitter is available under the Apache License 2.0. Licenses for bundled fonts, icons, and other third-party material are listed in THIRD_PARTY_LICENSES.md.

Star History

Star History Chart

kitter (what1f/kitter)

Searching Database…

306 ·GitHub
Kitter
What is this?Kitter is a desktop app and CLI for managing Agent Skills across multiple projects: you keep skills in one library and install only the combination each project needs, updating them all from one place.
Is Kitter a desktop app or a command-line tool?Both — it ships as a native desktop app (built in Rust with GPUI) and a separate standalone CLI built from the same core, so you can use either one on its own.
How do I install Kitter?Download the release for your OS from GitHub Releases: a macOS .dmg (Apple Silicon or Intel), a Windows x64 .exe, or a Linux x64 .tar.gz, then run the app or extract and run the './Kitter' binary.
Do I need anything besides the downloaded binary to use it?No — the desktop app and CLI are self-contained; for CLI-only use just put the 'kitter' binary on your PATH and install the built-in $kitter skill.
Does Kitter work the same on every platform?Not fully yet — the macOS build isn't signed with an Apple Developer ID so Gatekeeper may block the first launch, and the Linux desktop app 'still needs validation on real systems' even though the CLI is stable there.
Where does Kitter store my skills and settings?Everything stays local: configuration and source records go in the OS application-data directory, and skill contents live in a library folder (e.g. '~/Library/Application Support/Kitter/skills' on macOS), which you can relocate with 'kitter library --set'.
What exactly is a Skill in Kitter?A Skill is a reusable capability an agent can discover and use; you can add them from a local folder, GitHub, a skills.sh-compatible source, or a Claude plugin source, and Kitter keeps one maintained copy per skill.
How do I update skills across all my projects at once?Run 'Check for updates' in the desktop app or use 'kitter check' and 'kitter update' from the CLI — since projects link to a shared source via managed links rather than copies, one update reaches every linked installation.
Can I see which skills an agent can actually use right now?Yes, the Projects view shows the complete effective skill set per agent, including installs made outside Kitter, their sources, and an estimated per-agent token/context cost.
Can I bring skills I already scattered across projects into Kitter?Yes — choose 'Existing installations' to inspect and adopt already-installed skills without moving or disturbing their original source directories.
What are similar projects?evondevKit, asd-ste100-skill, aichat, leviathan, aos-ce, coral, open-knowledge, pdfcraft
Which topics is it in?package-manager, skills, plugin, claude, agent-skills, rust, command-line-tool, gui, desktop-app, terminal, tool, ai-agents
Creator
what1f
Size
8.7 MB
Stars
306
Updated
CommitOct 17Releasev0.2.0Oct 17
Age
1mo
Commits · 90 Days