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.
80
100%
Does it follow best practices?
Impact
—
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 a strong skill description that clearly communicates its purpose, format constraints, and trigger conditions. It uses third person voice, provides specific concrete actions, and includes comprehensive trigger terms covering both natural language and command invocations. The description is concise yet thorough, making it easy for Claude to distinguish this skill from others.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: generates commit messages, cuts noise while preserving intent/reasoning, uses Conventional Commits format, enforces subject ≤50 chars constraint, includes body only when 'why' isn't obvious. | 3 / 3 |
Completeness | Clearly answers both 'what' (ultra-compressed commit message generator with Conventional Commits format, subject ≤50 chars, body only when needed) 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', and 'staging changes'. These are phrases users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: commit message generation with a specific style (ultra-compressed, caveman). The unique slash commands and specific format constraints make it unlikely to conflict with other 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 skill that practices what it preaches — it's terse, actionable, and well-structured. The anti-pattern examples paired with correct examples provide high-value guidance. The Boundaries section clearly scopes the skill's behavior, and the Auto-Clarity section handles edge cases where compression should be avoided.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line earns its place. No explanations of what Conventional Commits are or how git works. The anti-patterns ('What NEVER goes in') are terse and high-value. The writing style itself embodies the skill's philosophy of terseness. | 3 / 3 |
Actionability | Provides concrete format rules, specific type lists, exact character limits, and complete before/after examples with realistic diffs. The examples show both subject-only and subject+body patterns with real commit messages that are copy-paste ready. | 3 / 3 |
Workflow Clarity | This is a single-task skill (generate a commit message) with clear decision points: when to add a body, when body is mandatory (breaking changes, security fixes, data migrations, reverts), and explicit boundaries about what the skill does NOT do. The workflow is unambiguous for a single-output task. | 3 / 3 |
Progressive Disclosure | For a standalone skill under 50 lines with no need for external references, the content is well-organized into logical sections (Rules, Examples, Auto-Clarity, Boundaries). No monolithic walls of text, and no unnecessary file splitting needed. | 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.
655b7d9
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.