CtrlK
BlogDocsLog inGet started
Tessl Logo

writing-git-commits

Writes git commit messages with proper format, type prefixes (feat/fix/chore), and imperative mood. Use when committing changes, writing a commit message, formatting commit text, or asking how to commit code properly.

70

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

93%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.

A tight, well-structured single-purpose skill body with concrete examples and a clear validation checklist, and no padding. The only marginal gap is the absence of an explicit error-recovery feedback loop, which the rubric notes is most critical for destructive/batch operations that this skill is not.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence—no preamble explaining what git or commits are—relying on compact tables, a short format template, and minimal examples, with every token earning its place.

5 / 5

Actionability

It provides fully concrete, copy-paste-ready guidance: explicit subject-line format, a type table with worked examples, and complete annotated example messages for the minimum, body, and footer cases.

5 / 5

Workflow Clarity

A clear sequenced 'Validation Gates' checklist (subject, body/footer only if requested, final checks) gives an explicit workflow, but the validation is a static checklist rather than a true validate-fix-retry feedback loop.

4 / 5

Progressive Disclosure

For a sub-50-line single-purpose skill with no bundle files and no need for external references, the content is well-organized into clearly labeled sections, satisfying the simple-skill exception for progressive disclosure.

5 / 5

Total

19

/

20

Passed

Description

78%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.

A strong, specific description that clearly states what the skill does and when to use it with natural trigger phrases. The only minor gap is that the 'when' clause is somewhat broad and could enumerate a few more concrete commit-related synonyms.

DimensionReasoningScore

Specificity

Names the domain (git commit messages) and lists several concrete actions—writing commit messages, applying type prefixes (feat/fix/chore), using imperative mood—though coverage of format details beyond prefixes is implied rather than exhaustive.

4 / 5

Completeness

It explicitly answers both 'what' (writes git commit messages with format, type prefixes, imperative mood) and 'when' (Use when committing changes, writing a commit message, formatting commit text, or asking how to commit code properly), with the 'when' slightly broad rather than maximally specific.

4 / 5

Trigger Term Quality

Includes natural user phrases like 'committing changes', 'writing a commit message', and 'how to commit code properly', covering common variations, though synonyms like 'git log' or 'PR description' are absent.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear, narrow niche (commit message authoring) with distinct trigger phrases and minimal overlap risk against other skills.

5 / 5

Total

17

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
emgreppi/Business-Central-AI-Skill
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.