CtrlK
BlogDocsLog inGet started
Tessl Logo

commits

Generate commit messages following Conventional Commits format. Use when creating commits, writing commit messages, or the user asks to commit changes.

70

Quality

85%

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

88%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, actionable reference for Conventional Commits with copy-paste examples and clear organization. Minor conciseness trim in the Best Practices section could push it higher.

DimensionReasoningScore

Conciseness

The type list, format template, and examples all earn their place with little padding, though the Best Practices bullets restate concepts Claude already knows ('Explain why, not just what'), keeping it just below 5.

4 / 5

Actionability

Copy-paste-ready commit examples cover the common types, and the concrete format template plus issue-reference syntax leave no ambiguity about how to execute.

5 / 5

Workflow Clarity

A simple single-purpose skill with an unambiguous single action, so workflow clarity is strong; no destructive or batch operation triggers the validation cap.

5 / 5

Progressive Disclosure

Well-organized sections (types, examples, good/bad, references) and self-contained with no bundle files, but at over 50 lines it is not a clean fit for the simple-skill 5.

4 / 5

Total

18

/

20

Passed

Description

82%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 clear, third-person description with an explicit 'Use when' clause and concrete trigger phrases. Slightly light on enumerating multiple specific actions, but otherwise strong.

DimensionReasoningScore

Specificity

Names the domain and one concrete action ('Generate commit messages following Conventional Commits format'), but does not list several specific actions like writing or reviewing messages, so it stops short of 4.

3 / 5

Completeness

Explicitly states what it does ('Generate commit messages following Conventional Commits format') and when to use it ('Use when creating commits, writing commit messages, or the user asks to commit changes').

5 / 5

Trigger Term Quality

Includes natural user phrases ('creating commits', 'writing commit messages', 'commit changes') that a user would actually say, though a few common synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

Has a clear niche around commit messages with distinct triggers, posing minimal conflict risk with 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
redis/RedisInsight
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.