linear

Use Symphony's `linear_graphql` client tool for raw Linear GraphQL operations such as comment editing and upload flows.

1.58x

Quality

68%

Does it follow best practices?

Impact

84%

1.58x

Average score across 3 eval scenarios

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.codex/skills/linear/SKILL.md

The canonical home for this skill is linear in openai/symphony

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.

The body is a dense, highly actionable set of executable Linear GraphQL recipes with clear workflows and good structure, assuming Claude's competence throughout. Its only real weakness is moderate redundancy across issue-lookup variants and a large inline reference surface that could be split out.

Dimension	Reasoning	Score
Conciseness	Mostly executable GraphQL with tight, purposeful prose and no padding about concepts Claude already knows; the four overlapping issue-lookup queries share redundant field selections that could be trimmed, keeping it just below a 5.	4 / 5
Actionability	Every code block is a complete, copy-paste-ready GraphQL operation with typed variables, and the examples cover the common cases (issue lookup, comment create/edit, state move, PR/URL attachment, file upload).	5 / 5
Workflow Clarity	Multi-step flows are clearly sequenced (the 3-step video upload, fetch-team-states-then-update pattern) with the global "top-level errors array = failed operation" checkpoint; not a 5 because the upload flow lacks an explicit error-recovery/feedback loop.	4 / 5
Progressive Disclosure	Well-organized into clearly headed sections (Primary tool, Discovering operations, Common workflows, Usage rules) with easy navigation and no nested references; not a 5 because ~390 lines of GraphQL recipes are inlined in SKILL.md with no split-out reference file despite the volume.	4 / 5
	Total	17 / 20 Passed

Description

53%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 distinct, naming a concrete tool and two representative actions, but it omits any explicit "Use when..." trigger guidance and offers only thin natural-keyword coverage.

Suggestions

Add an explicit trigger clause, e.g. "Use when you need raw Linear GraphQL operations like comment edits or file uploads during a Symphony session."

Broaden natural keywords to include terms users actually say (e.g. "edit a Linear comment", "attach a PR to a Linear issue", "upload a video to a Linear comment").

List a few more concrete actions (issue lookup, state transitions, attachments) to lift specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Names the tool ("Symphony's `linear_graphql` client tool") and domain ("raw Linear GraphQL operations") with two concrete actions ("comment editing and upload flows"), matching the anchor for 1-2 concrete actions without comprehensive coverage; not a 4 because only two actions are named via "such as".	3 / 5
Completeness	Has a clear "what" (use the linear_graphql tool for raw GraphQL operations) but no explicit "Use when..." trigger clause, so per the guideline a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Relevant keywords ("Linear GraphQL", "comment editing", "upload flows") are present but lean technical and lack common natural variations/synonyms a user might say; not a 4 because natural phrasing coverage is thin.	3 / 5
Distinctiveness Conflict Risk	Tied to a specific named tool ("Symphony's `linear_graphql`") with a clear Linear-GraphQL niche, making it mostly distinct with only minor overlap risk against other Linear skills; not a 5 because "raw GraphQL operations" is broad enough to brush related skills.	4 / 5
	Total	13 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: karanhudia/borg-ui
Path: .codex/skills/linear/SKILL.md
Commit: c7f32d1

Reviewed: 1 day 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.