linear-graphql

Call the Linear GraphQL API from agent sessions in this repo — authenticate via LINEAR_API_KEY loaded from .env.local without tripping the Freebuff env guard, use shorthand issue IDs, avoid the IssueFilter/ID-typing schema traps, and flip issues or query state with scripts/linear-flip-done.mjs.

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/linear-graphql/SKILL.md

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 highly actionable, well-structured skill body with executable code and clear sequencing; minor conciseness and validation-loop gaps prevent a perfect score.

Dimension	Reasoning	Score
Conciseness	Efficient and focused on Linear/repo-specific gotchas Claude would not know, but the inline dotenv-parsing regex block and explanatory code comments are minor instances that could be trimmed.	4 / 5
Actionability	Fully executable, copy-paste-ready code: the loader plus gql wrapper, the concrete `node scripts/linear-flip-done.mjs VAU-10 VAU-12` command, and the `freebuff-env set` command cover the common cases completely.	5 / 5
Workflow Clarity	Clear numbered sequence (ensure key → reuse helper → copy loader → housekeeping) with validation checkpoints in code (errors-array check, completed-state existence check, fallback loader); only a minor gap in that there is no explicit verify-after-flip feedback loop.	4 / 5
Progressive Disclosure	Well-organized into Knowledge, numbered Instructions, and Housekeeping sections with a signaling table for repo scripts and no nested references; the large inline loader/gql template is justified but keeps this just below the 5-anchor.	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 strong concrete actions and natural keywords, but it lacks an explicit 'Use when...' trigger clause, which caps completeness at 3.

Suggestions

Add an explicit trigger clause, e.g. 'Use when a task needs to read or mutate Linear issues, states, or projects from a terminal session in this repo.'

Include common synonyms such as 'tickets' or 'tasks' alongside 'issues' to broaden natural trigger coverage.

Keep the concrete action list but ensure the 'when' guidance is as explicit as the 'what' currently is.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Call the Linear GraphQL API', 'authenticate via LINEAR_API_KEY loaded from .env.local', 'use shorthand issue IDs', 'avoid the IssueFilter/ID-typing schema traps', 'flip issues or query state with scripts/linear-flip-done.mjs' — matching the comprehensive-coverage anchor.	5 / 5
Completeness	The 'what' is explicit and concrete, but there is no 'Use when...' clause or equivalent explicit trigger guidance; 'from agent sessions in this repo' is a scope constraint, not a trigger, so completeness is capped at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Strong natural keywords ('Linear GraphQL API', 'issues', 'flip issues', 'query state', 'LINEAR_API_KEY') that users would say, but missing common synonyms like 'tickets' or 'tasks' for the 5-anchor.	4 / 5
Distinctiveness Conflict Risk	Highly specific niche — 'Linear GraphQL API', 'Freebuff env guard', 'scripts/linear-flip-done.mjs' — with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
referenced_paths_exist	Referenced path issues: 4 missing	Warning

	Total	14 / 16 Passed

Repository: pvnkmnk/vault-memory
Path: .agents/skills/linear-graphql/SKILL.md
Commit: 8171052

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.