Content
56%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides solid actionable guidance with concrete CLI commands and script examples for Linear management, but is significantly undermined by poor editing — the 'When to Use This Skill' block is duplicated 5 times verbatim, and substantial content is repeated across sections. The progressive disclosure structure references appropriate external files but fails to actually move detailed content out of the main file, resulting in a bloated document that would benefit greatly from trimming and deduplication.
Suggestions
Remove all duplicate 'When to Use This Skill' blocks — this identical text appears 5 times and should appear at most once (or zero times if it's already in frontmatter).
Move the detailed 'Project Management Commands' reference section (project-status, link-initiative, unlink-initiative with their tables and examples) into projects.md, keeping only a brief summary with a link in the main SKILL.md.
Consolidate the overlapping project workflow content — the 'Project Planning Workflow', 'Complete Project Lifecycle Example', and 'Projects & Initiatives quick reference' sections all cover similar ground and should be merged or split clearly between SKILL.md overview and projects.md detail.
Add brief verification steps after key operations (e.g., 'Verify: `linear issues view ENG-XXX` to confirm creation') to improve workflow reliability.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is severely bloated with repeated 'When to Use This Skill' blocks (appearing 5 times with identical text), redundant sections covering the same commands in multiple places (e.g., project-status commands appear in both the workflow section and the command reference), and unnecessary explanations like 'Why This Matters' that Claude can infer. The content could easily be cut by 40-50%. | 2 / 5 |
Actionability | The skill provides concrete, executable CLI commands and script invocations throughout. Most operations have copy-paste ready examples with specific arguments. Minor gaps include the MCP tool usage which shows pseudo-syntax ('update_issue with id=...') rather than actual MCP tool call format, and some commands reference scripts without showing their full paths consistently. | 4 / 5 |
Workflow Clarity | The 'Complete Project Lifecycle Example' provides a clear numbered sequence from project creation through completion. The project planning workflow has good step-by-step guidance. However, validation/verification steps are mostly absent — there's no explicit 'verify the issue was created' or error recovery steps after operations. Since these aren't destructive/batch operations in the XML-manipulation sense, the missing validation doesn't trigger the cap at 3, but it's still a gap. | 4 / 5 |
Progressive Disclosure | The skill references multiple external files (api.md, sdk.md, sync.md, projects.md, troubleshooting.md, docs/labels.md) and has a reference table at the bottom, which is good. However, the main SKILL.md itself is overloaded with content that belongs in those referenced files (e.g., the full project-status command reference, the complete project lifecycle example, detailed MCP configuration). The inline content and referenced content likely overlap significantly. | 3 / 5 |
Total | 13 / 20 Passed |