Content
82%Weight 40%Scale 1-5Reviews 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-executed webhook skill: the verification core is correct, executable, and emphasizes the exact gotchas (raw body, lowercase hex, Read-Only key, custom-vs-Standard-Webhooks distinction), with details properly pushed to reference files. The main defects are promotional/relational sections that pad the token budget and three dangling examples/ links that promise content absent from the bundle.
Suggestions
Remove or shrink the "Related Skills" (7 links), "Recommended: webhook-handler-patterns", and "Attribution" sections, or fold them into a single reference file — they spend tokens without aiding the core task.
The "For complete handlers with route wiring..." note links to examples/express/, examples/nextjs/, and examples/fastapi/ which do not exist in the bundle; either add those example files or drop/replace the links with pointers that resolve.
Add a brief inline handler sequence (verify → parse → idempotently handle) in place of delegating entirely to the external webhook-handler-patterns skill, so the core workflow is self-contained.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with genuinely non-obvious information (raw-body signing, SHA-256-vs-SHA1 scheme distinction, thin payload with fetch-back) and avoids explaining concepts Claude already knows. Not 5 because the "Related Skills" list (7 external links), the "Recommended" cross-promotion, and the "Attribution" section add tokens that don't serve the task and could be trimmed or moved to a reference. | 4 / 5 |
Actionability | Fully executable, copy-paste-ready guidance: complete Node and Python verification functions with timing-safe comparison and malformed-hex handling, a concrete env var, a runnable hookdeck CLI command, and the exact fetch-back endpoint (GET /library/{libraryId}/videos/{videoGuid}). Covers the common cases end to end. | 5 / 5 |
Workflow Clarity | The critical sequencing is explicit ("Verify against the unparsed raw body", "Verify the signature **before** making any fetch-back call") and the code handles the error path (catch → false). Not 5 because the full handler sequence (verify → parse → idempotent handling) is delegated to an external skill rather than stated in-file, leaving minor checkpoint gaps for the handling step. | 4 / 5 |
Progressive Disclosure | Good structure: SKILL.md is an overview with clearly signaled, one-level-deep references (references/overview.md, setup.md, verification.md — all real files) each annotated with its purpose. Not 5 because the body links examples/express/, examples/nextjs/, and examples/fastapi/ which do not exist anywhere in the bundle, so navigation dead-ends for the promised complete handler examples. | 4 / 5 |
Total | 17 / 20 Passed |