Content
71%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 is a well-sectioned, highly actionable operator's guide for the Rube/Linear toolset with a validated setup flow, held back by wholesale duplication between the workflow, Known Pitfalls, and Quick Reference sections and by the absence of any reference files to offload the tool catalog. Splitting the reference material out and deduplicating the pitfalls would address the two weakest dimensions.
Suggestions
Move the Quick Reference tool table (and per-workflow parameter details) into a references/ file such as references/tool-catalog.md, keeping SKILL.md as a concise overview with clearly signaled links.
Deduplicate the pitfalls: priority integer values and team-scoping guidance each appear in both a workflow's Pitfalls block and the global Known Pitfalls section — state each once.
Add a minimal executable example for the GraphQL workflow (a sample query plus variables) and name the actual pagination cursor field instead of "Check for pagination cursors in responses."
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is almost entirely operational content — tool slugs, parameter names, integer mappings — with no explanation of concepts Claude already knows. It is not a 5 because the "Known Pitfalls" section repeats workflow-level pitfalls verbatim (priority integer values, team scoping) and the Quick Reference table duplicates the workflow tool sequences, so it could be meaningfully tightened. | 4 / 5 |
Actionability | Exact tool slugs (e.g. LINEAR_CREATE_LINEAR_ISSUE), named parameters (team_id, state_id, label_ids), the priority integer mapping, and ordered sequences give mostly executable, copy-paste-ready guidance; as an instruction-only MCP skill, absence of code is not penalized. Minor gaps keep it below 5: the GraphQL workflow gives no example query, and pagination says "Check for pagination cursors" without naming the actual cursor parameter. | 4 / 5 |
Workflow Clarity | The setup sequence includes an explicit validation checkpoint ("Confirm connection status shows ACTIVE before running any workflows") and an error-recovery branch (follow the auth link if not ACTIVE), and workflows tag [Prerequisite]/[Optional] steps. It is not a 5 because core workflows lack post-action verification (e.g., confirming a created issue's ID/state), leaving minor validation gaps. | 4 / 5 |
Progressive Disclosure | There are no bundle files at all, and the 19-row Quick Reference tool catalog plus the full parameter details are exactly the content that belongs in a one-level-deep reference file. Section structure is good, but all reference-grade content is inlined in a single 176-line file, matching anchor 3 rather than 4. | 3 / 5 |
Total | 15 / 20 Passed |