CtrlK
BlogDocsLog inGet started
Tessl Logo

precommit-release-gates

How to harden pre-commit against release-only failures, especially packaging mismatches

48

Quality

52%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.squad/skills/precommit-release-gates/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a concise, well-structured skill that efficiently communicates project-specific knowledge about hardening pre-commit hooks against release failures. Its main weakness is that it stays at the pattern/guidance level without providing executable commands or explicit validation steps, which limits actionability and workflow clarity. The anti-patterns section adds good value by clearly bounding what not to do.

Suggestions

Add an explicit numbered workflow with validation checkpoints, e.g., '1. Reproduce failure with `npm run package` 2. Fix config files 3. Re-run `npm run package` to verify 4. Update pre-commit script 5. Run pre-commit hook to confirm it catches the class of error'.

Include a concrete, copy-paste-ready code snippet showing the relevant portion of `scripts/pre-commit.ps1` or the exact commands to run for validation.

DimensionReasoningScore

Conciseness

Every bullet earns its place. No unnecessary explanations of what pre-commit hooks are or how packaging works. Assumes Claude understands the domain and gets straight to the novel, project-specific guidance.

3 / 3

Actionability

Provides concrete examples (specific files, specific commands like `npm run package`), but lacks executable code snippets or copy-paste-ready commands. The guidance is specific but more descriptive than directly executable—e.g., no actual script content or validation commands are shown.

2 / 3

Workflow Clarity

The Patterns section implies a sequence (reproduce → promote → sync docs → align configs), but it's presented as a bullet list rather than an explicit ordered workflow. There are no validation checkpoints or feedback loops for verifying the fix worked before committing.

2 / 3

Progressive Disclosure

For a simple, focused skill under 50 lines with no need for external references, the content is well-organized into clear sections (Context, Patterns, Examples, Anti-Patterns) that are easy to scan and navigate.

3 / 3

Total

10

/

12

Passed

Description

32%

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 identifies a narrow and somewhat specific topic (pre-commit hardening for release failures) but reads more like a document title than a skill description. It lacks concrete actions, explicit trigger guidance ('Use when...'), and sufficient natural keywords to help Claude reliably select it from a pool of skills.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user encounters pre-commit hook failures during releases, packaging version mismatches, or CI pipeline errors related to pre-commit configuration.'

List specific concrete actions the skill covers, e.g., 'Configures pre-commit hooks to catch packaging mismatches, validates version consistency between pyproject.toml and setup.cfg, and adds CI checks to prevent release-only failures.'

Include more natural trigger terms users might say, such as 'pre-commit hooks', 'CI failures', 'version mismatch', 'build packaging errors', or 'release pipeline'.

DimensionReasoningScore

Specificity

The description names a specific domain ('pre-commit') and a general action ('harden'), and mentions 'packaging mismatches' as a specific concern, but it doesn't list concrete actions like 'configure hooks', 'add version pinning', or 'validate package manifests'.

2 / 3

Completeness

The description addresses 'what' at a high level (hardening pre-commit against release-only failures) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' itself is also vague, warranting a 1.

1 / 3

Trigger Term Quality

Includes some relevant keywords like 'pre-commit', 'packaging mismatches', and 'release-only failures' that a user might mention, but misses common variations like 'CI failures', 'build errors', 'pre-commit hooks', 'pyproject.toml', 'setup.cfg', or 'dependency conflicts'.

2 / 3

Distinctiveness Conflict Risk

The combination of 'pre-commit' and 'release-only failures' is fairly specific and unlikely to conflict with many other skills, but 'packaging mismatches' could overlap with general packaging or dependency management skills.

2 / 3

Total

7

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
sbroenne/mcp-server-excel
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.