Caveman Manage
Inspect Caveman Cloud experiment lifecycles and block unsafe execution — eval-gated, read-only by default
- What
- Inspect Caveman Cloud experiment lifecycles and block unsafe execution — eval-gated, read-only by default
- Cost
- Free
- Needs
- a Caveman Cloud account with a logged-in identity; the Caveman MCP server or CLI; an experiment to inspect
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — the Caveman experiment-lifecycle skill: inspect Caveman Cloud experiments (project, state, results) via MCP or CLI, evaluate the evidence, then report one supported recommendation or block. Hard gates: never approve an experiment with pending results or missing guardrails, never convert lift into "verified savings" without provider-causal ledger evidence, never execute a lifecycle mutation even after user approval — unknown states fail closed. By @juliusbrussee, listed here with credit to its creator. Honest caveats: read-and-recommend only — the skill deliberately refuses to perform lifecycle changes; requires a logged-in Caveman identity and the MCP/CLI available. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Caveman Manage is a free listing for the Caveman experiment-lifecycle skill, inspecting Caveman Cloud experiments via MCP or CLI. It evaluates the evidence, then reports one supported recommendation or blocks, with hard safety gates. It never approves an experiment with pending results or missing guardrails, never converts lift into verified savings without causal ledger evidence, and never executes lifecycle mutations.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 2e08b91Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a Caveman Cloud account with a logged-in identity; the Caveman MCP server or CLI; an experiment to inspect Install "Caveman Manage" for me. Inspect Caveman Cloud experiment lifecycles and block unsafe execution — eval-gated, read-only by default Repository: https://github.com/juliusbrussee/caveman Pinned version: install the code at commit 2e08b9177c07bb7249a8a2d1a6758e5db281d002 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file for the juliusbrussee-caveman-manage skill from the repository into a temporary folder 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, credentials only via the secure vault, allowed hosts declared in the SKILL.md. 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 "juliusbrussee-caveman-manage". 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. any accounts, API keys, or CLI tools mentioned in the prerequisites above). 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. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 2e08b91 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026 · Observed during the install test: registry.npmjs.org
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.