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".
96
95%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is concise and effective at communicating its purpose and when to trigger. It excels at providing explicit trigger terms and occupying a clear, distinct niche. The main weakness is that the 'what' portion could be slightly more specific about what information the reference card actually displays.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain ('caveman modes, skills, and commands') and a specific action ('quick-reference card' / 'one-shot display'), but doesn't list multiple concrete actions beyond displaying help information. | 2 / 3 |
Completeness | Clearly answers both 'what' (quick-reference card for all caveman modes, skills, and commands; one-shot display, not persistent) and 'when' (explicit trigger terms listed after 'Trigger:'). The explicit trigger guidance is present. | 3 / 3 |
Trigger Term Quality | Includes multiple natural trigger phrases users would actually say: '/caveman-help', 'caveman help', 'what caveman commands', 'how do I use caveman'. These cover common variations of how a user would ask for help. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche — it's specifically a help/reference card for 'caveman' commands, with unique trigger terms that are unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent help/reference skill that exemplifies concise, well-structured documentation. The use of tables for modes and skills is ideal for quick scanning, configuration examples are concrete and copy-paste ready, and the content is perfectly scoped as a one-shot reference card. The opening instruction clearly bounds behavior (no mode changes, no persistence).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Tables compress mode/skill info perfectly. No unnecessary explanations—every token earns its place. The caveman style itself reinforces brevity. | 3 / 3 |
Actionability | Concrete triggers, exact commands, specific config file paths, env var names, and JSON examples are all provided. Copy-paste ready configuration examples with clear precedence rules. | 3 / 3 |
Workflow Clarity | This is a single-purpose reference card (one-shot display), so no multi-step workflow is needed. The single action is unambiguous: display the reference card when triggered. Deactivation and configuration steps are clearly sequenced. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections (Modes, Skills, Deactivate, Configure, More). Links to full docs externally. Content is appropriately sized for a single reference card with no need for additional files. | 3 / 3 |
Total | 12 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
84cc3c1
Table of Contents
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.