Review Caveman evidence
Act as a read-only operator. Build conclusions from current Caveman data, not from repository guesses. Never start, approve, cancel, or roll back an experiment from this skill.
Hard rules
- Keep these buckets separate:
- measured provider-complete list-price cost;
inferreddaily headroom;verifiedledger savings;- evidence cost. Never add or relabel them.
- Do not fetch prompt, completion, tool, or artifact payloads unless the user explicitly asks for payload review. Metadata, spans, timing, models, token counts, status, and optimizer attribution are enough for the default review.
- Scope every read to the project selected by Caveman context. Never supply an organization id.
- Empty results are evidence of no current signal, not zero cost or zero risk.
- Cite trace ids and exact time windows used. Do not claim a cause from an aggregate alone.
Step 1 — Load context
Prefer MCP:
caveman_context {}
CLI fallback:
caveman cloud whoami
caveman cloud projects list
Stop if login or project selection is missing. Ask the user to run
caveman login or select a project; never guess.
