CtrlK
BlogDocsLog inGet started
Tessl Logo

linear

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

72

1.58x
Quality

61%

Does it follow best practices?

Impact

84%

1.58x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.codex/skills/linear/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

64%

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

This is a solid, highly actionable skill with executable GraphQL examples covering a good range of Linear operations. Its main weaknesses are verbosity from redundant query variants and a lack of explicit error-handling/validation checkpoints in multi-step workflows. The content would benefit from splitting detailed query catalogs into a separate reference file and adding feedback loops for failure scenarios.

Suggestions

Add explicit error-handling guidance: what to check after each GraphQL call (inspect `errors` array, verify `success` field), and what to do on failure (retry, introspect schema, etc.) — especially for the multi-step upload workflow.

Consolidate the four issue lookup queries into one or two with inline comments noting which fields to add/remove, or move the full catalog to a separate REFERENCE.md file.

Move introspection patterns and less-common workflows to a separate file (e.g., INTROSPECTION.md or REFERENCE.md) and link from the main skill to keep it concise.

DimensionReasoningScore

Conciseness

The skill is mostly efficient and avoids explaining what GraphQL is or how Linear works, but it includes many similar query variants (e.g., four different issue lookup queries that are largely redundant) and some introspection examples that could be consolidated. The content could be tightened by ~30% without losing actionability.

2 / 3

Actionability

Every workflow includes fully executable GraphQL queries and mutations with proper variable declarations. The tool input format is clearly specified with a concrete JSON example, and the upload workflow provides a clear three-step process with the exact mutation and curl approach.

3 / 3

Workflow Clarity

The upload workflow has a clear three-step sequence, and the state transition workflow correctly instructs to fetch states first. However, there are no explicit validation checkpoints or error-handling feedback loops — e.g., no guidance on what to do if fileUpload fails, if the curl upload returns an error, or if a GraphQL errors array is returned beyond the initial mention to treat it as failure.

2 / 3

Progressive Disclosure

The content is well-structured with clear section headers and logical grouping, but it's a long monolithic file (~250 lines) with no references to external files. The many query variants and introspection patterns could be split into a reference file, keeping the SKILL.md as a concise overview with links to detailed examples.

2 / 3

Total

9

/

12

Passed

Description

57%

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 identifies a clear niche (raw Linear GraphQL operations via a specific client tool) and mentions a couple of concrete use cases, giving it good distinctiveness. However, it lacks an explicit 'Use when...' clause and could benefit from more comprehensive action listing and natural trigger terms that users would actually say.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to perform raw GraphQL queries against Linear, edit comments on Linear issues, or handle file upload flows via the Linear API.'

Expand trigger terms with natural user language such as 'Linear API', 'Linear query', 'issue comments', 'attachments', 'file uploads' to improve matching.

DimensionReasoningScore

Specificity

Names the domain (Linear GraphQL operations via Symphony's linear_graphql client tool) and mentions some actions (comment editing, upload flows), but the list is not comprehensive and 'raw Linear GraphQL operations' is somewhat vague.

2 / 3

Completeness

Answers 'what' (raw Linear GraphQL operations like comment editing and upload flows) but lacks an explicit 'Use when...' clause or equivalent trigger guidance, capping this at 2 per the rubric.

2 / 3

Trigger Term Quality

Includes relevant keywords like 'Linear', 'GraphQL', 'comment editing', 'upload flows', and 'linear_graphql', but misses common user-facing variations (e.g., 'Linear API', 'Linear query', 'issue comments', 'file upload'). The term 'Symphony' is internal/technical and may not be what users naturally say.

2 / 3

Distinctiveness Conflict Risk

The description is quite specific to a particular tool ('Symphony's linear_graphql client tool') and a narrow domain (raw Linear GraphQL operations), making it clearly distinguishable from other skills and unlikely to conflict.

3 / 3

Total

9

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
openai/symphony
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.