Name: linear
Rating: 61.6 (1 reviews)
Author: membranedev

linear

Linear integration. Manage Issues, Projects, Teams, Users, Cycles, Labels and more. Use when the user wants to interact with Linear data.

Quality

73%

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 ./skills/linear/SKILL.md

Quality

Content

71%Weight 40%Scale 1-5

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

Highly actionable with executable commands and a well-sequenced connection workflow, but it is held back by an over-long inline action table, some redundant explanatory prose, and no external reference files for progressive disclosure.

Suggestions

Move the Popular actions table into a separate reference file (e.g., ACTIONS.md) and keep only a handful of examples inline.

Add a validation/verification checkpoint after destructive or batch actions like delete-issue and update-issue.

Trim the opening 'Linear is a project management tool...' paragraph since Claude already knows what Linear is.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but the Popular actions table repeats 19 actions already discoverable via `membrane action list`, and the opening paragraph restates what Linear is — knowledge Claude already has.	3 / 5
Actionability	Provides copy-paste-ready CLI commands for install, login, connection ensure, polling, action search/run, and proxy requests, with flag tables covering the common cases.	5 / 5
Workflow Clarity	The connection setup flow is clearly sequenced with state checks (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a polling loop, but post-action verification and error-recovery feedback for batch/destructive actions (e.g., delete-issue, update-issue) are absent.	4 / 5
Progressive Disclosure	Has clear section structure but everything lives inline in SKILL.md with no bundle files; the large Popular actions table and reference-style flag options are content that could be split into a separate reference file.	3 / 5
	Total	15 / 20 Passed

Description

75%Weight 40%Scale 1-5

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 solid, mostly third-person description that names concrete entities and provides an explicit trigger clause. It is held back from a 5 by the generic 'and more' phrasing and missing synonyms like 'sprints' or 'tickets'.

Suggestions

Replace 'and more' with concrete additional actions or drop it to avoid over-claiming.

Add common synonyms such as 'sprints (Cycles)' and 'tickets' to broaden natural trigger coverage.

Tighten the 'Use when' clause with a couple of concrete scenarios (e.g., creating issues, planning sprints).

Dimension	Reasoning	Score
Specificity	Lists several concrete managed entities ('Manage Issues, Projects, Teams, Users, Cycles, Labels'), giving clear specific actions, though it stops at a list rather than enumerating per-entity operations.	4 / 5
Completeness	Has a clear 'what' (manage the listed Linear entities) and an explicit 'Use when the user wants to interact with Linear data' trigger, though the 'when' could be more specific about scenarios.	4 / 5
Trigger Term Quality	Includes natural terms users say ('Linear', 'Issues', 'Projects', 'Cycles', 'interact with Linear data') with good coverage, but misses common synonyms like 'sprints' or 'tickets'.	4 / 5
Distinctiveness Conflict Risk	The Linear-specific naming gives it a clear niche with minimal conflict risk, though the generic 'Manage... and more' tail slightly broadens it toward other project-management skills.	4 / 5
	Total	16 / 20 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/linear/SKILL.md
Commit: f484c82

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