caveman-evidence-review
Review Caveman Cloud evidence read-only: costs, Cave Score, Cave Plan, workflows, traces, latency, errors, compression, routing, and verified savings. Use when the user asks what Caveman found, where LLM spend goes, why cost or quality changed, which workflows need attention, or asks for a trace or analytics review. Prefer Caveman MCP tools; fall back to CLI JSON.
- License 许可
- MIT
- 最近更新
- 2026-08-19
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- description
- Review Caveman Cloud evidence read-only: costs, Cave Score, Cave Plan, workflows, traces, latency, errors, compression, routing, and verified savings. Use when the user asks what Caveman found, where LLM spend goes, why cost or quality changed, which workflows need attention, or asks for a trace or analytics review. Prefer Caveman MCP tools; fall back to CLI JSON.
03 SKILL.md 正文
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.
Step 2 — Establish baseline
Use caveman_report for:
overviewcostsscoreworkflowsverified_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:
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:
caveman cloud traces search \
--workflow <slug> \
--from <RFC3339> \
--to <RFC3339> \
--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:
caveman cloud traces show <trace-id> --spans
Step 5 — Report
Use this shape:
## Caveman evidence review
Scope: <project> · <from> to <to>
Measured cost: <value and basis>
Verified savings: <ledger value, kept separate>
Inferred headroom: <per-day band, kept separate>
Findings:
1. <finding> — <aggregate evidence> — traces <ids>
2. <finding> — <aggregate evidence> — traces <ids>
Unproven:
- <plausible explanation lacking a control, trace, or eval>
Next read-only check:
- <one bounded query>
Possible action:
- <proposal only; use caveman-manage for read-only lifecycle review and safety gate>
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.
04 同仓库更多 Skills
youtube-transcript
Extract transcripts from YouTube videos. Use when the user asks for a transcript, subtitles, or captions of a YouTube video and provides a YouTube URL (youtube.com/watch?v=, youtu.be/, or similar). Supports output with or without timestamps.
youtube-thumbnail-design
YouTube thumbnail design with specific dimensions, contrast rules, and mobile preview optimization. Covers safe zones, text placement, face expression psychology, and A/B testing. Use for: YouTube thumbnails, video cover images, click-through optimization. Triggers: youtube thumbnail, thumbnail design, video thumbnail, click through rate, ctr optimization, youtube cover, video cover image, thumbnail maker, thumbnail tips, youtube design, video preview image
youtube-short-maker
Make YouTube Shorts that hold attention with Pexo — vertical 9:16, fast-paced, hook in the first 3 seconds. Describe your topic and Pexo writes the script, generates the shots, picks the models, and assembles a finished Short with music and captions. Use for YouTube Shorts: "youtube short", "make a youtube short", "shorts video", "short-form video". NOT for long-form or landscape video.
xcode-project-setup
Safely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill whenever an iOS project needs dependencies installed (e.g. Firebase, Alamofire).
x402
Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — "just use it" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing touches your codebase) or "build it in" (install the SDK and write the key + code into your project). Walks through wallet setup, funding, .env, and a ~$1 test run. Use when the user asks about x402, pay-per-use, USDC payments, or wants Browser Use Cloud without an API key. For the free-tier signup (reverse-CAPTCHA → API key), use `browser-use cloud signup` or the `cloud` skill instead.
x-twitter-scraper
Build GitHub Copilot workflows with Xquik X API SDKs, REST endpoints, hosted Apify Actor runs, MCP tools, TweetClaw OpenClaw plugin installs, signed webhooks, tweet search, user lookup, follower exports, media actions, and agent automation.