CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

engram-commit-hygiene

Commit and branch naming standards for Engram contributors, enforced by GitHub rulesets. Trigger: Any commit creation, review, or branch cleanup.

Quality

80%

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 ./skills/commit-hygiene/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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, highly actionable standards document whose regexes, examples, and checklist give Claude everything needed to comply. Remaining gaps are minor: some rule duplication between sections, no explicit commit-workflow step order, and one broken external reference.

DimensionReasoningScore

Conciseness

The body is dense and efficient — regex, type table, and valid/invalid example blocks with zero concept padding — but has minor redundancy: the pre-commit checklist restates the rules and the branch-type list repeats the commit types, keeping it just below anchor 5.

4 / 5

Actionability

Guidance is fully executable for an instruction-only skill: exact validation regexes, concrete <type>(<scope>): <description> and type/description formats, 10 valid + 5 invalid annotated examples per format, and a runnable pre-commit checklist covering common cases.

5 / 5

Workflow Clarity

Rules are clearly organized with an explicit validation checkpoint (the pre-commit checklist) and 'push will be rejected' feedback signaling, but there is no explicit step sequence for the commit workflow itself, matching anchor 4 rather than 5.

4 / 5

Progressive Disclosure

A single, well-sectioned file with appropriately inline content and one clearly signaled external link; however, at ~125 lines it exceeds the simple-skill threshold and the referenced ../../CONTRIBUTING.md#transient-artifact-policy does not resolve from the skill's location, leaving minor organization gaps.

4 / 5

Total

17

/

20

Passed

Description

71%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 concise, third-person description that clearly answers both what and when with explicit trigger phrases, and is firmly anchored to the Engram contributor niche. Its weakness is thin keyword coverage and a content-catalog framing that never states the actions Claude takes (e.g., write commit messages, name branches).

Suggestions

State the concrete actions Claude performs, e.g. 'Write Conventional Commits messages and name branches as type/description for Engram contributors, per GitHub rulesets.'

Add natural trigger variations users actually say, such as 'commit message', 'naming a branch', 'git commit', or 'PR commit history'.

DimensionReasoningScore

Specificity

The description names the domain concretely ('Commit and branch naming standards for Engram contributors, enforced by GitHub rulesets') covering two concrete artifacts, but it describes the skill's content rather than the actions Claude performs, so it does not reach anchor 4's 'several specific actions'.

3 / 5

Completeness

Both what ('Commit and branch naming standards for Engram contributors, enforced by GitHub rulesets') and when ('Trigger: Any commit creation, review, or branch cleanup') are explicitly stated with concrete trigger phrases, matching the anchor 5 example.

5 / 5

Trigger Term Quality

'Any commit creation, review, or branch cleanup' provides some relevant natural keywords, but common variations users would say ('commit message', 'git', 'PR', 'push rejected') are missing, matching anchor 3.

3 / 5

Distinctiveness Conflict Risk

The Engram-specific, ruleset-enforced niche is mostly distinct, but generic triggers like 'commit creation' and 'review' overlap with general commit-message skills, so it is minor overlap risk (anchor 4) rather than minimal (anchor 5).

4 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 suspicious

Warning

Total

15

/

16

Passed

Repository

Gentleman-Programming/engram

Path

skills/commit-hygiene/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.