Name: linear-claude-skill
Rating: 43.2 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

linear-claude-skill

Manage Linear issues, projects, and teams

Quality

45%

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/AI-Agents-Safe-Coding-Skills-claude/skills/linear-claude-skill/SKILL.md

The canonical home for this skill is linear-claude-skill in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

50%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.

The content is rich with executable Linear commands and clear planning workflows, but it is heavily padded with duplicated boilerplate, lacks validation checkpoints for its batch/destructive operations, and references bundle files that do not exist. Tightening redundancy and adding real referenced files would materially improve it.

Suggestions

Remove the five duplicated 'When to Use This Skill' blocks and consolidate project-status command examples into a single reference to cut the body's token cost.

Add explicit validation/verification steps to batch and lifecycle workflows (e.g. confirm an issue exists and check its current state before bulk-updating status, verify the project was created before adding issues).

Create the referenced bundle files (api.md, sdk.md, sync.md, projects.md, troubleshooting.md, docs/labels.md, scripts/linear-ops.ts) or remove the dangling references so progressive disclosure reflects the actual bundle structure.

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose: the 'When to Use This Skill' boilerplate ('Manage Linear issues... Use this skill when working with manage linear issues, projects, and teams.') is duplicated five times, project-status usage is repeated across multiple sections, and headings are merged mid-paragraph, leaving several padded, redundant sections. It is not a 1 because the command references themselves are not preamble-style concept explanations.	2 / 5
Actionability	The skill provides concrete, executable commands (linear issues create --title, npx tsx scripts/linear-ops.ts ..., MCP server JSON config) covering common operations copy-paste ready, with only minor gaps such as needing to look up STATE_IDs. It falls short of 5 because some examples use ENG-XXX placeholders and a few commands lack complete argument details.	4 / 5
Workflow Clarity	Sequenced workflows exist (Project Planning Workflow, the numbered Complete Project Lifecycle Example), but the skill performs batch and destructive operations (bulk status Done on multiple issues, project lifecycle changes) without explicit validation checkpoints or verify-before-proceeding feedback loops, so per the batch/destructive cap it cannot exceed 3 even though the sequence is otherwise clear.	3 / 5
Progressive Disclosure	There is a Reference table and inline pointers to api.md, sdk.md, sync.md, projects.md, troubleshooting.md, and scripts, but none of these bundle files actually exist in references/ or scripts/, so the one-level-deep structure is aspirational rather than real and the bulk of guidance is inlined in SKILL.md. It is not a 4 because the claimed external files are missing and the body carries content that should live in those separate files.	3 / 5
	Total	12 / 20 Passed

Description

41%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.

The description is brief and domain-specific but generic in its actions and lacks any 'when to use' trigger guidance, capping completeness. It identifies Linear clearly enough to avoid most conflicts, yet does not list concrete operations or natural trigger phrases.

Suggestions

Add concrete actions to the description, e.g. 'Create and update Linear issues, manage project status, and link projects to initiatives'.

Append an explicit trigger clause such as 'Use when working with Linear issues, projects, teams, sprints, or when the user mentions Linear tickets'.

Include natural user-language terms ('Linear ticket', 'sprint', 'move to Done') to improve trigger-term quality.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Manage Linear issues, projects, and teams') but lists only the entity types rather than concrete actions such as create, update, or link, fitting the 'names the domain but actions are minimal or generic' anchor better than the score-3 anchor which requires 1-2 concrete actions.	2 / 5
Completeness	It has a clear 'what' ('Manage Linear issues, projects, and teams') but no 'Use when...' or equivalent trigger clause, so per the missing-trigger guideline completeness is capped at 3, and it is not a 4 because 'when' is entirely absent rather than weakly implied.	3 / 5
Trigger Term Quality	It surfaces a couple of generic keywords (Linear, issues, projects, teams) but omits the natural phrases users actually say ('create a Linear issue', 'move tickets to Done', 'update my sprint'), matching the 'one or two generic keywords; missing natural phrases' anchor.	2 / 5
Distinctiveness Conflict Risk	Naming 'Linear' specifically carves out a clear niche with minimal conflict risk, though the broad 'issues, projects, and teams' wording leaves minor overlap with general project-management skills, so it sits at 'mostly distinct; minor overlap risk' rather than a 5.	4 / 5
	Total	11 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (543 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 40 missing	Warning

	Total	13 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/linear-claude-skill/SKILL.md
Commit: 57c135b

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