CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

prek-pro

Review, configure, and troubleshoot prek hooks when users need prek.toml edits, shim installs, hook validation, or pre-commit migration help.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./Skills/agent-ops/prek-pro/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%Weight 40%Scale 1-5

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

The body is a well-organized, safety-conscious runbook whose diagnosis path (inspect status, classify patch hunks, block on ambiguity) is genuinely specific, but it reads more as a policy document than an executable guide: no prek CLI commands or config examples, heavy repetition of the patch rules, and one dangling external reference. Tightening the repetition and naming the actual commands would lift the core dimensions.

Suggestions

Add the actual prek commands (shim install, hook run, repo validation command) and a minimal prek.toml example, or point 'docs-backed prek syntax' at the specific docs, so the primary setup/migration tasks are executable rather than descriptive.

Consolidate the patch-disposition rules repeated across Workflow, Constraints, Execution Boundaries, Failure Mode, and Gotchas into a single decision section, and drop skill-maintenance meta (context-disposition policy, strict-audit notes) from the runtime body.

Fix the dangling "Infrastructure/references/deferred-skill-context/agent-ops-prek-pro/" pointer by moving that content into the skill's own references/ or removing it, and name the validation command per task type instead of "the command that proves the fix".

DimensionReasoningScore

Conciseness

The bullet style avoids tutorial padding, but patch-disposition rules are repeated across Workflow, Constraints, Execution Boundaries, Failure Mode, and Gotchas, and sections like Philosophy and Constraints carry skill-maintenance meta ("context-disposition policy", "strict skill audit and Plugin Eval") that does not serve the runtime task.

3 / 5

Actionability

Some concrete guidance exists ("git status --short --branch", "~/.cache/prek/patches/*.patch", "git commit --only"), but the core prek tasks lack any executable command or config snippet — no shim-install or hook-run invocation, no prek.toml example, and "docs-backed prek syntax" points to no specific documentation.

3 / 5

Workflow Clarity

The Workflow bullets (read config, classify task, scoped change, run validation) and the Failure Mode branches form a sequence with validation principles ("fail fast", "run the command that proves the fix"), but the steps are unnumbered and scattered across sections, and the validating commands are never actually named.

3 / 5

Progressive Disclosure

A dedicated Progressive Disclosure section signals references/contract.yaml, references/evals.yaml, and references/task-profile.json (all verified present) one level deep with per-file purposes, but the bundle-external "Infrastructure/references/deferred-skill-context/agent-ops-prek-pro/" pointer does not resolve inside the skill, and some Failure Mode detail could live in references.

4 / 5

Total

13

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person, concrete, with an explicit 'when' clause listing specific trigger surfaces. Weaknesses are minor — the stash/patch failure scenarios from the body are not represented as triggers, and the migration phrase could be clearer about migrating to prek.

DimensionReasoningScore

Specificity

"Review, configure, and troubleshoot prek hooks" plus "prek.toml edits, shim installs, hook validation, or pre-commit migration" names the domain with several specific actions, but coverage has gaps — the commit-hook stash/patch failure diagnosis that dominates the skill body is absent.

4 / 5

Completeness

It explicitly answers both parts: what ("Review, configure, and troubleshoot prek hooks") and when ("when users need prek.toml edits, shim installs, hook validation, or pre-commit migration help") with concrete trigger phrases, in third person.

5 / 5

Trigger Term Quality

Good natural keyword coverage ("prek.toml", "shim installs", "hook validation", "pre-commit migration") that users would plausibly say, but common variations like "hook failure", "stash", "patch", or "prek install" are missing.

4 / 5

Distinctiveness Conflict Risk

The prek/prek.toml niche is clearly distinct, but "pre-commit migration help" is directionally ambiguous and could route to a generic pre-commit skill, creating minor overlap risk with a closely related skill.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

jscraik/Agent-Skills

Path

Skills/agent-ops/prek-pro/SKILL.md

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.