CtrlK
BlogDocsLog inGet started
Tessl Logo

setup-pre-commit

Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.

100

1.33x
Quality

100%

Does it follow best practices?

Impact

100%

1.33x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

This is a well-crafted skill that provides clear, actionable, step-by-step instructions for setting up Husky pre-commit hooks. It's concise without sacrificing completeness, includes executable code and config files, and has a proper verification checklist. The adaptive instructions (package manager detection, conditional script inclusion) show thoughtful handling of real-world variation.

DimensionReasoningScore

Conciseness

The content is lean and efficient. It doesn't explain what Husky, lint-staged, or Prettier are beyond their role. Every section serves a purpose and there's no padding or unnecessary context. The 'What This Sets Up' section is a brief bullet list, not a verbose explanation.

3 / 3

Actionability

Every step includes concrete, executable commands and exact file contents to write. The config files are complete JSON, the commands are copy-paste ready, and adaptive instructions (e.g., detecting package manager, omitting missing scripts) are specific and clear.

3 / 3

Workflow Clarity

The 8 steps are clearly sequenced with logical ordering (detect → install → init → configure → verify → commit). Step 7 includes an explicit verification checklist with specific checks, and Step 8 serves as a smoke test. The 'Adapt' callout in Step 4 handles conditional logic clearly.

3 / 3

Progressive Disclosure

For a single-purpose skill under 100 lines with no need for external references, the content is well-organized with clear section headers and appropriate depth. Everything needed is inline, which is appropriate for this scope.

3 / 3

Total

12

/

12

Passed

Description

100%

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 is an excellent skill description that clearly communicates specific capabilities (Husky, lint-staged, Prettier, type checking, tests), includes a well-formed 'Use when' clause with natural trigger terms, and occupies a distinct niche. It uses proper third-person voice and is concise without being vague.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: setting up Husky pre-commit hooks, configuring lint-staged with Prettier, type checking, and tests. These are all concrete, actionable capabilities.

3 / 3

Completeness

Clearly answers both 'what' (set up Husky pre-commit hooks with lint-staged, Prettier, type checking, and tests) and 'when' (explicit 'Use when' clause listing multiple trigger scenarios like adding pre-commit hooks, setting up Husky, configuring lint-staged, or adding commit-time checks).

3 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: 'pre-commit hooks', 'Husky', 'lint-staged', 'Prettier', 'commit-time formatting', 'typechecking', 'testing'. These are all terms a developer would naturally use when requesting this setup.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche: Husky + lint-staged + pre-commit hook setup. The specific tool names (Husky, lint-staged, Prettier) and the commit-time context make it very unlikely to conflict with other skills like general linting or testing skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
mattpocock/skills
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.