Content
50%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 operational half of this skill is strong — executable Membrane CLI commands with clear connection-state handling — but it is undermined by a ~280-line auto-generated noun dump that inflates the body and adds no value. Data-mutating operations also lack validation or verification steps.
Suggestions
Delete the 'Spotlightr Overview' bullet list (or move genuine Spotlightr-specific entities into a separate reference file); it is largely generic, duplicated padding.
Add a validation/verification checkpoint before destructive or batch operations (e.g., confirm the action's inputSchema, dry-run or confirm before proxy DELETE/PUT, verify the `output` field after running an action).
Replace placeholder values (CONNECTION_ID, QUERY, actionId) with a concrete end-to-end worked example so the guidance is fully copy-paste ready.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body opens with ~280 lines of a generic noun list (Video, Hotspot, Button, Link, Create, Read, Update, Delete...) with many duplicates, which is a heavily padded section that wastes the context window; it is not a 1 because the operational CLI sections that follow are reasonably efficient and free of concept over-explanation. | 2 / 5 |
Actionability | The CLI sections give concrete, copy-paste-ready commands (install, login, connection ensure, action list/run, request) plus a full proxy flag table, matching 'mostly executable guidance with minor gaps'; it is not a 5 because placeholders (CONNECTION_ID, QUERY, actionId) are left for the reader to resolve and the overview list adds no actionable value. | 4 / 5 |
Workflow Clarity | The connection flow is clearly sequenced with state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-again feedback loop, but running actions and proxy requests (which support destructive POST/PUT/DELETE and manage Users/Organizations) lack any validation or verification step, capping workflow clarity at 3 per the destructive/batch guideline. | 3 / 5 |
Progressive Disclosure | The operational sections are organized under clear headers, but the giant inlined overview list is content that clearly belongs in a separate reference file or should be removed, and no external bundle references are signaled; it is not a 4 because nothing is split out despite the body being ~340 lines. | 3 / 5 |
Total | 12 / 20 Passed |