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 mostly lean, actionable connector skill with a solid connection-state workflow, but it lacks validation/verification guidance for the destructive and batch email actions it exposes, which caps its workflow clarity. Structure and actionability are otherwise strong.
Suggestions
Add a validation/verification step before destructive or batch actions (e.g., list-then-confirm before delete-email or move-emails, and check the response `output`/`error` field after running) to lift workflow clarity above the cap.
Clarify the `membrane connection ensure ""` placeholder — show what URL/domain value belongs there, or provide an end-to-end example that threads the returned connection id into `action list`/`action run`.
Consider moving the popular-actions reference table into a separate reference file and linking to it from the body, so the overview stays leaner.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Direct executable commands and assumes Claude's competence throughout; minor editorial padding ("so you can focus on the integration logic rather than auth plumbing") keeps it just below the lean anchor 5. | 4 / 5 |
Actionability | Concrete, copy-paste-ready commands cover the common cases (login, connect, search, run, proxy), but a few placeholders are ambiguous — notably `membrane connection ensure ""` with an empty-string URL and chaining of `<id>`/`<actionId>` across commands without an end-to-end example — preventing anchor 5. | 4 / 5 |
Workflow Clarity | The connection setup is a well-sequenced workflow with a poll-state feedback loop, but the skill includes destructive/batch actions (delete-email, move-emails, mark-emails-as-read/unread) with no validation or verification guidance before running them, which caps workflow clarity at 3 per the destructive-operation rule. | 3 / 5 |
Progressive Disclosure | Well-organized sections with clear headers and no nested references, and no bundle files exist; the 14-row popular actions table is bulk reference content kept inline, a minor organization gap that keeps it below the ideally-split anchor 5. | 4 / 5 |
Total | 15 / 20 Passed |