Content
68%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.
A strong, lean reference-style skill whose core is genuinely excellent: executable, correct signature-verification code and immediately usable commands. It loses points on the periphery — promotional cross-links and attribution padding, no explicit handler sequence, and dead examples/ paths relative to the actual bundle.
Suggestions
Add a short numbered handler workflow in the body (receive raw body → verify signature → parse event by X-GitHub-Event → dispatch to handler → respond 200) so the sequence and the verify-first checkpoint are explicit rather than deferred to the examples.
Fix or remove the examples/express/, examples/nextjs/, and examples/fastapi/ links — these paths do not exist in the bundle, so either ship the files, point to the GitHub repo URLs, or drop the pointer to the three reference files.
Trim the 11-item Related Skills list and the Attribution block (or move them to a single reference file) — they consume context without changing what Claude does for this task.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The verification core, tables, and commands are lean, but there is real padding: an 11-item "Related Skills" cross-promotion list, a "Recommended" section that repeats one of those skills, and an "Attribution" block — none of which help Claude execute the task. This is 'mostly efficient but includes some unnecessary content' rather than merely minor trimmable instances. | 3 / 5 |
Actionability | Two complete, copy-paste-ready verification functions (Node and Python) with correct raw-body, sha256, and timing-safe handling, plus a runnable tunnel command (`npx hookdeck-cli listen 3000 github --path /webhooks/github`) and a concrete env var. The common cases are covered by executable code. | 5 / 5 |
Workflow Clarity | The body is organized topically (verification, events, headers, env, dev) rather than as a sequenced handler workflow; the receive → verify → parse → dispatch order is only implied and deferred to the examples/ directories, with no explicit checkpoints in this file. That matches 'sequence present but implicit; checkpoints missing'. | 3 / 5 |
Progressive Disclosure | The three references/*.md links are real, one-level-deep, and clearly signaled with short descriptions — good overview structure. However, the 'examples/express/', 'examples/nextjs/', and 'examples/fastapi/' links point to paths that do not exist in the bundle, breaking navigation for the promised complete handlers, which is more than a purely minor gap. | 4 / 5 |
Total | 15 / 20 Passed |