caveman-help

Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

100%Weight 40%Scale 1-3

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

A tightly written, fully self-contained reference card: lean tables, copy-paste config examples, and a clear single action with explicit resolution order. It exemplifies brevity and actionability for a simple skill.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: short tables, fragments like 'Mode stick until changed or session end', and no padding or explanation of concepts Claude already knows.	3 / 3
Actionability	It provides concrete, executable guidance — exact triggers in every row, a copy-paste bash export, an example JSON config, and a concrete PR-comment example 'L42: bug: user null. Add guard.'	3 / 3
Workflow Clarity	This is a simple, single-task reference skill: the single action ('Display this reference card when invoked') is unambiguous, and configuration resolution is explicitly ordered (env var > config file > full).	3 / 3
Progressive Disclosure	Under 50 lines with no external bundle files needed; it is a self-contained, well-organized card with clearly labeled sections, matching the simple-skill exception for a top score.	3 / 3
	Total	12 / 12 Passed

Description

90%Weight 40%Scale 1-3

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 concise, well-triggered description that clearly answers both what it does and when to use it. The only gap is that specificity lists a single action rather than multiple concrete capabilities.

Suggestions

Enumerate a couple of concrete capabilities in the description (e.g., 'Lists all modes, skills, triggers, and configuration options') to lift specificity from domain-and-action to multiple concrete actions.

Dimension	Reasoning	Score
Specificity	The description names the domain ('all caveman modes, skills, and commands') and the concrete action of displaying a reference card, but it does not enumerate multiple distinct capabilities — it lists one action (display a card) plus what is covered.	2 / 3
Completeness	It states both what it does ('Quick-reference card for all caveman modes, skills, and commands') and when to use it ('One-shot display, not a persistent mode. Trigger: ...') with explicit trigger guidance.	3 / 3
Trigger Term Quality	It gives strong natural trigger coverage — '/caveman-help', 'caveman help', 'what caveman commands', 'how do I use caveman' — which are exactly the phrases a user would say.	3 / 3
Distinctiveness Conflict Risk	The 'caveman' niche and explicit '/caveman-help' trigger are distinct from other skills and unlikely to fire for the wrong skill.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

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: JuliusBrussee/caveman
Path: skills/caveman-help/SKILL.md
Commit: ec83e5b

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.