Content
61%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 content delivers mostly executable CLI guidance with a solid connection workflow, but it is padded with platform explanation, lacks a concrete Shippo action example, and omits validation for the destructive/batch operations it lists.
Suggestions
Trim the platform-explanation intro and editorial filler (e.g., "so you can focus on the integration logic rather than auth plumbing") to assume Claude's competence.
Add one concrete end-to-end Shippo example, e.g., creating a shipment and purchasing a label with real `--input` parameters, instead of only generic discovery commands.
Add a validation/verification step for batch and purchase operations (e.g., confirm batch state and check transaction status after Purchase Batch) to satisfy the batch-operation feedback-loop requirement.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The intro paragraph ("Shippo is a shipping platform that helps businesses manage and automate their shipping processes...") explains the platform itself, and padding like "so you can focus on the integration logic rather than auth plumbing" and "This is the fastest way to get a connection" goes beyond minor over-explanation. | 3 / 5 |
Actionability | Concrete, executable commands are given throughout (npm install, membrane login, connection ensure, action run, request) with a flags table, but templates use unsubstituted placeholders (<actionId>, CONNECTION_ID) and no concrete Shippo-specific example (e.g., creating a shipment with real params) is shown, leaving minor gaps. | 4 / 5 |
Workflow Clarity | The connection setup has a clear sequence with validation checkpoints (polling BUILDING→READY, handling CLIENT_ACTION_REQUIRED, re-polling), but the skill lists destructive/batch operations (Create Batch, Purchase Batch) with no validation/verification step for actually running them, which caps workflow clarity at 3 per the batch-operation rule. | 3 / 5 |
Progressive Disclosure | The body is well-organized with clear headers (Overview, Working with Shippo, sub-sections, Best practices) and no nested references, but at ~150 lines with an inlined full action enumeration it is above the simple-skill threshold and could be split, so structure is good rather than exemplary. | 4 / 5 |
Total | 14 / 20 Passed |