Content
65%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 highly actionable, executable webhook skill with comprehensive code and reference tables, weakened by triplicated signature-verification code, missing validation feedback loops around batch DB writes, and a monolithic structure that doesn't leverage reference files.
Suggestions
De-duplicate the signature-verification routine: define it once and reference it from Quick Start and setup-webhook-endpoint to recover token budget.
Add a validate-before-write checkpoint (e.g., schema/required-field check → fix → retry) in the batch handle-data-events upsert loops so destructive/batch operations get a feedback loop.
Move the bulk payload schemas, IP whitelist list, and retry schedule into files under references/ and link to them from SKILL.md so the overview stays lean.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient reference material (tables, retry schedules, IPs) rather than concept padding, but the signature-verification function is repeated three times (Quick Start, setup-webhook-endpoint, verify-signature) and five full JSON payload examples inflate the file, so it could be tightened. | 3 / 5 |
Actionability | Fully executable, copy-paste-ready code covering the common cases (endpoint setup, signature verification, data/auth event handling, idempotency, curl/ngrok testing); the few undefined helpers (db, logger, handle_nutrition) are typical scaffolding rather than missing logic. | 5 / 5 |
Workflow Clarity | A clear numbered sequence exists in Quick Start (verify → parse → handle → respond) with a signature-check checkpoint, but the batch database upsert loops in handle-data-events perform destructive writes with no validate-before-write feedback loop, capping this dimension per the destructive/batch rule. | 3 / 5 |
Progressive Disclosure | The file is well-sectioned with clear headers and tables, but at ~559 lines it is monolithic — payload schemas, the IP whitelist, and the retry table are content that belongs in separate reference files, and no bundle references are used to offload them. | 3 / 5 |
Total | 14 / 20 Passed |