--- name: caveman-evidence-review description: >- Read-only review of Caveman Cloud evidence: cost, Cave Score, workflows, traces, latency, errors, routing, savings. Use when asked what Caveman found or where LLM spend goes. title: caveman-evidence-review canonical_url: https://skilld.dev/gh/juliusbrussee/caveman/caveman-evidence-review last_updated: 2026-09-27T15:58:53.000Z --- > Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt) > **Skill from skilld.dev.** Follow the user's requested action. > If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it. > Otherwise, follow the instructions below for this session. You do not need to install anything. > > If the user asked to install this Skill, run `npx skilld install juliusbrussee/caveman/caveman-evidence-review`. Install writes the Skill files into the project, so every session loads them. > > ## Fork workflow > > A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation. > 1. Check `./skills/caveman-evidence-review`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target. > 2. Read [source metadata](https://skilld.dev/api/v1/skills/juliusbrussee/caveman/caveman-evidence-review) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit. > 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call: > > ```sh > git init --quiet "$temporary_dir" > git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit" > git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD > ``` > > Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop. > 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/caveman-evidence-review`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md. > Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical. > 5. In the project root, run `skilld install ./skills/caveman-evidence-review --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/caveman-evidence-review --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure. > 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks. # 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 1. Keep these buckets separate: - measured provider-complete list-price cost; - `inferred` daily headroom; - `verified` ledger savings; - evidence cost. Never add or relabel them. 2. 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. 3. Scope every read to the project selected by Caveman context. Never supply an organization id. 4. Empty results are evidence of no current signal, not zero cost or zero risk. 5. Cite trace ids and exact time windows used. Do not claim a cause from an aggregate alone. ## Step 1 — Load context Prefer MCP: ```text caveman_context {} ``` CLI fallback: ```bash 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. ## Step 2 — Establish baseline Use `caveman_report` for: - `overview` - `costs` - `score` - `workflows` - `verified_savings` Then use `caveman_plan` for ranked daily headroom. If question is narrow, skip unrelated reports. Read shortest set that can answer it. CLI fallback: ```bash caveman cloud costs caveman cloud score caveman cloud plan --json ``` State report window and basis before interpreting direction. ## Step 3 — Test the leading explanation with traces Use `caveman_trace_search`. Choose a bounded window and closed filters: workflow, agent, model, provider, error code, runtime mode, cache status, optimization id, status class, token/cost/latency bounds, compression, or monitor verdict. Useful groupings: - `workflow` — find jobs driving cost or failures; - `model` — compare model mix; - `session` — isolate retry or loop behavior; - ungrouped — identify exact traces. Compare a suspect cohort with a control cohort or earlier bounded window. Do not infer causality from one expensive trace. CLI fallback: ```bash caveman cloud traces search \ --workflow \ --from \ --to \ --sort total_cost_usd \ --dir desc \ --limit 25 ``` ## Step 4 — Inspect representative traces Call `caveman_trace_get` for a small number of high-signal trace ids. Inspect request and span metadata, latency, status, token counts, cache state, applied optimizers, and model route. Keep payload retrieval off. CLI fallback: ```bash caveman cloud traces show --spans ``` ## Step 5 — Report Use this shape: ```text ## Caveman evidence review Scope: · to Measured cost: Verified savings: Inferred headroom: Findings: 1. — — traces 2. — — traces Unproven: - Next read-only check: - Possible action: - ``` If data is missing, name missing signal and stop at strongest supported statement. Never turn a catalog subtotal into an invoice or an experiment result into verified savings.