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

87%

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

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

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.

A tight, well-structured reference-card skill that excels at conciseness and organization with concrete config guidance. Actionability is strong but stops just short of fully copy-paste-ready across all paths.

Dimension	Reasoning	Score
Conciseness	Lean tables and terse prose ('Mode stick until changed or session end.') with no padding or explanation of concepts Claude already knows; every token earns its place per the top anchor.	5 / 5
Actionability	Concrete, executable guidance throughout — exact slash triggers, what each mode changes, copy-paste config commands ('export CAVEMAN_DEFAULT_MODE=ultra', the JSON config), and deactivate phrases — with only minor gaps, fitting 'mostly executable guidance' rather than the fully copy-paste-ready 5.	4 / 5
Workflow Clarity	Simple single-purpose skill whose one action is unambiguous ('Display this reference card when invoked. One-shot — do NOT change mode, write flag files, or persist anything.'); the simple-skill exception applies and there are no destructive/batch operations requiring validation.	5 / 5
Progressive Disclosure	Under 50 lines with no bundle files, organized into clear sections (Modes, Skills, Deactivate, Configure Default Mode, More) and a single one-level-deep external docs link, qualifying for the top anchor under the simple-skill exception.	5 / 5
	Total	19 / 20 Passed

Description

82%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 well-constructed description that explicitly states what the skill does and when to invoke it, with a strong natural-language trigger clause and a distinct niche. The only weakness is that the capability set is a single display action, limiting specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ('all caveman modes, skills, and commands') and the concrete action ('Quick-reference card', 'One-shot display') but the action set is essentially a single display operation rather than multiple specific actions, fitting the '1-2 concrete actions, not comprehensive' anchor rather than the several-actions anchor at 4.	3 / 5
Completeness	Clearly answers both 'what' (quick-reference card, one-shot, not persistent) and 'when' via an explicit Trigger clause with concrete trigger phrases, matching the top anchor; the 'Use when' cap does not apply since explicit trigger guidance is present.	5 / 5
Trigger Term Quality	Explicit 'Trigger:' clause lists the slash command plus three natural phrases users would say ('caveman help', 'what caveman commands', 'how do I use caveman'), giving good keyword coverage with synonyms; short of 5 only because a few additional natural variants are absent.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (the caveman help card) with a distinct trigger (/caveman-help) separate from sibling caveman skills, giving minimal conflict risk per the top anchor.	5 / 5
	Total	17 / 20 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: anthonystepvoy/caveman-opencode
Path: .opencode/skills/caveman-help/SKILL.md
Commit: d3f5b6e

Reviewed: 22 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.