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 body delivers strong, executable Membrane CLI guidance with good coverage of auth, connection lifecycle, actions, and proxy fallback, and reasonable single-file organization. Its weaknesses are padded conceptual intro text, a workflow with a broken step reference ('Step 2') and no validation for the destructive delete actions it lists, and a confusing overview section. Tightening the intro and fixing the step numbering with validation checkpoints would raise it substantially.
Suggestions
Remove or compress the introductory paragraphs explaining what ArcGIS Online is, and delete the filler line 'Use action names and parameters as needed' plus the duplicate 'User' bullet.
Fix the workflow numbering: define the steps being referenced (the 'skip to **Step 2**' target does not exist) and give '1b' a matching '1a'/'Step 2' structure.
Add a validation checkpoint before destructive actions (delete-item, delete-group), e.g. get the item/group first, confirm with the user, then delete and verify the result.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly dense commands and tables, but it spends tokens on concepts Claude already knows ('ArcGIS Online is a cloud-based mapping and analysis platform... Think of it as Google Maps but for professional use'), includes filler like 'Use action names and parameters as needed', and duplicates the 'User' bullet in the overview. It is below anchor 4 because there are several, not just minor, unnecessary passages. | 3 / 5 |
Actionability | Concrete, copy-paste-ready CLI commands cover install, login (including headless completion), connection setup, action discovery/execution, and proxied API requests, backed by a 15-action table and a flags table. It falls short of anchor 5 because placeholders like <actionId>, <code>, and CONNECTION_ID are never instantiated in a single worked end-to-end example. | 4 / 5 |
Workflow Clarity | A rough sequence exists (install → authenticate → connect → poll state → search actions → run), but 'skip to **Step 2**' references a step that is never defined, the '1b' heading has no matching '1a'/'2' structure, and destructive actions (Delete Item, Delete Group) have no validation or confirmation workflow. Per the rubric's destructive-operation cap, this cannot score above 3. | 3 / 5 |
Progressive Disclosure | The skill is a single file with no bundle files; its sections and inline tables (popular actions, proxy flags) are reasonably placed and appropriately sized, with no nested references. It is below anchor 5 because the 'ArcGIS Online Overview' bullet tree is confusing (duplicated 'User', no explanation of the hierarchy) and heading nesting is inconsistent ('Searching for actions' sits inside 'Working with ArcGIS Online' while 'Popular actions' is a sibling). | 4 / 5 |
Total | 14 / 20 Passed |