prek-pro

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

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%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.

A well-structured, safety-conscious runbook with explicit validation checkpoints and clean progressive disclosure to real bundle files. Main gaps are minor redundancy across safety sections and the absence of copy-paste command blocks for the most common diagnoses.

Suggestions

Consolidate the repeated patch-classification and partial-commit cautions that appear in Workflow, Execution Boundaries, Failure Mode, and Gotchas into a single authoritative section to tighten conciseness.

Add 1-2 copy-paste command blocks for the common commit-hook stash failure diagnosis (e.g., the exact git status / patch inspection sequence) to lift actionability to fully executable.

Mark the deferred Infrastructure/references path as optional/legacy more explicitly so it is not mistaken for a required local bundle.

Dimension	Reasoning	Score
Conciseness	Lean runbook of bullet points that assumes Claude's competence and explains no basic concepts, but some guidance recurs across Workflow, Execution Boundaries, Failure Mode, and Gotchas (e.g., patch-classification and git-commit--only cautions), which could be consolidated.	4 / 5
Actionability	Concrete commands and paths are named ('git status --short --branch', '~/.cache/prek/patches/*.patch', 'git commit --only'), giving mostly executable guidance; falls short of 5 because there are no copy-paste command blocks for the common fix/diagnosis paths.	4 / 5
Workflow Clarity	Clear sequenced checklist with explicit validation ('Run the hook or validation command that proves the fix', 'Fail fast: stop at first failed gate') and a Failure Mode section providing classify/inspect feedback loops for the destructive commit-hook case.	5 / 5
Progressive Disclosure	A dedicated Progressive Disclosure section signals one-level-deep references (references/contract.yaml, evals.yaml, task-profile.json — all present) plus a deferred legacy path, with the body kept as a concise overview and details pushed to bundle files.	5 / 5
	Total	18 / 20 Passed

Description

92%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 tight, well-targeted description that names the domain, multiple concrete actions, and explicit use-when triggers in third person. Minor room for synonym/extension coverage in trigger terms, but otherwise exemplary.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Review, configure, and troubleshoot prek hooks') plus four concrete sub-triggers (prek.toml edits, shim installs, hook validation, pre-commit migration), giving comprehensive coverage of the niche.	5 / 5
Completeness	Explicitly answers both '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.	5 / 5
Trigger Term Quality	Strong natural terms ('prek hooks', 'prek.toml', 'shim installs', 'hook validation', 'pre-commit migration') that users would say, but coverage stops short of synonyms/extensions; not a 5 because it lacks common phrasings like 'prek setup' or file extensions.	4 / 5
Distinctiveness Conflict Risk	Clear niche (prek hook lifecycle) with distinct, specialized triggers and minimal overlap with other skills; the prek/pre-commit specificity sharply reduces conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: jscraik/Agent-Skills
Path: Skills/agent-ops/prek-pro/SKILL.md
Commit: f1f2f21

Reviewed: ~7 hours ago

Table of Contents

Discovery Implementation Validation

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.