precommit-release-gates
How to harden pre-commit against release-only failures, especially packaging mismatches
61
52%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.squad/skills/precommit-release-gates/SKILL.mdQuality
Discovery
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 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 specifying triggers like 'when the user encounters pre-commit hooks passing locally but failing in CI/release pipelines' or 'when debugging packaging mismatches between development and release environments'.
List specific concrete actions the skill covers, such as 'configure pre-commit hooks to validate package metadata, pin dependency versions, detect version drift between pyproject.toml and lock files'.
Include more natural trigger terms users might say, such as 'CI failure', 'pre-commit hooks', 'build fails on release', 'version mismatch', 'package manifest', or specific tool names like 'pyproject.toml', 'setup.py'.
| Dimension | Reasoning | Score |
|---|---|---|
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' only vaguely ('harden pre-commit against release-only failures') and completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 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 somewhat distinctive, but 'packaging mismatches' could overlap with general packaging or dependency management skills, and the lack of specificity makes the boundary unclear. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
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 captures non-obvious lessons about release-only failures. Its main weakness is the lack of executable examples (e.g., a sample pre-commit script snippet) and an explicit step-by-step workflow with validation checkpoints. The anti-patterns section adds good value by clarifying common mistakes.
Suggestions
Add an executable code example showing a minimal pre-commit.ps1 snippet that runs the release command and checks the exit code, making the guidance more copy-paste ready.
Restructure the Patterns section as a numbered workflow with an explicit validation step (e.g., 'Run the release command again to confirm the fix before committing').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every bullet point conveys a distinct, non-obvious insight. No unnecessary explanations of what pre-commit hooks are or how packaging works. | 3 / 3 |
Actionability | The guidance is specific and directional (e.g., 'run the exact release command', 'align config files'), and includes concrete examples like specific file paths and commands. However, there are no executable code snippets or copy-paste ready commands/scripts showing how to implement the pre-commit hook or the fix. | 2 / 3 |
Workflow Clarity | The patterns section implies a sequence (reproduce → promote → synchronize docs), 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. | 2 / 3 |
Progressive Disclosure | For a simple, focused skill under 50 lines, the content is well-organized with clear sections (Context, Patterns, Examples, Anti-Patterns). No need for external references given the scope. | 3 / 3 |
Total | 10 / 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.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- sbroenne/mcp-server-excel
- Commit
468809e
- 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.