Content
76%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 highly actionable with multiple executable handlers and good reference structure, but lacks an explicit verify→parse→handle workflow with validation checkpoints and includes some duplicated/dangling references.
Suggestions
Add an explicit sequenced workflow (verify signature → check timestamp tolerance → parse → handle idempotently by email_id) with validation checkpoints rather than embedding the sequence only in code.
Remove the duplicate webhook-handler-patterns listing or consolidate it into a single reference, and either create the example/ directories or drop the dangling examples/express, examples/nextjs, examples/fastapi links.
Trim the Attribution section and inline ceremony to tighten token budget.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly lean with copy-paste code and minimal preamble, but the webhook-handler-patterns listing is duplicated across 'Recommended' and 'Related Skills' and the Attribution ceremony adds little. | 4 / 5 |
Actionability | Three complete copy-paste-ready handlers (Express SDK, manual JS, FastAPI), concrete env vars, a local-dev command, and an event-type table fully cover the common cases. | 5 / 5 |
Workflow Clarity | Verify-then-parse ordering is embedded in code with try/catch error handling, but there is no explicit sequenced workflow with validation checkpoints, and signature verification is security-sensitive—capping clarity at 3 per the destructive/batch rule. | 3 / 5 |
Progressive Disclosure | Body is an overview delegating detail to real one-level-deep references (overview.md, setup.md, verification.md), but the 'examples/express' etc. links point to bundle paths that do not exist in the skill. | 4 / 5 |
Total | 16 / 20 Passed |