Content
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid integration skill with excellent actionability and workflow clarity — every step has executable commands and the connection state machine is well-documented with feedback loops. The main weaknesses are unnecessary introductory content explaining what AfterShip is (which Claude already knows) and a somewhat sparse 'Overview' section that doesn't add value. Overall it's a functional, well-structured skill that could benefit from trimming the preamble.
Suggestions
Remove or drastically shorten the opening paragraph explaining what AfterShip is — Claude already knows this, and the description metadata covers it.
Either flesh out the 'AfterShip Overview' section with meaningful structural information or remove it entirely, as two nested bullet points provide no useful guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what AfterShip is (shipment tracking platform, e-commerce businesses, etc.) is unnecessary context Claude already knows. The Membrane CLI setup and authentication sections are reasonably efficient but could be tightened. The 'AfterShip Overview' section with just two bullet points adds little value. | 2 / 3 |
Actionability | The skill provides fully executable CLI commands for every step: installation, authentication, connection setup, action discovery, action execution, and proxy requests. Commands are copy-paste ready with clear parameter placeholders and flag descriptions. | 3 / 3 |
Workflow Clarity | The multi-step connection workflow is clearly sequenced with explicit state checks (READY, BUILDING, CLIENT_ACTION_REQUIRED, errors) and feedback loops (poll until ready, handle client actions, re-check state). The progression from connection setup → action discovery → action execution is logical and well-structured. | 3 / 3 |
Progressive Disclosure | The content is reasonably organized with clear sections, but it's somewhat monolithic for its length. The popular actions table, proxy request details, and best practices could potentially be split out. However, with no bundle files provided, the inline approach is acceptable though the 'AfterShip Overview' section is poorly structured and adds little navigational value. | 2 / 3 |
Total | 10 / 12 Passed |