linear

Manage issues, projects & team workflows in Linear. Use when the user wants to read, create or updates tickets in Linear.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/linear/skills/linear/SKILL.md

Quality

Content

50%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An organized instruction-only skill with a clear workflow and concrete tool inventory, but it is somewhat verbose, lacks tool-field specifics, omits an explicit validation checkpoint before batch operations, and keeps detail inline rather than splitting it into referenced files.

Suggestions

Add an explicit verification checkpoint in Step 3 before batch/bulk applies (e.g., list and confirm the planned changes with the user, then apply), so the workflow earns a feedback loop for batch operations.

Specify the required fields/parameters for the key tool calls (e.g., create_issue needs team key, title, description, priority, labels) instead of only naming the tools, to make the guidance fully actionable.

Trim generic 'Tips for Maximum Productivity' and 'Troubleshooting' advice Claude already knows (rate-limit batching, clearing cookies) and consider moving the detailed Practical Workflows into a references/ file, keeping SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, but the Overview and Prerequisites restate the frontmatter description, and 'Tips for Maximum Productivity'/'Troubleshooting' include generic guidance (rate limits, clearing cookies, refreshing tokens) Claude already knows, so it lands at 'could be tightened' rather than every-token-earns-its-place.	2 / 3
Actionability	Concrete Linear tool names are listed and example sprint names are given, but the Practical Workflows stay high-level and required tool fields/parameters (e.g., the fields create_issue needs) are never specified, leaving the guidance incomplete.	2 / 3
Workflow Clarity	A clear ordered Step 0–4 sequence is present with a retry loop in Step 0, but Step 3's batch operations lack an explicit verify-before-apply validation checkpoint, which per the guideline caps this dimension at 2.	2 / 3
Progressive Disclosure	Sections are well labeled, but the file is a ~73-line monolith with no references/ or scripts/ bundle and no external references, while detailed Practical Workflows and Troubleshooting that could be split out remain inline — placing it above the 'under 50 lines, no refs needed' bar for a 3.	2 / 3
	Total	8 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A concise, well-scoped description that clearly states both capabilities and an explicit trigger, anchored to the distinct Linear domain. A minor grammatical slip ('or updates' should read 'or update') does not affect scoring.

Dimension	Reasoning	Score
Specificity	Names the domain (issues, projects, team workflows in Linear) alongside multiple concrete actions ('read, create or updates tickets'), matching the anchor listing several specific actions rather than a single vague one.	3 / 3
Completeness	Explicitly answers what it does ('Manage issues, projects & team workflows in Linear') and when to use it via an explicit 'Use when the user wants to read, create or updates tickets in Linear' clause.	3 / 3
Trigger Term Quality	Uses natural Linear vocabulary users would actually say — 'issues', 'tickets', 'projects', 'team workflows' — giving good coverage rather than jargon-only or generic terms.	3 / 3
Distinctiveness Conflict Risk	Scoping every action to Linear gives a clear niche with distinct triggers that are unlikely to fire for an unrelated skill.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: openai/plugins
Path: plugins/linear/skills/linear/SKILL.md
Commit: 11c74d6

Reviewed: 17 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.