CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

linear

Search, read, create, and update the user's Linear issues, projects, and comments through their own Linear connection.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

A lean, highly actionable skill with executable curl examples, an explicit approval gate for writes, and good error/pagination checkpoints. The main gaps are a missing update-state mutation example and no explicit verification of mutation success before reporting results.

Suggestions

Add an issueUpdate mutation example (e.g. changing state) since updates are advertised but only creates are shown.

Instruct the agent to check the mutation response's `success` field and `errors` before reporting the identifier/url to the user.

If the skill grows (cycles, labels, more entities), move extended query examples to a reference file and signal it clearly from SKILL.md.

DimensionReasoningScore

Conciseness

Every section earns its place: the auth paths, error handling ("tell the user they need to connect Linear and stop"), and curl examples carry no padding, and it delegates composio details to "the composio skill's 'Raw requests' section" instead of re-explaining. This matches the lean anchor; there is no over-explanation to trim, so it is not 4.

5 / 5

Actionability

Copy-paste-ready curl commands cover search, single-issue read, team listing, issue creation, and commenting, matching mostly-executable guidance. It falls short of anchor 5 because updates are promised ("changing state is a write") but no issueUpdate/state-change mutation example is provided — a minor gap in covering common cases.

4 / 5

Workflow Clarity

The flow is clear (find/read → approval gate "summarize what it will create/change ... and ask for approval" → write → "Always report the resulting issue/comment identifier and url"), with checkpoints for pagination ("if pageInfo.hasNextPage is true, re-query") and auth failure (401/400 handling). It is not 5 because there is no explicit instruction to check the mutation response's success/errors payload before reporting, and the update flow has no example — minor validation gaps.

4 / 5

Progressive Disclosure

The body is well-sectioned ("Find / read issues", "Writes require approval") with all content appropriately inline for a single-file skill of this size; nothing clearly belongs in a separate file. It is not 5 because at ~90 lines it exceeds the under-50-line simple-skill exception, and the full operation reference is inlined with no signaling of where deeper material would live if the skill grew.

4 / 5

Total

17

/

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 specific, distinctive description with comprehensive action coverage, undermined only by the complete absence of a "when to use" trigger clause and a few missing synonyms like "tickets". Adding an explicit trigger sentence would lift it substantially.

Suggestions

Add a "Use when..." clause, e.g. "Use when the user mentions Linear, issues, tickets, cycles, or their team's work tracking."

Include the synonym "tickets" for issues and mention "cycles" so natural user phrasing matches the description.

Consider mentioning team/project work tracking contexts to broaden trigger coverage without adding vagueness.

DimensionReasoningScore

Specificity

"Search, read, create, and update" enumerates four concrete actions applied to "issues, projects, and comments", giving comprehensive CRUD coverage of the domain's core entities. This matches the anchor for multiple specific concrete actions with comprehensive coverage; it is not score 4 because the action list is complete rather than having minor gaps.

5 / 5

Completeness

The "what" is clear (search/read/create/update Linear issues, projects, comments) but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guideline. It is not 4 because the "when" is entirely absent rather than present but imprecise.

3 / 5

Trigger Term Quality

Natural terms like "Linear", "issues", "projects", and "comments" are present and would be said by users. It falls short of anchor 5 because common synonyms such as "tickets" (a frequent user word for issues) and "cycles" are missing.

4 / 5

Distinctiveness Conflict Risk

"the user's Linear issues, projects, and comments through their own Linear connection" names a clear niche with Linear-specific triggers, so the risk of triggering for the wrong skill is minimal. No neighboring anchor fits better.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

yc-software/qm

Path

skills-seed/linear/SKILL.md

Reviewed

Table of Contents

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.