Content
75%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.
A well-organized, operationally dense skill body: executable commands, a complete picker example, host-specific behavior notes, and unusually good error-recovery guardrails for auth failures and timeouts. The main gaps are the absence of parameter examples for the direct-action tools and a small amount of content that could be split into a reference file.
Suggestions
Add one short parameter example for the most common direct action (e.g. generate-image with prompt and library/size arguments) so the unattended path is as copy-paste ready as the picker path.
Specify what a terminal refresh-generation-run state looks like (success/failed fields) so the video polling loop has an explicit stop condition.
Consider moving the client-specific install variants and reconnect troubleshooting into a reference file to keep SKILL.md closer to an overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with product-specific, non-obvious operational detail ("keep the install/connect command running until the browser authorization finishes", "Never reinstall from scratch just to fix auth") that Claude cannot know. It falls short of the lean 5 anchor because the opening routing sentence restates the description and a few Guardrails sentences could be tightened. | 4 / 5 |
Actionability | Provides copy-paste-ready commands (npx install/connect/reconnect), a complete picker JSON payload, an exact browser fallback URL shape, and specific tool names plus preserved response fields (id, runId, previewUrl). Not a 5 because the eight direct actions are only listed by name with no parameter examples, leaving minor gaps for the unattended path. | 4 / 5 |
Workflow Clarity | Scenarios are clearly separated (Setup, Picker, Direct Actions, Guardrails) with real feedback loops: detect "Session terminated"/"needs auth" → stop retrying → reconnect via /mcp or the reconnect command → continue, plus restart/reload if tools do not appear and batch-timeout retry with count: 1. The batch-timeout validation means the destructive/batch cap at 3 does not apply; it stays at 4 rather than 5 because there is no explicit end-to-end validation step for the video polling loop (no check on what a terminal run state looks like). | 4 / 5 |
Progressive Disclosure | No bundle files exist, and the ~120-line body is organized into four well-labeled sections with everything at one level and no nested references. It does not reach the 5 anchor because the skill exceeds 50 lines and some setup/troubleshooting detail (client-specific install variants, reconnect procedure) could arguably live in a separate reference file. | 4 / 5 |
Total | 16 / 20 Passed |