setup-caliber SKILL.md skillA
setup-caliber from caliber-ai-org/ai-setup is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add caliber-ai-org/ai-setup/setup-caliber@git:20260329.8cf93fdPins git:20260329.8cf93fd in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- caliber-ai-org/ai-setup
- Path
.agents/skills/setup-caliber/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260329.8cf93fd, committed Mar 29, 2026
- Size
- 7,834 bytes
- Repository stars
- 1,316
- License
- MIT
Sets up Caliber for automatic AI agent context sync. Installs pre-commit hooks so CLAUDE.md, Cursor rules, and Copilot instructions update automatically on every commit. Use when Caliber hooks are not yet installed or when the user asks about keeping agent configs in sync.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Setup Caliber Dynamic onboarding for Caliber — automatic AI agent context sync. Run all diagnostic steps below on every invocation to determine what's already set up and what still needs to be done. ## Instructions Run these checks in order. For each step, check the current state first, then only act if something is missing. ### Step 1: Check if Caliber is installed ```bash command -v caliber >/dev/null 2>&1 && caliber --version || echo "NOT_INSTALLED" ``` - If a version prints → Caliber is installed globally. Set `CALIBER="caliber"` and move to Step 2. - If NOT_INSTALLED → Install it globally (faster for daily use since the pre-commit hook runs on every commit): ```bash npm install -g @rely-ai/caliber ``` Set `CALIBER="caliber"`. If npm fails (permissions, no sudo, etc.), fall back to npx: ```bash npx @rely-ai/caliber --version 2>/dev/null || echo "NO_NODE" ``` - If npx works → Set `CALIBER="npx @rely-ai/caliber"`. This works but adds ~500ms per invocation. - If NO_NODE → Tell the user: "Caliber requires Node.js >= 20. Install Node first, then run /setup-caliber again." Stop here. ### Step 2: Check if pre-commit hook is installed ```bash …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_5ek5qwb4vyinkkep/0d5a028b72e48a24c3b8f540f6e575077c2e8868d658ae739e5ab56ba8420fc8.json
Then /plugin install setup-caliber@markdownregistry-5ek5qwb4vyinkkep in Claude Code. It installs git:20260329.8cf93fd, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add caliber-ai-org/ai-setup/setup-caliber@sha256:0d5a028b72e48a24The line at the top of this page pins the label git:20260329.8cf93fd, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_5ek5qwb4vyinkkep)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in caliber-ai-org/ai-setup/setup-caliber since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of setup-caliber from somewhere else? Ask it: where did my setup-caliber come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Mar 29, 2026.
Watch this file (sign in, one email per new version)
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/setup-caliber/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7834 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
caliber-ai-org/ai-setup · 1,316 stars · license MIT · pushed 2026-09-24 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_5ek5qwb4vyinkkep GET https://markdownregistry.com/api/v1/resolve?ref=caliber-ai-org/ai-setup/setup-caliber GET https://markdownregistry.com/api/v1/blob/0d5a028b72e48a24c3b8f540f6e575077c2e8868d658ae739e5ab56ba8420fc8
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from caliber-ai-org/ai-setup
Every file in caliber-ai-org/ai-setup
Other files named setup-caliber
Browse by kind, by grade A, or by owner.
Kept in .agents/skills, the folder Codex reads. More agent skills for Codex.