Content
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable CLI-based guidance for integrating with AdShares via Membrane, with a well-structured connection workflow including state handling and error recovery. The main weaknesses are unnecessary introductory context about what Adshares is, a stub overview section that adds no value, and a somewhat monolithic structure that could benefit from splitting detailed reference material into separate files.
Suggestions
Remove the introductory paragraph explaining what Adshares is — Claude already knows this, and the description frontmatter covers it.
Either flesh out the 'AdShares Overview' section (Campaign, Wallet, Transaction, User) with actionable details or remove it entirely, as the current stub adds no value.
Consider extracting the proxy request options table and connection state machine details into separate reference files to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what Adshares is (decentralized advertising marketplace, blockchain, etc.) is unnecessary context Claude already knows. The Membrane CLI instructions are mostly efficient but include some redundant explanations like 'so you can focus on the integration logic rather than auth plumbing.' The proxy section and best practices are reasonably lean. | 2 / 3 |
Actionability | The skill provides fully executable CLI commands throughout — from installation, authentication, connection setup, action discovery, action execution, to proxy requests. Commands are copy-paste ready with clear flag descriptions and a useful options table for proxy requests. | 3 / 3 |
Workflow Clarity | The multi-step connection workflow is clearly sequenced with explicit state-based branching (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR). There are clear polling/retry loops for BUILDING state, and the workflow handles error states with guidance on what to check. The overall flow from install → auth → connect → discover actions → run actions is well-structured. | 3 / 3 |
Progressive Disclosure | The content is reasonably organized with clear sections, but it's somewhat monolithic — the proxy request details, connection state machine documentation, and best practices could potentially be split into separate files. The 'AdShares Overview' section listing Campaign/Targeting/Wallet/Transaction/User entities is a stub that adds no value without further content or references. No bundle files are provided to offload detail. | 2 / 3 |
Total | 10 / 12 Passed |