setup-caliber
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.
npx skills add caliber-ai-org/ai-setup --skill setup-caliber --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 grep -q "caliber" .git/hooks/pre-commit 2
- Instructions
- Step 1: Check if Caliber is installed
- Step 2: Check if pre-commit hook is installed
- Step 3: Detect agents and check if configs exist
- Step 4: Check if configs are fresh
- Step 5: Ask about team setup
- Summary
- When to trigger
- When NOT to trigger
command -v caliber >/dev/null 2>&1 && caliber --version || echo "NOT_INSTALLED"
npm install -g @rely-ai/caliber
npx @rely-ai/caliber --version 2>/dev/null || echo "NO_NODE"
grep -q "caliber" .git/hooks/pre-commit 2>/dev/null && echo "HOOK_ACTIVE" || echo "NO_HOOK"
echo "DETECTED_AGENTS=${AGENTS:-none}"
echo "CLAUDE_MD=$([ -f CLAUDE.md ] && echo exists || echo missing)"
echo "CURSOR_RULES=$([ -d .cursor/rules ] && ls .cursor/rules/*.mdc 2>/dev/null | wc -l | tr -d ' ' || echo 0)"
echo "AGENTS_MD=$([ -f AGENTS.md ] && echo exists || echo missing)"
echo "COPILOT=$([ -f .github/copilot-instructions.md ] && echo exists || echo missing)"
command -v gh >/dev/null 2>&1 && echo "GH_AVAILABLE" || echo "NO_GH"What does the setup-caliber skill do?
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.
How do I install it?
Run `npx skills add caliber-ai-org/ai-setup --skill setup-caliber --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From caliber-ai-org/ai-setup, a repository with 1,235 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.