Quiver
A CLI sync layer for AI agent skills — push your globally installed skills to a private GitHub Gist and restore them on any machine with a single command.
Quiver solves a small but frustrating problem: when you install skills globally for your AI agents — Claude Code, Cursor, Gemini CLI, GitHub Copilot — they live in ~/.agents/.skill-lock.json. Move to a new machine and that file doesn't come with you. Quiver fixes that without a proprietary backend, a new account, or a server to maintain.
The model is intentionally simple. quiver push reads your local lock file and uploads it to a secret GitHub Gist. quiver sync fetches that Gist on any other device and reinstalls every missing skill. Sync is additive only — it never removes or overwrites what's already local.
Quiver is agent-agnostic by design. It doesn't care which agents your skills target — it syncs whatever is in the global lock file. It's also not a package manager: skill installation still goes through npx skills. Quiver only learns about installs after the fact, keeping it fully decoupled from the install workflow.
The CLI is built with TypeScript and oclif, published to npm as usequiver. The web app (Next.js + Fumadocs) is purely static — marketing and docs only. Authentication runs through GitHub OAuth device flow, which also yields the gist scope token the CLI uses directly for all storage operations. No lock data ever touches a Quiver server.
One extra: quiver remove patches a known bug in npx skills rm — the official command removes skill files but leaves stale entries in the lock file. Quiver does the full cleanup, fixes the lock, and pushes the update.
TypeScript, oclif, Next.js 16, Tailwind CSS v4, Fumadocs, GitHub Gist API, GitHub OAuth (RFC 8628), Turborepo, pnpm workspaces, Changesets, Vercel