CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

commit-guards

Load to add, tune, or debug a commit guard lane, its git hooks, or COMMIT_GUARDS_* settings.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

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 lean, tightly written operational skill body that routes each task to an authoritative reference with explicit exit-code and refusal semantics. The main gaps are inline commands for the hook install/disarm workflow and two referenced files (CHECKS.md, kendex.settings.toml.example) missing from the bundle.

DimensionReasoningScore

Conciseness

The ~30-line body is dense and pointer-heavy with zero padding: a four-command quick-start block, exit codes, and conditional 'read X before Y' routing, with no explanation of concepts Claude already knows. Every token carries operational information; only the Git 2.45.1 version-pin sentence borders on the time-sensitive-info concern.

5 / 5

Actionability

The quick-start block ('commit-guards all --staged', '--base origin/main', 'CHECK --help', 'md-reflow PATH...') is copy-paste ready and exit codes 0/1/2 plus concrete push-refusal conditions give executable semantics. Hook install/disarm commands are delegated to 'scripts/install-git-hooks --help' and DEVELOPMENT.md rather than shown inline, leaving minor gaps.

4 / 5

Workflow Clarity

Each task path is unambiguously routed (read CHECKS.md before tuning a check, read hooks-and-settings.md before changing setup, refuse a push whose tip is not HEAD), and validation semantics are explicit via exit codes and collection-error handling. There is no end-to-end sequenced workflow with feedback loops for the install path — it delegates to --help and the DEVELOPMENT.md contract.

4 / 5

Progressive Disclosure

Structure is exemplary: quick-start inline, three well-labeled sections each pointing to one-level-deep references with specific anchors (references/hooks-and-settings.md exists and matches its cited sections). However, CHECKS.md — described as owning all check contracts — and kendex.settings.toml.example are referenced but absent from the bundle, so two central pointers dangle.

4 / 5

Total

17

/

20

Passed

Description

75%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 compact, third-person description with concrete actions and a functional load trigger, well anchored to a distinct niche. Its main limitation is that neither the guard types nor explicit user-trigger phrases are named, leaving it just below the top anchors on every dimension.

DimensionReasoningScore

Specificity

'add, tune, or debug' names three concrete actions applied to specific targets ('a commit guard lane, its git hooks, or COMMIT_GUARDS_* settings'). It falls short of comprehensive because the description never enumerates what the guards check (bytes, conflicts, changelog, markdown, Python names).

4 / 5

Completeness

'Load to add, tune, or debug…' supplies both the what (those actions on lanes, hooks, settings) and an explicit loading condition equivalent to a 'Use when' clause. It lacks concrete user-mention trigger phrases ('when the user asks to…'), so it does not reach the fully explicit level.

4 / 5

Trigger Term Quality

'commit guard', 'git hooks', and 'COMMIT_GUARDS_* settings' are terms a user of this tool would naturally say, and 'tune'/'debug' are natural verbs. Common variations like 'pre-commit hook', 'commit message check', or 'pre-push' are missing, keeping it below comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

'commit guard lane' and 'COMMIT_GUARDS_*' form a clear, tool-specific niche unlikely to fire for unrelated skills. The generic 'git hooks' term creates minor overlap risk with general git-hook skills.

4 / 5

Total

16

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 3 possibly missing (CHECKS.md, CHECKS.md#secrets, kendex.settings.toml.example)

Warning

Total

13

/

16

Passed

Repository

vanillagreencom/kendex

Path

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