v0.2.7 · agent-agnostic

Keep your AI agent skills in sync across every device.

Quiver is a CLI sync layer for the global skills your agents share. Push from one machine, run quiver sync on the next, and pick up exactly where you left off — no dotfile scripts, no new accounts, no proprietary backend.

$npm install -g usequiver
See how it works
macbook-airwork-imacthinkpad-x1
// before
"I set up all my skills on my work machine and now I'm on my personal Mac and nothing is there."
// with quiver
quiver sync — one command, every skill, every agent, every device.
01 / Surface

Six commands. Zero ceremony.

Quiver does one thing — keep your global skills consistent across machines — and exposes the minimum surface to do it.

01
$quiverlogin

AUTHENTICATE

GitHub OAuth device flow. No new account, no new password — just your existing GitHub session.

02
$quiverpush

UPLOAD

Snapshots your global .skill-lock.json to a private Gist. Gist revision history doubles as an audit log.

03
$quiversync

INSTALL

Pulls the remote lock and replays missing installs. Additive only — never overwrites local work.

04
$quiverstatus

DIFF

Shows what differs between this device and the source of truth before you commit to anything.

05
$quiverremove<skill>

CLEAN REMOVE

Deletes the skill, fixes the lock file (npx skills leaves stale entries), and pushes the update.

06
$quiverwhoami

IDENTIFY

Prints the authenticated GitHub user, gist ID, device name and last sync timestamp.

02 / Flow

A sync layer, not another package manager.

Quiver sits between your global skill lock file and a private Gist. That's the entire architecture.

01

You install skills the usual way

Use npx skills add <repo> --skill <name> -g. Quiver does not replace your installer — it observes the lock file it produces.

02

quiver push uploads ~/.agents/.skill-lock.json

The lock file is written to a secret GitHub Gist named quiver-skill-lock.json. One Gist per user. No database, no proprietary backend.

03

On a new device: quiver sync

Quiver fetches the remote lock, groups missing skills by source repo, and installs all groups in parallel with live progress per source. Lock file is reconciled after every group settles. Additive only — your local work is never overwritten.

04

Your skills follow you

Work iMac, home laptop, the corporate lender — every machine ends up with the same set of agent skills, ready for Claude Code, Cursor, Gemini, Copilot, or whatever you use next.

device topologygithub gist · quiver-skill-lock.json
◆ gist://nublson/quiver-skill-lock.jsonrev #22
work-imacinstalling…
~/.agents/.skill-lock.json
  • ▸frontend-design
  • ▸pdf-reading
  • ▸react-best-practices
macbook-air— empty
~/.agents/.skill-lock.json
no skills installed
thinkpad-x1— empty
~/.agents/.skill-lock.json
no skills installed
syncs skills for
Claude CodeCursorCodexGemini CLIGitHub CopilotWindsurfZedany agent using skill-lock
03 / Why

Built the way devs already work.

01

Zero-friction sync

One command on a fresh machine restores every global skill you had elsewhere. No dotfile copy-paste, no manual reinstall.

02

GitHub-native

Auth is GitHub OAuth. Storage is a private Gist on your own account. Nothing new to trust, no new account to remember.

03

Agent-agnostic

Works with Claude Code, Cursor, Gemini CLI, Copilot — anything that uses the global skill lock at ~/.agents/.skill-lock.json.

04

Non-destructive

Sync is additive only. Local skills are never removed or overwritten. Conflict resolution stays your call.

05

No proprietary backend

There is no Quiver server holding your skill data. Gist is the source of truth; the CLI talks to it directly.

06

Open source · MIT

Read the code, run it yourself, fork it. Released under MIT — no shady terms hidden behind a free tier.

04 / Get it

Stop reinstalling skills. Start syncing them.

Quiver is free and open source. Install the CLI, run quiver login once, and your global skills follow you to every machine you sign in on.

$npm install -g usequiver