Content
75%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 comprehensive, copy-paste-ready Membrane CLI commands and a well-sequenced connection state machine with feedback loops. Its main weaknesses are a marketing-flavored intro that pads the token budget and a dangling 'Step 2' reference with no destructive-action validation guidance.
Suggestions
Trim the introductory marketing paragraph ('CraftMyPDF is a document automation platform that helps users generate PDFs ... used by businesses of all sizes') to a single purpose line, since Claude does not need the platform pitch.
Fix the dangling 'Step 2' reference by either labeling the workflow steps explicitly (Step 1: Connect, Step 2: Run actions) or removing the cross-reference.
Add a short validation checkpoint before destructive/batch actions (e.g. 'Before running delete-template, confirm the template ID with the user') to lift workflow clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Most of the body is efficient CLI guidance, but the opening marketing paragraph ('document automation platform that helps users generate PDFs ... used by businesses of all sizes') and phrases like 'so you can focus on the integration logic rather than auth plumbing' are unnecessary explanation Claude does not need, matching the 'mostly efficient but includes some unnecessary explanation' anchor. | 3 / 5 |
Actionability | The body provides copy-paste-ready executable commands throughout (npm install, membrane login, connection ensure/get, action list/run, request) with concrete flags and a tables of action keys and proxy options, fully covering the common cases per the 5-anchor. | 5 / 5 |
Workflow Clarity | The connect → poll-until-ready → handle clientAction states → search → run → proxy sequence is clear with a genuine feedback loop (poll state, act, re-poll), but the dangling 'skip to Step 2' reference (no Step 2 is defined) and the absence of validation guidance around destructive actions like delete-template leave minor gaps, fitting 4 over 5. | 4 / 5 |
Progressive Disclosure | The skill is a single file with no bundle references, but it is well-organized into clearly headed sections (Install, Authentication, Connecting, Searching, Popular actions, Running, Proxy, Best practices) with content appropriately placed for a CLI integration guide, matching 'good structure; most content appropriately placed; minor organization gaps' rather than the over-50-line monolith penalty of 3. | 4 / 5 |
Total | 16 / 20 Passed |