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 restated title with boilerplate metadata. It provides no concrete actions, no meaningful trigger terms beyond the skill name repeated twice, and no explicit guidance on when Claude should select this skill. It would be very difficult for Claude to confidently choose this skill from a large pool.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates and configures git pre-commit hooks, sets up the pre-commit framework, defines linting and formatting checks that run before each commit.'
Add a 'Use when...' clause with natural trigger terms like 'git hooks', 'pre-commit config', '.pre-commit-config.yaml', 'run checks before commit', 'husky', 'lint-staged'.
Remove the duplicate trigger term and replace with diverse, natural phrases users would actually say when needing this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('pre commit hook setup') but does not describe any concrete actions like 'creates hook scripts', 'configures linting rules', or 'installs pre-commit framework'. It merely restates the skill name without elaborating on what it actually does. | 1 / 3 |
Completeness | The description fails to clearly answer 'what does this do' beyond the title, and there is no explicit 'when should Claude use it' clause. The 'Triggers on' line is just a duplicate of the skill name, not meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are identical duplicates ('pre commit hook setup') with no natural variations users might say, such as 'git hooks', 'pre-commit config', '.pre-commit-config.yaml', 'linting before commit', or 'husky setup'. | 1 / 3 |
Distinctiveness Conflict Risk | The phrase 'pre commit hook' is somewhat specific to a particular DevOps task, which provides some distinctiveness. However, the lack of detail means it could overlap with broader git configuration or DevOps skills without clear differentiation. | 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 essentially a placeholder template with no substantive content. It contains no executable code, no specific commands, no configuration examples, and no actual instructions for setting up pre-commit hooks. It fails on every dimension because it describes what a skill would do rather than actually providing the skill.
Suggestions
Add concrete, executable examples: show how to install pre-commit (e.g., `pip install pre-commit`), create a `.pre-commit-config.yaml` with sample hooks, and run `pre-commit install`.
Define a clear workflow with validation steps: 1) Install pre-commit tool, 2) Create config file, 3) Install hooks, 4) Test with `pre-commit run --all-files`, 5) Verify hooks trigger on `git commit`.
Remove all meta-description sections ('Purpose', 'When to Use', 'Capabilities', 'Example Triggers') and replace with actionable content that teaches Claude how to actually set up pre-commit hooks.
Include a concrete `.pre-commit-config.yaml` example with common hooks (trailing whitespace, YAML lint, secrets detection) that Claude can adapt for users.
| 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 instructions, commands, or configurations for setting up pre-commit hooks. Every section restates the same vague idea. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no configuration examples, no specific tool references (e.g., pre-commit framework, husky, git hooks). It only describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow steps are provided at all. Setting up pre-commit hooks is inherently a multi-step process (install tool, create config, install hooks, test), yet none of this is present. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to supporting files, no structured navigation, and no separation of overview from detail. There are no bundle files to support it either. | 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
13d35b8
- 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.