CtrlK
BlogDocsLog inGet started
Tessl Logo

caveman-commit

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

Quality

100%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

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 — terse, precise, and actionable. The rules are specific and concrete, the examples demonstrate both good and bad patterns with realistic diffs, and the boundaries are clearly defined. The content is well-structured for a single-purpose skill with no unnecessary verbosity.

DimensionReasoningScore

Conciseness

Every line earns its place. No explanations of what Conventional Commits is or how git works. The rules are stated as terse directives, and the anti-patterns ('What NEVER goes in') are sharp and specific. The tone itself models the skill's purpose.

3 / 3

Actionability

Provides concrete, copy-paste-ready examples with both good and bad outputs. The rules are specific enough to execute (character limits, allowed types, imperative mood verbs, bullet style). The examples show real commit messages with body formatting, issue references, and breaking change notation.

3 / 3

Workflow Clarity

This is a single-task skill (generate a commit message), and the workflow is unambiguous: read the diff, apply the rules, output a code block. The 'Auto-Clarity' section acts as a validation checkpoint for when body is mandatory. The 'Boundaries' section clearly scopes what the skill does and doesn't do. No destructive or batch operations are involved.

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 bundle files are needed, and the structure supports quick scanning.

3 / 3

Total

12

/

12

Passed

Description

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 concrete actions, comprehensive trigger terms that users would naturally use, explicitly answers both what and when, and occupies a clear distinctive niche. The description is concise yet information-dense, using third person voice throughout.

DimensionReasoningScore

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 concrete, actionable details about what the skill does.

3 / 3

Completeness

Clearly answers both 'what' (ultra-compressed commit message generator with Conventional Commits format, subject ≤50 chars, body only when why isn't obvious) 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 users would say: 'write a commit', 'commit message', 'generate commit', '/commit', '/caveman-commit', 'staging changes'. These are highly natural phrases a user would actually type.

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 format constraints (≤50 chars) make it clearly distinguishable from generic git or coding skills.

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
anthonystepvoy/caveman-opencode
Reviewed

Table of Contents

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.