AGENT SKILL

caveman-internal

Internal token-compression protocol for Cavekit agent artifacts — handoff notes, artifact summaries, context bundles, review notes, status lines. NOT the user-facing /caveman skill; that one compresses assistant replies to the user. This skill compresses machine-to-machine prose so the next agent in the loop reads fewer tokens. Three intensities (lite / full / ultra) with automatic selection based on budget pressure. Used by task-builder, builder, inspector, verifier, convergence-monitor, and the stop-hook status block.

License 许可
Apache-2.0
最近更新
2026-11-11
Stars
★ 1.6k
Forks
474

01 前言 Front Matter

name
caveman-internal
description
Internal token-compression protocol for Cavekit agent artifacts — handoff notes, artifact summaries, context bundles, review notes, status lines. NOT the user-facing /caveman skill; that one compresses assistant replies to the user. This skill compresses machine-to-machine prose so the next agent in the loop reads fewer tokens. Three intensities (lite / full / ultra) with automatic selection based on budget pressure. Used by task-builder, builder, inspector, verifier, convergence-monitor, and the stop-hook status block.

02 资源文件 1

03 SKILL.md 正文

Caveman Internal Protocol

Scope

IN-scope (compress)

  • Artifact summaries written to .cavekit/artifacts/
  • Context bundles between tasks (.cavekit/context-bundles/)
  • Review notes and gap lists (non-user-facing)
  • state.md notes: field and loop-log.md entries
  • Status-block body (dashboard injected by the stop hook)
  • Inter-agent handoff memos

OUT-of-scope (never compress)

  • Source code (any language, any file)
  • Git commit messages and PR descriptions
  • Kits (specs), build sites, DESIGN.md
  • Error messages that a human will act on
  • Security warnings and deprecation notices
  • Structured findings tables (P0/P1/P2/P3, coverage matrices)
  • Regression test names and assertion messages

Compressing out-of-scope content is a bug. If a reader cannot act on a compressed artifact, regenerate it verbose and log a caveman fallback — see "Fallback protocol" below.

Intensity levels

Lite — trim the fat (~20% savings)

Professional tone. Grammar intact. Drop filler, pleasantries, hedging. Keep articles and full sentences.

Rate-limit middleware passes unit tests. Integration failed on 429 header case sensitivity. Fix in progress.

Full — default (~40% savings)

Classic caveman. Drop articles, filler, pleasantries. Fragments fine. Technical terms stay exact. Pattern: [thing] [action] [reason]. [next].

Rate-limit mw pass unit. Integration fail on 429 header case. Fixing.

Ultra — maximum grunt (~65% savings)

Telegraphic. Abbreviate common terms (DB, auth, config, req, res, fn, impl, mw, mcp). Arrow notation for causality. One-word answers when enough.

mw ok, int fail header case → fix

Automatic intensity selection

Consult the session budget ledger before writing an internal artifact:

Budget remaining Intensity
> 50 % lite
20 – 50 % full
< 20 % ultra

Override rules:

  • depth = thorough tasks clamp to lite regardless of pressure (accuracy matters more than tokens when the stakes are high).
  • phase = inspecting clamps to lite for the gap-analysis output.
  • Security-sensitive artifacts clamp to lite.
  • If the caller sets caveman_intensity explicitly in the artifact envelope, use that and skip auto-selection.

See references/budget-thresholds.md for the detailed decision table.

Fallback protocol

If a downstream reader cannot reconstruct intent from a compressed artifact:

  1. Regenerate the artifact in full prose (no compression).
  2. Append a one-line entry to state.md's "Caveman fallbacks" section:
    - 2026-04-17T12:34Z T-017 verifier fallback: artifact summary re-expanded
    
  3. If the same artifact category fails 3+ times in one session, clamp that category to lite for the rest of the session and log to state.md.

Envelope

Every compressed artifact carries a tiny header:

<!-- caveman: intensity=full version=1 -->

Readers that see this header know the body is compressed and apply the reverse-expansion grammar (re-add articles, re-expand abbreviations) when rendering for a human.

Examples

Verbose Full Ultra
"The build completed successfully after three waves." "Build complete. 3 waves." "Build ok 3w"
"All tests pass, but one test was skipped due to a missing fixture." "Tests pass. One skipped, missing fixture." "Tests ok 1 skip fx"
"The reviewer flagged two critical issues in the auth middleware." "Reviewer: 2 P0 in auth mw." "Rev 2 P0 auth mw"

Integration with the existing caveman skill

The user-facing caveman skill governs how the assistant speaks to the user during a session (answers, explanations, replies). This caveman-internal skill governs how agents write artifacts for each other. Both must be on or both off for a coherent experience, so caveman_mode = off in config also disables this skill.

04 同仓库更多 Skills

hashgraph-online
hashgraph-online/awesome-codex-plugins

migrate-to-e2e

Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for /migrate-to-e2e, "migrate our tests to e2e", "port these Maestro flows", "move our TesterArmy tests", or when a project has an e2e config and an older suite still running.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

e2e

Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

create-verification-skill

Generate a project-local verify-<app> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for /create-verification-skill, "make a verification skill for this repo", or when a project has no scripted way to prove UI behavior.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

deja-search

deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

deja-reflect

End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

revid

Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.

图像与多媒体Skill与智能体开发
★ 1.6k