CtrlK
BlogDocsLog inGet started
Tessl Logo

git-commit

Use when creating git commits to ensure commit messages follow project standards. Applies the 7 rules for great commit messages with focus on conciseness and imperative mood.

67

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

An actionable, well-organized single-purpose skill with executable formatting, concrete examples, and a validation checklist. Its only real weakness is mild redundancy from restating the well-known 7 rules alongside overlapping key principles.

Suggestions

Condense or merge 'The 7 Rules' with 'Key Principles' to remove restatement of standard knowledge Claude already has, improving token efficiency.

If the rules list is retained as a reference, flag it explicitly as a checklist rather than teaching material to signal it is not new instruction.

DimensionReasoningScore

Conciseness

The body is mostly efficient, but 'The 7 Rules' section restates a well-known standard Claude already knows and the 'Key Principles' section overlaps with those rules (imperative mood, subject standing alone), so it could be tightened; not padded enough to score 1.

2 / 3

Actionability

Provides a copy-paste-ready executable HEREDOC commit command plus concrete good and bad commit examples with diagnosed problems and a pre-commit checklist, fully meeting the 'executable, specific, copy-paste ready' anchor.

3 / 3

Workflow Clarity

This is a simple single-task skill that is well-organized, and the 'Checklist Before Committing' serves as an explicit validation checkpoint before the commit, which the simple-skills scoring note permits to score 3.

3 / 3

Progressive Disclosure

A self-contained skill with clear, well-organized sections and no nested or multi-level references; there is no content that genuinely needs splitting into separate files, so well-organized single-file structure earns a 3.

3 / 3

Total

11

/

12

Passed

Description

75%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A clear, third-person description with an explicit 'Use when' trigger and a distinct niche, answering both what and when. It is held back from the top band only by limited action specificity and incomplete coverage of common trigger phrasings.

Suggestions

Add a few more concrete actions to lift specificity, e.g. 'Drafts subject lines and bodies, checks length and mood, and stages the commit'.

Broaden trigger terms to natural user phrasings like 'write a commit message', 'make a commit', or 'review staged changes'.

DimensionReasoningScore

Specificity

Names the domain and an action ('creating git commits to ensure commit messages follow project standards', 'Applies the 7 rules...with focus on conciseness and imperative mood') but describes essentially one action with modifiers rather than the multiple distinct concrete actions the level-3 anchor requires.

2 / 3

Completeness

Explicitly answers both what ('Applies the 7 rules for great commit messages with focus on conciseness and imperative mood') and when ('Use when creating git commits...'), satisfying the explicit-trigger requirement that allows a 3.

3 / 3

Trigger Term Quality

Includes relevant natural terms ('git commits', 'commit messages') but misses common user variations such as 'write a commit message', 'make a commit', or 'staged changes', matching the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

Targets a clear, narrow niche (git commit messages) with a distinct trigger ('Use when creating git commits') that is unlikely to fire for unrelated skills.

3 / 3

Total

10

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
cloudflare/sandbox-sdk
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.