linear

Linear issue tracker API integration. Covers first-use identity bootstrap (viewer + teams cached), raw GraphQL for list/search/create/update, and the rules for handling "my issues" / "assigned to me" requests.

Quality

87%

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

Quality

Content

92%

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

A highly actionable, concise skill body with executable GraphQL examples and a well-sequenced bootstrap workflow including error recovery. The only weakness is progressive disclosure: all reference material lives inline with no file separation despite the skill's length.

Suggestions

Move the API Patterns query catalog into a separate `references/linear-api-reference.md` and keep SKILL.md as an overview with a one-level-deep pointer, raising progressive_disclosure to 3.

If keeping everything inline, add a short table of contents or 'See API Patterns below' navigation cues so the reference section is clearly signaled.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it never explains what GraphQL or Linear is, and prose like the identity-bootstrap rationale ('avoids re-fetching viewer... makes filter-by-assignee queries deterministic') conveys non-obvious API-specific behavior rather than padding.	3 / 3
Actionability	Every API pattern is a complete, copy-paste-ready `http(...)` call with concrete GraphQL queries and variables (list, search, create, update, get-by-id), fully executable rather than pseudocode.	3 / 3
Workflow Clarity	The bootstrap flow is a numbered 5-step sequence with an explicit error-recovery checkpoint (step 5: 'On HTTP 401 or an AuthenticationError... invalidate the cache and re-prompt'), giving clear sequencing and a feedback loop.	3 / 3
Progressive Disclosure	Content is well-sectioned but entirely inline in a ~120-line SKILL.md with no bundle files; the seven-query API Patterns block is reference material that could be split into a separate REFERENCE file, matching the 'content that should be separate is inline' anchor.	2 / 3
	Total	11 / 12 Passed

Description

82%

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, third-person description that names concrete capabilities and natural trigger phrases, clearly distinguishable as a Linear-only integration. Its main gap is the absence of an explicit 'Use when...' clause, which caps completeness.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when the user asks about Linear issues, tickets, or assignments') to lift completeness to 3.

Mirror the 'my issues' / 'assigned to me' trigger phrasing directly in an explicit usage trigger so the 'when' is stated, not implied.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — "first-use identity bootstrap (viewer + teams cached)", "raw GraphQL for list/search/create/update", and "handling 'my issues' / 'assigned to me' requests" — matching the 'lists multiple specific concrete actions' anchor; it is not merely naming a domain.	3 / 3
Completeness	It clearly states what the skill does but lacks an explicit 'Use when...' clause; the 'when' is only implied via the 'my issues' / 'assigned to me' phrasing, so per the guidelines completeness caps at 2 rather than 3.	2 / 3
Trigger Term Quality	It includes natural phrasings a user would actually say — "my issues", "assigned to me", and "Linear issue tracker" — giving good coverage rather than only technical jargon.	3 / 3
Distinctiveness Conflict Risk	'Linear issue tracker API integration' is a clear, narrow niche tied to a specific product, making it unlikely to trigger for the wrong skill.	3 / 3
	Total	11 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nearai/ironclaw
Path: skills/linear/SKILL.md
Commit: b60038b

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