Content
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A concise, highly actionable API skill body with clean progressive disclosure via real reference files. Its one weakness is workflow clarity: batch and destructive operations ship without validation checkpoints or error-recovery guidance.
Suggestions
Add validation/verification steps for risky operations: after createBulk, check the response for per-subscriber success and retry failures; before delete, note it is irreversible and that existing notifications persist (already a pitfall) so the caller can confirm.
For createBulk specifically, document how to handle partial failures across the 500-subscriber batch rather than presenting it as a fire-and-forget call.
Fix the typo "subsriberId-1" in the FCM credentials example so the copy-paste-ready code is accurate.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and code-first — each operation is a tight code block with only Novu-specific notes; it does not explain concepts Claude already knows, and the Common Pitfalls add genuinely non-obvious per-environment/autocreate behavior. Not the level below because there is no unnecessary explanation or padding to tighten. | 3 / 3 |
Actionability | Every operation (create, retrieve, search, patch, delete, createBulk, topics CRUD, FCM/APNS credentials) ships as concrete, copy-paste-ready TypeScript with realistic values, matching the fully-executable anchor. A minor typo ("subsriberId-1" in the FCM example) does not undermine the executability of the guidance. | 3 / 3 |
Workflow Clarity | Individual operations are unambiguous, but the batch operation (createBulk, 500 subscribers) and destructive operations (delete) lack any validation checkpoints or feedback loops, which the rubric's scoring notes explicitly cap at 2. It is not a 3 because there are no verify-after-write or error-recovery steps for these risky operations. | 2 / 3 |
Progressive Disclosure | The body is a clear overview with a well-signaled one-level-deep References section pointing to three real, existing files (subscriber-crud-examples.md, topics-examples.md, credentials-examples.md), giving easy navigation without nested references. | 3 / 3 |
Total | 11 / 12 Passed |