CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

commit-style

How to write commit messages in this project.

58

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./examples/docs/skills/skills/commit-style/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

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

The body is an exemplary lean instruction: two precise, immediately actionable rules with no wasted tokens. Its only gap is the absence of a short example commit message showing the expected format in practice.

DimensionReasoningScore

Conciseness

A single sentence — "Write commit messages in the imperative mood and keep the subject under 50 characters" — with zero padding and no explanation of concepts Claude already knows (e.g. what imperative mood is). Every token earns its place, matching the 'lean and efficient' anchor.

5 / 5

Actionability

Two concrete, executable rules (imperative mood; subject under 50 characters) give directly actionable instruction-only guidance with only a minor gap: no example commit message illustrating the expected format. Not 5 because anchor 5 requires examples that cover the common cases.

4 / 5

Workflow Clarity

This is a simple, single-purpose skill (one line, single task) and the single action is unambiguous; per the rubric's simple-skill exception, workflow clarity scores 5 without a multi-step workflow. Commit-message writing is not a destructive or batch operation, so the validation cap does not apply.

5 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references, and no bundle files exist (references/, scripts/, assets/ are absent), which is consistent with its one-sentence scope. Per the rubric's simple-skill guidance, this scores 5.

5 / 5

Total

19

/

20

Passed

Description

40%Weight 40%Scale 1-5

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 identifies its subject (commit messages in this project) but is a topic label rather than a capability statement: it lists no concrete actions and provides no 'Use when' trigger guidance, capping completeness low. It would benefit most from an explicit trigger clause and a concrete action verb.

Suggestions

Add an explicit trigger clause, e.g. "Use when writing or reviewing commit messages, or when preparing to commit changes in this project", to supply the missing 'when' that currently caps completeness.

State concrete capabilities instead of restating the topic, e.g. "Generate commit messages from staged git diffs following the project's message format", to sharpen specificity.

Include natural trigger variations such as "git commit", "commit message", and "conventional commits" to broaden keyword coverage.

DimensionReasoningScore

Specificity

"How to write commit messages" names the domain but the only action is the generic "write" — no concrete capabilities such as generating messages from diffs or enforcing a message format. This matches anchor 2 ('names the domain but actions are minimal or generic') rather than 3, which requires 1-2 concrete actions.

2 / 5

Completeness

The description is a thin topical statement — it never states what the skill actually does (guide? generate? validate?) and has no 'Use when...' clause or equivalent trigger guidance. The what is vague rather than clear, so it sits at anchor 2 ('vague what and no when') and does not reach the cap of 3.

2 / 5

Trigger Term Quality

"commit messages" is a natural phrase a user would say, but the description includes no variations or synonyms such as "git commit", "commits", or "conventional commits". This matches anchor 3 ('some relevant keywords but missing common variations') rather than 4, which requires good keyword coverage.

3 / 5

Distinctiveness Conflict Risk

"commit messages in this project" carves a mostly distinct niche with only minor overlap risk against closely related git-commit skills. Not 5 because there are no distinct trigger phrases reinforcing the niche.

4 / 5

Total

11

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

rivet-dev/sandbox-agent

Path

examples/docs/skills/skills/commit-style/SKILL.md

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.