Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.
100
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 is an excellent skill description that hits all the marks. It provides specific capabilities (compressed commit messages, Conventional Commits format, character limits), explicit trigger terms covering natural user phrases and slash commands, and a clear 'Use when' clause. The distinctive 'caveman' branding and specific constraints make it unlikely to conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Ultra-compressed commit message generator', 'Cuts noise from commit messages while preserving intent and reasoning', 'Conventional Commits format', 'Subject ≤50 chars', 'body only when why isn't obvious'. These are highly specific and actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (ultra-compressed commit message generator with Conventional Commits format, ≤50 char subjects, noise reduction) and 'when' (explicit 'Use when...' clause with multiple trigger phrases plus auto-trigger condition). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'write a commit', 'commit message', 'generate commit', '/commit', '/caveman-commit', 'staging changes'. These are exactly the phrases users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche: commit message generation with a specific style (ultra-compressed, caveman). The unique slash commands ('/caveman-commit') and specific constraints (≤50 chars) make it clearly distinguishable from general git or coding skills. | 3 / 3 |
Total | 12 / 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, tightly written skill that exemplifies token efficiency while remaining highly actionable. The rules are specific and concrete, the examples demonstrate both good and bad patterns with real commit messages, and the boundaries section clearly scopes the skill's behavior. The 'What NEVER goes in' section adds genuine value by encoding project-specific anti-patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line earns its place. No explanation of what commits are or how git works. Rules are terse bullet points. The anti-patterns list is valuable project-specific knowledge Claude wouldn't inherently know. | 3 / 3 |
Actionability | Provides concrete format specifications, explicit type lists, character limits, and complete before/after examples with real commit messages. The examples are copy-paste ready and demonstrate both subject-only and subject+body patterns. | 3 / 3 |
Workflow Clarity | This is a single-task skill (generate a commit message) with clear decision logic: when to add body vs. skip it, what never to include, and when body is mandatory (breaking changes, security fixes, etc.). The boundaries section clearly scopes what the skill does and doesn't do. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with no need for external references, the content is well-organized into logical sections (Rules, Examples, Auto-Clarity, Boundaries) that are easy to scan and navigate. | 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.