Content
67%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 a well-structured, actionable guide with concrete CLI commands and a clear connection/execution workflow supported by state-polling validation. Its main weakness is introductory and commentary padding that competes with the token budget.
Suggestions
Trim the opening paragraph explaining what ZenRows is and who uses it; Claude already knows scraping APIs.
Remove commentary like "so you can focus on the integration logic rather than auth plumbing" that adds no executable value.
Standardize on either `membrane` or `npx @membranehq/cli` consistently across examples to avoid invocation ambiguity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient but includes unnecessary padding — the intro explaining what ZenRows is and who uses it, plus "so you can focus on the integration logic rather than auth plumbing" — that Claude does not need. | 3 / 5 |
Actionability | It provides concrete, copy-paste-ready commands (install, login, connection ensure, action list/run, request) with a flags table, with only minor gaps such as unresolved placeholders and mixed npx/membrane invocations. | 4 / 5 |
Workflow Clarity | The install → login → ensure → poll → search → run sequence is clear and includes validation via state polling (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) with a re-poll feedback loop after user action. | 4 / 5 |
Progressive Disclosure | No bundle files are present; the single SKILL.md is well-organized with clear section headers and no nested references, though at ~150 lines it exceeds the simple-skill threshold that would warrant a 5. | 4 / 5 |
Total | 15 / 20 Passed |