pre-commit-hook-setup
Pre Commit Hook Setup - Auto-activating skill for DevOps Basics. Triggers on: pre commit hook setup, pre commit hook setup Part of the DevOps Basics skill category.
35
3%
Does it follow best practices?
Impact
94%
0.97xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/01-devops-basics/pre-commit-hook-setup/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a title repeated with boilerplate metadata rather than a functional skill description. It provides no concrete actions, no explicit trigger guidance, and no natural language keywords that would help Claude select this skill appropriately from a pool of available skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Configures git pre-commit hooks, sets up .pre-commit-config.yaml files, installs pre-commit framework, and adds code quality checks like linting and formatting before commits.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about git hooks, pre-commit configuration, automated code checks before committing, .pre-commit-config.yaml, husky setup, or linting on commit.'
Remove the redundant duplicate trigger term ('pre commit hook setup' is listed twice) and replace with varied natural language terms users might actually use.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('pre commit hook setup') but does not describe any concrete actions like 'configure hooks', 'install pre-commit framework', 'add linting checks', etc. It merely repeats the skill name without elaborating on what it actually does. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the title and completely lacks a 'when should Claude use it' clause. There is no explicit trigger guidance or description of capabilities. | 1 / 3 |
Trigger Term Quality | The only trigger terms are 'pre commit hook setup' repeated twice. It misses natural variations users would say like 'git hooks', 'pre-commit config', '.pre-commit-config.yaml', 'linting before commit', 'husky', or 'git pre-commit'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'pre commit hook' is somewhat specific to a particular DevOps task, which provides some distinctiveness. However, the vague 'DevOps Basics' category and lack of concrete details could cause overlap with other DevOps or git-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell—a template placeholder that contains no actual technical content about pre-commit hook setup. It describes what it would do in abstract terms but provides zero actionable guidance, no code examples, no configuration snippets, and no workflow steps. It would be entirely useless to Claude when trying to help a user set up pre-commit hooks.
Suggestions
Replace the abstract meta-descriptions with actual executable content: include a minimal `.pre-commit-config.yaml` example and the `pre-commit install` command.
Add a clear workflow: 1) Install pre-commit (`pip install pre-commit`), 2) Create `.pre-commit-config.yaml`, 3) Run `pre-commit install`, 4) Validate with `pre-commit run --all-files`.
Include at least one concrete, copy-paste-ready configuration example with common hooks (e.g., trailing-whitespace, end-of-file-fixer, check-yaml, black, flake8).
Remove all boilerplate sections (Purpose, When to Use, Capabilities, Example Triggers) that describe the skill rather than teaching the task—these waste tokens without adding value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content. Every section describes rather than instructs, wasting tokens on information Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance—no commands, no code, no configuration examples, no file paths. The skill contains no executable instructions for actually setting up pre-commit hooks (e.g., no `.pre-commit-config.yaml` example, no `pre-commit install` command, nothing). | 1 / 3 |
Workflow Clarity | There is no workflow whatsoever. No steps are defined for setting up pre-commit hooks, no validation checkpoints, and no sequencing of any kind. The phrase 'step-by-step guidance' is promised but never delivered. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-descriptions with no meaningful structure. There are no references to detailed files, no quick-start section, and no navigation to deeper content. The sections that exist (Purpose, When to Use, Capabilities, Example Triggers) are all boilerplate with no technical substance. | 1 / 3 |
Total | 4 / 12 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 — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
87f14eb
- 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.