caveman-manage

Inspect Caveman Cloud experiment lifecycles and block unsafe lifecycle mutations.

1|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/tkogut/agents-os-core --skill caveman-manage-tkogut
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: caveman-manage
Source: https://github.com/tkogut/agents-os-core/tree/main/vault/.agents/skills/caveman-manage
Command: npx skills add https://github.com/tkogut/agents-os-core --skill caveman-manage-tkogut

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing eval-gated experiments in Caveman Cloud requires strict evidence review before any lifecycle change, but the current control API cannot atomically enforce lifecycle transitions and evidence gates. This Skill ensures every start, approve, cancel, promote, or rollback request is handled as a read-only, fail-closed review so unsafe or premature mutations are never executed. ## Core Features & Use Cases - Evidence-Based Review: Reads experiment state, results, sample sizes, quality scores, and guardrails (latency, error, cost, retry, drop, escalation) via MCP tools or the caveman CLI before recommending anything. - Fail-Closed Safety Gates: Blocks approval when results are pending, guardrails are missing, or evidence reports a breach, and treats unknown states and server errors as failures with exact cave_snake_code reporting. - Mutation Blocking: Refuses to execute lifecycle commands even after user approval, since agent-generatable action strings are not proof of human intent and the server does not yet enforce transitions atomically. - Use Case: A user asks to approve experiment 7f after seeing promising lift. The Skill reads the experiment and results, finds a guardrail report missing, states evidence is incomplete, and blocks the approval instead of promoting unverified changes. ## Quick Start Ask the agent to review the current state and results of a Caveman experiment and recommend whether it can be started, approved, cancelled, or rolled back.

Frequently Asked Questions about caveman-manage

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

FAQPage Schema
How do I review a Caveman experiment before approving it?▼

Read the experiment state and results using caveman_experiment_get with actions get and results, or the CLI commands caveman cloud experiments show and results. Then evaluate sample sizes, quality scores, and all configured guardrails before proposing any action.

Can the agent approve or start a Caveman experiment directly?▼

No. The current control API does not enforce lifecycle transitions and evidence gates atomically, so agent surfaces expose reads only. The Skill proposes one supported action but blocks execution until server-authoritative gates ship.

What happens when experiment evidence is incomplete or pending?▼

The Skill reports evidence incomplete and refuses to propose approval. Absence of required fields is never treated as a pass, and unknown states or server errors fail closed with the exact cave_snake_code reported.

Does experiment lift count as verified savings?▼

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

Why does a rollback request return cave_not_implemented?▼

Current deployments may honestly reject rollback requests with cave_not_implemented because the server-side policy path is not fully shipped. The Skill reports this response accurately and never describes it as a completed rollback.