CtrlK
BlogDocsLog inGet started
Tessl Logo

caveman-learn

Act on a Caveman learn report - review the ranked token sinks, apply cost-lowering fixes with per-edit consent, and report what those fixes returned. Use when asked to lower an agent's token cost, what caveman has saved, to trim a heavy CLAUDE.md, or to offload re-pasted context into cavemem.

76

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tightly written, highly actionable skill body with strong sequencing and validation for destructive consent-gated edits. Minor conciseness redundancy and the absence of any external reference structure keep it just short of top marks.

Suggestions

Consolidate the repeated 'never make the agent dumber', consent, and 'never claim an unmeasured saving' rules into a single binding-rules section referenced once to reduce restatement.

Consider extracting the savings-reporting rungs and attribution rules into a references/ file to lighten the inline body while keeping the main workflow prominent.

DimensionReasoningScore

Conciseness

Dense and rule-packed with no padding about concepts Claude already knows, but several rules are restated multiple times ('never make the agent dumber', consent, never claim unmeasured savings), so a few tokens could still be trimmed.

4 / 5

Actionability

Fully executable guidance throughout — concrete commands with flags such as 'caveman learn report --json', 'caveman learn apply <sink_id> --dry-run', 'caveman mem remember -- "<the real block>"' cover the common cases copy-paste ready.

5 / 5

Workflow Clarity

Sequenced by fix class (REDUCIBLE, RECURRING_CONTEXT, SKILL_DISTILLATION) with explicit validation checkpoints — the net-token-negative gate, sha256 block verification, recall-path guard, and revert paths — plus feedback loops for these destructive edits.

5 / 5

Progressive Disclosure

No bundle files exist and the skill is a single well-organized SKILL.md with clear sections and no nested references; structure is good, though the reporting/savings block is dense inline content that could be split out.

4 / 5

Total

18

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that concretely states what the skill does and when to use it with natural trigger phrasing and a distinct niche. No vague fluff or over-claims present.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'review the ranked token sinks', 'apply cost-lowering fixes with per-edit consent', 'report what those fixes returned' — giving comprehensive coverage of the skill's behavior.

5 / 5

Completeness

Explicitly answers both what (act on the report, review sinks, apply fixes, report results) and when via a clear 'Use when...' clause with concrete trigger scenarios.

5 / 5

Trigger Term Quality

Includes natural phrases a user would actually say — 'lower an agent's token cost', 'what caveman has saved', 'trim a heavy CLAUDE.md', 'offload re-pasted context into cavemem' — with strong synonym coverage.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (caveman learn reports, CLAUDE.md trimming, cavemem offload) with distinct, product-specific triggers that minimize conflict with other skills.

5 / 5

Total

20

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
JuliusBrussee/caveman
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.