Content
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A tight, action-oriented reference with copy-paste JSON examples and no wasted tokens, well-organized for a self-contained single-purpose skill. Its main weakness is the absence of explicit confirmation/validation checkpoints for destructive actions such as unsend and edit.
Suggestions
Add an explicit confirmation step before destructive actions (unsend, edit), e.g. 'Confirm the messageId with the user before calling unsend, since it is irreversible.'
Clarify how to obtain a valid messageId/chat_guid (e.g., from a prior send response or incoming webhook), since several actions depend on it but the source is only implied.
Note which actions are macOS-version dependent inline with the relevant example rather than only in the Notes section, so the constraint is visible at the point of use.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean: a short overview, an inputs list, compact per-action JSON blocks, and brief notes with no padding or explanation of concepts Claude already knows, so every token earns its place. | 3 / 3 |
Actionability | Each action ships a concrete, copy-paste-ready JSON example with real field values (send, react, edit, unsend, reply, sendAttachment, sendWithEffect), matching the 'fully executable, copy-paste ready' anchor. | 3 / 3 |
Workflow Clarity | The disambiguation guardrail ('If the user is vague... ask for...') adds some sequence, but destructive actions like unsend and edit lack any explicit confirmation or validation checkpoint, capping the score at 2 per the rubric's destructive-operation guidance. | 2 / 3 |
Progressive Disclosure | No bundle files exist, and the body is self-contained and well-organized into clear sections with a single clearly signaled one-level reference (extensions/bluebubbles/README.md), avoiding nested references. | 3 / 3 |
Total | 11 / 12 Passed |