demo

Write clear, conventional git commit messages

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/demo/SKILL.md

Quality

Content

100%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 content is a tightly written, fully actionable guide to Conventional Commits with concrete format rules and examples, well-organized for a simple single-purpose skill.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it specifies the format, rules, and examples with no padding or explanations of concepts Claude already knows.	5 / 5
Actionability	It gives a concrete format `<type>(<scope>): <description>`, enumerates types, sets a 72-char limit, and provides copy-paste-ready examples covering common cases.	5 / 5
Workflow Clarity	A simple, single-purpose skill with an unambiguous numbered sequence of rules; no destructive/batch operation is involved, so the simple-skill exception applies.	5 / 5
Progressive Disclosure	Under 50 lines with no need for external references (no bundle files present), the body is well-organized into a numbered list and examples, satisfying the simple-skill exception.	5 / 5
	Total	20 / 20 Passed

Description

53%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 is concise and names a concrete, distinct domain in third person, but it lacks an explicit "Use when..." trigger and offers only a single named action with limited keyword coverage.

Suggestions

Add a "Use when..." clause (e.g. "Use when writing or reviewing git commit messages or staged changes") to raise completeness.

Expand the action coverage and natural keywords (e.g. "write, review, and format commit messages") to improve specificity and trigger-term quality.

Dimension	Reasoning	Score
Specificity	The phrase "Write clear, conventional git commit messages" names the domain and one concrete action (write), but is not comprehensive — it omits review/editing and has no enumerated capabilities.	3 / 5
Completeness	It gives a clear "what" (write conventional commit messages) but no "when"/"Use when..." trigger clause, capping completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	"git commit messages" and "conventional" are relevant natural terms, but common variations/synonyms (e.g. "commits", "committing", "review staged changes") are missing.	3 / 5
Distinctiveness Conflict Risk	The git-commit niche is mostly distinct with minimal overlap risk, though the absence of an explicit trigger phrase keeps it just short of the clearest 5 anchor.	4 / 5
	Total	13 / 20 Passed

Validation

100%

Warnings & errors only

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: popey/tessl-plugin-demo
Path: skills/demo/SKILL.md
Commit: 975d18b

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.