Caveman Cloud evidence review: where your LLM spend goes
Read-only audit of Caveman cost evidence — measured list-price cost, Cave Score, traces, latency, errors, routing, verified savings
- What
- Read-only audit of Caveman cost evidence — measured list-price cost, Cave Score, traces, latency, errors, routing, verified savings
- Cost
- Free
- Needs
- a Caveman Cloud account with the caveman CLI (or MCP) configured and a project selected — the skill is a read-only methodology, nothing to deploy
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Selected by Skill Harbor — short listing (the repo states no license, so no content is reproduced): @juliusbrussee's read-only review workflow for Caveman Cloud evidence — answer "where does the LLM spend go" without ever changing anything. Hard rules: keep measured provider list-price cost, inferred daily headroom, verified ledger savings and evidence cost strictly separate; never fetch payloads (metadata, timing, token counts and status are enough); never supply an organization id; cite trace ids and exact time windows. The workflow: load context (caveman_context or caveman cloud CLI), establish a baseline (caveman_report for overview/costs/score/workflows/verified_savings, caveman_plan for ranked headroom), test the leading explanation against bounded trace searches with a control cohort (never infer causality from one expensive trace), inspect representative traces, and report in a fixed shape — scope, measured cost, verified savings, inferred headroom, findings with trace ids, an "unproven" section, one next read-only check, and a proposal-only possible action. Never start, approve, cancel or roll back an experiment from this skill. Honest caveats: requires a Caveman Cloud account with the caveman CLI/MCP configured and a selected project; the evidence discipline is demanding — empty results mean no signal, not zero cost; license not stated by the source repo — short listing with a link only, nothing copied. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a Caveman Cloud account with the caveman CLI (or MCP) configured and a project selected — the skill is a read-only methodology, nothing to deploy Install "Caveman Cloud evidence review: where your LLM spend goes" for me. It gives my agent @juliusbrussee's read-only evidence-review workflow: keep measured cost, inferred headroom, verified savings and evidence cost separate; establish a baseline with caveman_report/caveman_plan; test the leading explanation against bounded trace searches with a control cohort; inspect representative traces; and report findings with trace ids, an "unproven" section and one next read-only check — never starting, approving, canceling or rolling back anything. IMPORTANT: the repo states no license — fetch from the link only, and reproduce nothing beyond the link. Repository: https://github.com/juliusbrussee/caveman/blob/main/skills/caveman-evidence-review/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "caveman-evidence-review". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. log in with `caveman login` and select a project — the agent must never guess; nothing else). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.