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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

100%

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

A tightly written, well-organized reference card that stays on-point and gives Claude everything needed to act in one screen. It exemplifies token-efficient, actionable skill content.

Dimension	Reasoning	Score
Conciseness	The body is a lean reference card of tables and terse directives ("Drop filler. Keep sentence structure.", "Mode stick until changed or session end.") with no padding or explanations of concepts Claude already knows.	3 / 3
Actionability	Exact triggers, per-mode behavior, copy-paste config snippets (`export CAVEMAN_DEFAULT_MODE=ultra`, the JSON config), and an explicit resolution order ("env var > config file > full") give fully executable guidance.	3 / 3
Workflow Clarity	This is a simple single-action skill whose instruction is unambiguous ("Display this reference card when invoked. One-shot — do NOT change mode, write flag files, or persist anything. Output in caveman style."), so per the simple-skills note it earns a 3.	3 / 3
Progressive Disclosure	Content is organized into clearly labeled sections (Modes, Skills, Deactivate, Language, Configure Default Mode, More) with a single one-level-deep external link to full docs; no nested references and no bundle files to navigate.	3 / 3
	Total	12 / 12 Passed

Description

90%

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 lean, third-person, and pairs an explicit what statement with concrete natural-language triggers. Its only gap is that 'reference card' describes one composite action rather than a list of several discrete capabilities.

Suggestions

Optionally list two or three discrete actions (e.g., 'List modes, list skills, show deactivate/config steps') to lift specificity toward the 3-anchor bar.

Dimension	Reasoning	Score
Specificity	"Quick-reference card for all caveman modes, skills, and commands" names the domain and the core action (display a reference card), but it does not enumerate multiple distinct concrete actions comparable to the 3-anchor example.	2 / 3
Completeness	It states what the skill is ("Quick-reference card", "One-shot display, not a persistent mode") and when to use it via explicit "Trigger:" guidance, satisfying both what and when.	3 / 3
Trigger Term Quality	"Trigger: /caveman-help, 'caveman help', 'what caveman commands', 'how do I use caveman'" gives natural phrasings a user would actually say, with good coverage of variations.	3 / 3
Distinctiveness Conflict Risk	The caveman-prefixed triggers carve a clear niche tied to a specific command family, making false-positive activation by other skills unlikely.	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
Commit: 0d95a81

Reviewed: 1 day 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.