CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

caveman-review

Ultra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says "review this PR", "code review", "review the diff", "/review", or invokes /caveman-review. Auto-triggers when reviewing pull requests.

76

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

The canonical home for this skill is caveman-review in JuliusBrussee/caveman

SKILL.md
Quality
Evals
Security

Quality

Content

100%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.

An exemplary lean skill body: every section adds non-obvious, directive guidance, with concrete formats, a severity taxonomy, illustrative ❌/✅ pairs, explicit exceptions, and clear boundaries. Nothing is padded and nothing Claude already knows is re-explained.

DimensionReasoningScore

Conciseness

The ~45-line body is entirely directive — format template, severity legend, drop/keep lists, examples — with zero explanation of concepts Claude already knows. The verbose ❌ quotes are deliberate before/after illustrations that earn their tokens; every token adds non-obvious guidance, matching anchor 5.

5 / 5

Actionability

Fully executable guidance: the exact template `L<line>: <problem>. <fix>.` (with the multi-file variant), four defined severity prefixes, literal hedging phrases to drop, and four ❌/✅ example pairs covering the common cases. Copy-paste-ready patterns with no gaps.

5 / 5

Workflow Clarity

A simple single-purpose skill whose one action (write terse review comments) is unambiguous. Exception handling is explicit (Auto-Clarity lists when to drop terse mode) and exit conditions are stated ("stop caveman-review... revert to verbose review style"); no destructive or batch operations exist, so no validation cap applies.

5 / 5

Progressive Disclosure

Under 50 lines with no need for external references (no references/, scripts/, or assets/ exist), and content is well-organized into Rules, Examples, Auto-Clarity, and Boundaries sections — satisfying the simple-skill condition for a top score.

5 / 5

Total

20

/

20

Passed

Description

91%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 description: third-person voice, explicit what and when with concrete trigger phrases, and a specific output-format statement. The only weaknesses are minor coverage gaps (severity prefixes, auto-clarity fallback) and trigger terms shared with generic code-review skills.

DimensionReasoningScore

Specificity

"Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix" lists several specific actions plus a concrete output format. Minor gaps remain — severity prefixes and the auto-clarity exception are unmentioned — so it sits at anchor 4 rather than the comprehensive coverage of anchor 5.

4 / 5

Completeness

Explicitly answers both what ("Ultra-compressed code review comments... Each comment is one line: location, problem, fix") and when ("Use when user says 'review this PR', 'code review'...") with concrete trigger phrases, exactly matching the anchor-5 example pattern.

5 / 5

Trigger Term Quality

Natural trigger phrases are comprehensively covered: "review this PR", "code review", "review the diff", "/review", "invokes /caveman-review", and "Auto-triggers when reviewing pull requests" — synonyms and slash-command variants included, matching anchor 5.

5 / 5

Distinctiveness Conflict Risk

The ultra-compressed one-line niche is distinct, but the triggers "code review" and "review this PR" are generic terms any standard review skill would also match — minor overlap risk with closely related skills (anchor 4), not the minimal-conflict clarity of anchor 5.

4 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

masweb/waxp-vuebo

Path

.agents/skills/caveman-review/SKILL.md

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.