caveman--caveman-manage

Inspect Caveman Cloud experiment lifecycles and block unsafe lifecycle mutations.

Updated Dec 3, 2025
One-click install
npx skills add https://github.com/hhenrichsen/dots --skill caveman-caveman-manage-hhenrichsen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: caveman--caveman-manage
Source: https://github.com/hhenrichsen/dots/tree/main/dot_skills/caveman/caveman-manage
Command: npx skills add https://github.com/hhenrichsen/dots --skill caveman-caveman-manage-hhenrichsen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing eval-gated experiments in Caveman Cloud requires strict evidence checks before any lifecycle change, and current agent surfaces are read-only because the control API does not yet enforce lifecycle transitions and evidence gates atomically. This Skill ensures every start, approve, cancel, promote, or rollback request is evaluated against complete evidence and blocked when unsafe. ## Core Features & Use Cases - Evidence-Based Review: Reads experiment state, sample sizes, quality results, guardrails, and cost evidence via MCP or CLI before recommending any action. - Fail-Closed Safety Gates: Refuses approval when results are pending, guardrails are absent, or evidence reports a breach, and never converts experiment lift into verified savings. - Mutation Blocking: Never executes lifecycle mutations, even after user approval, because agent-generatable action strings are not proof of human intent. - Use Case: A user asks to approve experiment 7f after seeing positive lift. The Skill reads the experiment detail and results, finds a missing latency guardrail, reports "evidence incomplete", and blocks the approval instead of executing it. ## Quick Start Ask the assistant to review Caveman experiment 7f and recommend whether it should be approved, started, cancelled, or rolled back.

Frequently Asked Questions about caveman--caveman-manage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I approve a Caveman Cloud experiment safely?▼

Approval requires complete passing evidence: quality or eval results, all configured guardrails, and a safety class the current role may approve. The Skill reads experiment detail and results first, then proposes approve only when every required field is present and passing.

How to check experiment results and guardrails in Caveman?▼

Use the caveman_experiment_get MCP tool with action results, or the CLI command caveman cloud experiments results <id>. The Skill reports sample sizes, quality results, latency, error, cost, retry, drop, and escalation guardrails when present.

Can the agent execute experiment lifecycle changes directly?▼

No. The current agent MCP surface is intentionally read-only because the control API does not yet enforce lifecycle transitions and evidence gates atomically. The Skill blocks all mutations and explains that execution waits for server-authoritative gates.

Why was my experiment approval request blocked?▼

Approvals are blocked when results are pending, required guardrails are absent, or evidence reports a breach. Absence of a required field is treated as incomplete evidence, never as a pass, and unknown states fail closed.

Does experiment lift count as verified savings?▼

No. Experiment lift is never converted into verified_savings. Only active real traffic plus provider-causal, provider-complete signed ledger evidence can record verified savings.

What happens if a rollback returns cave_not_implemented?▼

Current deployments may honestly reject rollback requests with cave_not_implemented. The Skill reports the exact cave_snake_code and never describes that response as a successful rollback.