CtrlK
BlogDocsLog inGet started
Tessl Logo

cavecrew

When to delegate to `cavecrew-investigator` (locate code), `cavecrew-builder` (1-2 file edit) or `cavecrew-reviewer` (diff review) instead of working inline or using `Explore`. Their output is compressed, so main context lasts longer.

68

Quality

81%

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

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

The body is a tightly structured, action-first reference with executable output contracts, explicit chaining workflows, and built-in validation via terminal tokens. It is an exemplar of token-efficient, actionable skill content with only minor conciseness headroom.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, with tight output contracts and a terse comparison table; the "Why this exists" section is slightly explanatory and could be trimmed, keeping it just below 5.

4 / 5

Actionability

Fully concrete, copy-ready output contracts with exact formats ("path:line — symbol — short note", "verified: <re-read OK | mismatch @ path:line>") and enumerated terminal tokens cover the common cases precisely.

5 / 5

Workflow Clarity

The locate→fix→verify chaining pattern is explicitly sequenced, and the builder's terminal-first tokens ("too-big.", "needs-confirm.", "ambiguous.", "regressed.") act as explicit validation checkpoints with feedback loops for recovery.

5 / 5

Progressive Disclosure

Self-contained with no bundle files and well-organized sections (when-to-use, output contracts, chaining, anti-patterns); per the simple-skill note, a sub-50-line skill with no external references can score 5 on structure alone.

5 / 5

Total

19

/

20

Passed

Description

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

The description is specific, well-scoped, and third-person, clearly establishing a distinct niche for compressed-output subagent delegation. Its main weakness is trigger-term coverage, which uses a few natural phrases but misses common synonyms users would actually say.

Suggestions

Add concrete user-facing trigger phrases (e.g. "Use when the user asks to find, search, or locate code; make a small edit; or review a diff") to lift trigger_term_quality and completeness toward 5.

Include common synonyms for each agent's job ("search/find definitions", "small/surgical edit", "review/audit diff") so natural user phrasings map to the right subagent.

Consider naming file extensions or concrete nouns (e.g. "diff review", "branch review") to broaden distinctiveness anchors.

DimensionReasoningScore

Specificity

Names three concrete agents and their concrete actions ("locate code", "1-2 file edit", "diff review"), with only minor coverage gaps; not a full 5 because it doesn't enumerate all capabilities of each agent.

4 / 5

Completeness

Both what (delegate to one of three specific agents) and when ("instead of working inline or using Explore") are present and third-person; the "when" could be more explicit with concrete trigger phrases, so it is above 3 but not a 5.

4 / 5

Trigger Term Quality

Some natural terms like "locate code", "diff review", and "edit" appear, but common user phrasings/synonyms (e.g. "search", "find", "refactor") are missing, so it lands at the midpoint rather than a strong 4.

3 / 5

Distinctiveness Conflict Risk

The compressed-output subagent niche is specific and clearly differentiated from vanilla Explore/edit/reviewer defaults, giving it a distinct trigger profile with minimal conflict risk.

5 / 5

Total

16

/

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.