← ClaudeAtlas

lifesight-calibrationlisted

Use the FIRST time you operate a Lifesight workspace, when no lifesight-workspace-profile exists yet, or when the user asks to "set up", "calibrate", "onboard", "configure for my account", or "recalibrate" Lifesight. Also use when the active workspace changed, when channel names or models look unfamiliar, or when the user wants to set guardrails (iROAS floor, max per-channel change, locked channels). Produces the per-workspace profile that every other Lifesight skill reads.
lifesight/lifesight · ★ 0 · AI & Automation · score 75
Install: claude install-skill lifesight/lifesight
# Lifesight Calibration — Learn the Workspace Once The Lifesight skills are **universal** — the same files ship to every customer. Nothing about a specific account is baked into them. This skill is how a universal skill set adapts to one account: it inspects the live workspace **once** and writes a small `lifesight-workspace-profile` that the router, core, rendering, and every persona spoke then read. Skills stay universal; the profile is the only per-customer artifact. **Follow `lifesight-core` operating rules throughout** (one heavy call per turn, clean errors, no leaks). ## When to run - No `lifesight-workspace-profile` exists yet for the active workspace. - The user explicitly asks to set up / calibrate / recalibrate. - The active workspace just changed (the profile is per-workspace). - Channels or models in a response don't match the profile (drift — refresh it). If a current profile already exists and matches the active workspace, **don't re-run** — just use it. ## What to inspect (cheap calls only) All of these are light tools — no flood risk. Run them in this order: 1. **Confirm the workspace.** `list_workspaces` → note the active workspace name/id. 2. **Discover models.** `list_models` → capture every model (name, KPI) and which is the default/recommended. If zero models, stop and tell the user to set a default scenario in the platform UI — calibration can't complete without one. 3. **Learn the channels + spend scale in one call.** `get_current_budget(d