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

81%

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

88%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 highly actionable with executable GraphQL examples and a well-sequenced, validated bootstrap workflow. Minor conciseness trims and an optional split of API patterns into a reference file would push it higher.

Suggestions

Remove the redundant restatement about not passing viewer.id inline (already covered in the preceding pattern note).

Consider moving the seven API pattern examples into a references/ file, keeping only the bootstrap and key patterns inline in SKILL.md.

Tighten the identity cache YAML example to the minimum fields needed to convey the shape.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's knowledge of GraphQL/Linear, with a few redundant sentences (e.g., repeated 'never pass viewer.id inline') and a detailed cache YAML example that could be trimmed.	4 / 5
Actionability	Provides fully executable, copy-paste-ready http() calls with complete parameterized GraphQL queries covering list, search, create, update, and get-by-id.	5 / 5
Workflow Clarity	The bootstrap flow is a numbered sequence with explicit validation checkpoints (stale cache check, stop condition) and a feedback loop for HTTP 401 / AuthenticationError recovery.	5 / 5
Progressive Disclosure	Well-organized into clear sections with one-level-deep structure and no nested references, though the seven inline API patterns could arguably be split into a separate reference file.	4 / 5
	Total	18 / 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.

The description is specific and clearly distinctive, but lacks an explicit 'Use when...' trigger clause, which caps completeness. Adding concrete trigger guidance and a few synonym terms would raise the score.

Suggestions

Add an explicit 'Use when ...' clause listing trigger scenarios (e.g., listing/creating/updating Linear issues, 'my Linear issues' requests).

Include natural synonym terms users say — 'Linear tickets', 'Linear backlog', 'linear.app' — to broaden trigger coverage.

Keep the concrete capability list; it is already strong on specificity.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — identity bootstrap, raw GraphQL list/search/create/update, and assignee-filter rules — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	The 'what' is clear and concrete, but there is no explicit 'Use when...' clause; the 'when' is only weakly implied, so per the rubric completeness is capped at 3.	3 / 5
Trigger Term Quality	Includes natural phrases users say ('my issues', 'assigned to me', 'Linear issue tracker') but omits common synonyms like 'Linear tickets', 'backlog', and the linear.app extension.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Linear specifically) with distinct triggers and explicit exclusion of competing trackers, yielding minimal conflict risk.	5 / 5
	Total	17 / 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: nearai/ironclaw
Path: skills/linear/SKILL.md
Commit: 2831516

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