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 is genuinely actionable — real commands, state-machine handling for connections, and a proxy escape hatch — but is undermined by padded intro prose, a redundant overview section, an incorrect table row, and the absence of any validation guidance for the destructive operations it advertises. Tightening the filler and adding delete-safety checks would lift it substantially.
Suggestions
Add validation/verification guidance for destructive operations (e.g. fetch the project with get-project and confirm with the user before delete-project/delete-user), which currently caps workflow clarity at 3.
Fix the "Update Project" row in the Popular actions table, which reuses the get-project-settings key and description instead of the actual update action.
Trim the padded introduction ("Windows developers and teams use it to streamline their software development lifecycle"), the duplicated Project bullet in the Overview, and the filler line "Use action names and parameters as needed".
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient commands and tables, but contains unnecessary padding Claude does not need: "Windows developers and teams use it to streamline their software development lifecycle", a redundant Overview section that lists Project twice with the filler "Use action names and parameters as needed", and "so you can focus on the integration logic rather than auth plumbing". This exceeds the 'minor instances' of the 4 anchor and fits 'mostly efficient but includes some unnecessary explanation'. | 3 / 5 |
Actionability | Guidance is concrete and copy-paste ready throughout (install, login with headless completion, connection ensure/--wait with clientAction handling, action search/run with --input JSON, proxy flag table). Minor gaps keep it below the 5 anchor: the "Update Project" table row incorrectly lists the get-project-settings key and description — a copy-paste hazard — and there is no fully worked end-to-end example with a real action id. | 4 / 5 |
Workflow Clarity | A clear sequence exists (install → login → connection → poll to READY → search actions → run → proxy fallback) with a genuine re-poll feedback loop for CLIENT_ACTION_REQUIRED, but the skill surfaces destructive operations (Delete Project, Delete User, Delete Build) with no validation or verification guidance, which caps workflow clarity at 3 per the rubric. The "skip to Step 2" reference also points to a step label that does not exist. | 3 / 5 |
Progressive Disclosure | A single SKILL.md with well-organized, clearly headed sections and no bundle files to reference. Minor gaps: the 20-row action table is arguably splittable into a reference file, and step numbering is inconsistent (a "1b" subsection and a "Step 2" reference with no Step 1/Step 2 anchors). Fits the 'good structure, minor organization gaps' anchor rather than the 5 anchor, which the under-50-line simple-skill exception does not cover at ~160 lines. | 4 / 5 |
Total | 14 / 20 Passed |