windows-hook-debugging

Windows环境下Claude Code插件Hook执行错误的诊断与修复。当遇到hook error、cannot execute binary file、.sh regex误匹配、WSL/Git Bash冲突时使用。

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./bundled/skills/windows-hook-debugging/SKILL.md

Quality

Content

58%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 concise and well-structured as a triage spec, but it stops at triggers and boundaries without any executable diagnostic or repair workflow. Adding a concrete step-by-step diagnosis/fix procedure would lift the two weakest dimensions.

Suggestions

Add a '## Diagnostic steps' section with a concrete ordered procedure (e.g., read settings.json/hooks.json, classify the error string to a root cause, apply the matching fix) so the skill is actionable beyond triage.

Include specific fix commands or snippets for each trigger (e.g., how to convert /d/ paths, how to replace .sh args, how to resolve 'cannot execute binary file'), turning the trigger list into executable guidance.

Add a validation checkpoint (e.g., re-run the hook / restart Claude Code and confirm the error is gone) to give the repair workflow a feedback loop.

Dimension	Reasoning	Score
Conciseness	The ~25-line body is lean and never over-explains concepts Claude already knows (Windows, WSL, hooks); every line — triggers, boundaries, required inputs — earns its place, matching the anchor for lean and efficient content.	5 / 5
Actionability	It provides concrete trigger strings and a required-inputs list, but gives no actual diagnostic or repair steps, commands, or code for the stated "诊断和修复" task, leaving only minimal concrete guidance on how to execute it.	2 / 5
Workflow Clarity	Only a rough triage structure (when to use / not for / required inputs) is present; the diagnostic-fix workflow has no sequenced steps or validation checkpoints, matching the anchor for rough structure with steps absent.	2 / 5
Progressive Disclosure	Under 50 lines with no bundle files needed and clean section headers (When to Use, Not For / Boundaries), qualifying for the simple-skill exception where well-organized sections alone score 5.	5 / 5
	Total	14 / 20 Passed

Description

82%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 tightly scoped, well-triggered description that clearly answers both what and when with concrete error-message keywords and minimal conflict risk. Its only weakness is modest action specificity (only diagnose/repair are named).

Dimension	Reasoning	Score
Specificity	Names the domain (Windows Claude Code Hook 执行错误) and two concrete actions ("诊断与修复" = diagnose and repair), matching the anchor for 1-2 concrete actions without comprehensive coverage; it does not list the several specific actions needed for a 4.	3 / 5
Completeness	It explicitly states both what ("诊断与修复…Hook执行错误") and when ("当遇到…时使用") with concrete trigger phrases, matching the anchor for clearly answering both what and when.	5 / 5
Trigger Term Quality	Includes concrete error strings a user would actually encounter and paste — "hook error", "cannot execute binary file", ".sh regex误匹配", "WSL/Git Bash冲突" — giving good keyword coverage, though a few natural synonyms are missing so it falls short of a 5.	4 / 5
Distinctiveness Conflict Risk	A clear Windows-only Claude Code Hook niche with distinctive error-string triggers (cannot execute binary file, /d/ //c/ paths, WSL/Git Bash) gives minimal conflict risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: foryourhealth111-pixel/Vibe-Skills
Path: bundled/skills/windows-hook-debugging/SKILL.md
Commit: d5ae560

Reviewed: 1 day 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.