linear

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

1.48x

Quality

75%

Does it follow best practices?

Impact

92%

1.48x

Average score across 5 eval scenarios

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

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

Quality

Content

50%

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

The skill is well-structured and gives genuinely executable setup guidance, but the core operating workflow is more descriptive than actionable and lacks validation checkpoints for its batch operations. Existing bundle assets are not wired into the body, leaving progressive disclosure underdeveloped.

Suggestions

Add concrete, executable examples or required-field signatures for the main workflow steps (e.g., a sample create_issue call with team key, title, priority) so the guidance is copy-paste ready, not just descriptive.

Insert explicit validation checkpoints for batch/destructive operations in Steps 3-4 (e.g., 'after bulk create, list_issues to confirm counts before proceeding'), which would raise workflow_clarity.

Reference the bundled assets (assets/linear.png / linear.svg) from the body where relevant, or split the nine Practical Workflows and tool signatures into a reference file linked one level deep, to improve progressive disclosure and signal the existing bundles.

Dimension	Reasoning	Score
Conciseness	The body avoids re-explaining what Linear/issue tracking is, but the nine-item Practical Workflows list and the Tips section restate approach descriptively rather than giving lean, token-earning guidance; it could be tightened.	2 / 3
Actionability	Step 0 gives concrete, copy-paste-ready commands and a WSL config, but the core workflow (Steps 1-4) and Available Tools are abstract ('Execute Linear MCP tool calls in logical batches', tool names without signatures or required fields), leaving key executable detail missing.	2 / 3
Workflow Clarity	Steps 0-4 are clearly numbered with an explicit ordering cue and the MCP-setup branch has a feedback loop, but the batch create/update operations in Steps 3-4 lack explicit validate-then-verify checkpoints, which the rubric caps at 2 for batch/destructive work.	2 / 3
Progressive Disclosure	Sections are well-organized, but the skill is a single monolithic file with no one-level-deep references; the bundled assets (assets/linear.png, assets/linear.svg) exist yet are never signaled or linked from the body, and tool/workflow detail that could be split out is inline.	2 / 3
	Total	8 / 12 Passed

Description

100%

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 strong, well-formed description that clearly states capabilities and an explicit 'Use when' trigger tied to a distinct product. The only nit is the minor grammar slip 'updates' instead of 'update', which does not change any anchor level.

Dimension	Reasoning	Score
Specificity	The description names multiple concrete actions ('Manage issues, projects & team workflows', 'read, create or updates tickets') rather than vague language, matching the top anchor.	3 / 3
Completeness	It explicitly answers both what ('Manage issues, projects & team workflows in Linear') and when ('Use when the user wants to read, create or updates tickets in Linear'), with an explicit trigger clause.	3 / 3
Trigger Term Quality	It uses natural terms a Linear user would say ('issues, projects, tickets', 'read, create or updates') alongside the Linear brand, giving good coverage of likely user phrasing.	3 / 3
Distinctiveness Conflict Risk	Tied to a distinct product niche (Linear) with brand-specific triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: openai/skills
Commit: 49f948f

Reviewed: 19 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.