agent skill library · a protocol, not a platform

One protocol.
Every agent.

Install Sieve in one command. It reads the same in Claude Code, Codex, and Cursor, and 20 more agents besides. The rules live in plain files you own, not in one vendor’s memory.

terminal
$ npx sievekit initcopy AGENTS.md copy sieve.index.json copy templates seed PROGRESS.md seed HISTORY.jsonl seed PROPOSED.md seed STALE.md seed staging/README.md A couple of questions to pick the right skills. Press Enter to skip any of them. write CLAUDE.md (Claude Code) write .cursor/rules/sieve.mdc (Cursor) write .github/copilot-instructions.md (GitHub Copilot) ... Sieve is ready. Open your coding agent and describe what you want to build.

Two short questions. Then it pulls only the skills that fit from the registry, not the whole catalog. No registry? It falls back to the full bundled set on its own.

Stays honest over time

A dashboard ships with the toolkit too. No account, no telemetry, self-hostable. Catalog health, activity, skill usage. On the command line, the same report:

terminal
$ sieve checkCatalog check (staleness window: 90 days) Skills: 9 total none past the staleness window. Growth loop inputs: PROPOSED.md: 0 pending proposal(s) STALE.md: 0 pending flag(s) Catalog is healthy. Nothing to triage.

A report, not a mutation. Run it on a cadence. Triage what it flags yourself.

Why not just paste rules into every tool?

The alternative is doing this by hand, per agent, forever. Or trusting each vendor’s own memory feature, and relearning it every time you switch tools.

SieveHand-copied rulesVendor-native memory
Works the same across agentsone AGENTS.mdcopy/paste per toollocked to one vendor
Plain files you ownyesyesvendor-held state
Skills fit the project, not everythingregistry-recommended shortlistall or nothing, by handno scoped-skill concept
Catalog health you can checksieve checknobody's tracking itopaque
Portable if you switch agentsyes, by designstart overstart over

Reads natively, or bridges in one line

AGENTS.md is read natively by most of these. For the rest, sieve bridge writes a thin pointer file back to it. Never a second copy of the rules.

Claude CodeCodexCursorGitHub CopilotGemini CLIAiderWindsurfZed+ 20 more

How it stays honest

One command, tailored skills

Two short questions: new idea or existing project, any focus areas. Only the skills that fit get installed, plus the always-on guardrails. Not the whole catalog.

One protocol, every agent

AGENTS.md is the single source of truth. sieve bridge writes thin pointer files for the rest. You never maintain the same rules twice.

Six-pillar catalog

Planning, testing, review, debugging, verification, maintenance. Every skill has a clear job. The catalog stays legible as it grows.

Grows by use, not by design

Skills are proposed, validated, and promoted as real work surfaces them. sieve check keeps the catalog honest over time.

Start in one command

No account, no server round-trip required, no lock-in.

terminal
$ npx sievekit init
MIT licensed · a plain, file-based layer you own.