setup caliber

AI Community

Skill notes

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

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): Set CALIBER="caliber". If npm fails (permissions, no sudo, etc.), fall back to npx: If npx works → Set CALIBER="npx @rely-ai/caliber". This works but adds ~500ms per invocation.

Step 2: Check if pre-commit hook is installed

If HOOK_ACTIVE → Tell the user: "Pre-commit hook is active — configs sync on every commit." Move to Step 3. If NO_HOOK → Tell the user: "I'll install the pre-commit hook so your agent configs sync automatically on every commit."

Step 3: Detect agents and check if configs exist

First, detect which coding agents are configured in this project: If no agents are detected, ask the user which coding agents they use (Claude Code, Cursor, Codex, GitHub Copilot). Build the agent list from their answer as a comma-separated string (e.g. "claude,cursor"). Then check if agent configs exist: If configs exist for the detected agents → Tell the user which configs are present. Move to Step 4.

Step 4: Check if configs are fresh

If score is 80+ → Tell the user: "Your configs are in good shape (score: X/100)." If score is below 80 → Tell the user: "Your configs could be improved (score: X/100). Want me to run a refresh?" If yes:

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Required · OpenAI / Anthropic / GitHub
Operating systems
Linux
Runtime requirements
Node.js >=20
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Check if Caliber is 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): Set `CALIBER="caliber"`. If npm fails (permissions, no sudo, etc.), fall back to npx: If npx works → Set `CALIBER="npx @rely-ai/caliber"`. This works but adds ~500ms per invocation.

02
Step 2: Check if pre-commit hook is installed

If HOOK_ACTIVE → Tell the user: "Pre-commit hook is active — configs sync on every commit." Move to Step 3. If NO_HOOK → Tell the user: "I'll install the pre-commit hook so your agent configs sync automatically on every commit."

03
Step 3: Detect agents and check if configs exist

First, detect which coding agents are configured in this project: If no agents are detected, ask the user which coding agents they use (Claude Code, Cursor, Codex, GitHub Copilot). Build the agent list from their answer as a comma-separated string (e.g. "claude,cursor"). Then check if agent configs exist: If configs exist for the detected agents → Tell the user which configs are present. Move to Step 4.

04
Step 4: Check if configs are fresh

If score is 80+ → Tell the user: "Your configs are in good shape (score: X/100)." If score is below 80 → Tell the user: "Your configs could be improved (score: X/100). Want me to run a refresh?" If yes:

05
Step 5: Ask about team setup

Ask the user: "Are you setting up for yourself only, or for your team too?" If solo → Continue with solo setup: Check if session learning is enabled: If learning is already enabled → note it in the summary. If not enabled → ask the user: "Caliber can learn from your coding sessions — when you correct a mistake or fix a pattern, it remembers for next time. Enable session learning?"

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.