CtrlK
BlogDocsLog inGet started
Tessl Logo

linear-tools

Linear project management expert for issues, cycles, projects, and workflow automation

62

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./crates/openfang-skills/bundled/linear-tools/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

87%

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 concise, highly actionable set of Linear management practices with clear sectioning and no unnecessary padding. Its main gap is the absence of any sequenced workflow with validation checkpoints for operations like bulk backlog archiving or automated state transitions.

DimensionReasoningScore

Conciseness

The body is a tight, well-organized bullet list that assumes Claude's competence and avoids explaining what Linear or basic planning concepts are; every bullet carries specific guidance, matching the 'lean and efficient; every token earns its place' anchor.

3 / 3

Actionability

Despite being instruction-only, it gives highly concrete, copy-ready guidance — the `[Area] Brief description` title pattern, P0-P3 priority definitions, two-week cycle duration, label cap under 15, Fibonacci estimates (1,2,3,5,8), and SLA targets (P0: 1 hour) — so the absence of code is not penalized per the scoring notes.

3 / 3

Workflow Clarity

Content is organized into Principles, Techniques, Patterns, and Pitfalls, but there is no sequenced multi-step process or any validation/checkpoint for risky operations (e.g., bulk archiving, state transitions), matching the 'sequence present but checkpoints missing' anchor and below the level-3 explicit-feedback-loop bar.

2 / 3

Progressive Disclosure

The skill is under 50 lines, single-purpose, and has no bundle files in references/scripts/assets, so per the guidelines well-organized sections alone qualify it for the top score; its sectioned structure provides clear navigation.

3 / 3

Total

11

/

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 is specific and clearly anchored to Linear, but it omits any explicit usage trigger and offers only partial coverage of natural keyword variations. Adding a 'Use when...' clause referencing common terms like sprints, backlog, and triage would lift completeness and trigger quality.

Suggestions

Append an explicit trigger clause such as 'Use when managing Linear issues, planning cycles/sprints, triaging a backlog, or automating Linear workflows' to satisfy the completeness dimension.

Broaden trigger terms to include natural user phrasings like 'sprints', 'backlog', 'triage', and 'tickets' alongside 'cycles' and 'issues'.

Reframe the domain nouns as concrete actions (e.g., 'create and triage issues, plan cycles, track projects, automate workflows') to push specificity toward level 3.

DimensionReasoningScore

Specificity

The description names the domain and several concrete objects ("issues, cycles, projects, and workflow automation") but does not enumerate concrete actions like 'extract' or 'merge', matching the 'names domain and some actions, but not comprehensive' anchor rather than the multi-action level-3 example.

2 / 3

Completeness

It states clearly what the skill covers but lacks any explicit 'Use when...' trigger clause; per the judging guidelines a missing explicit trigger caps completeness at 2.

2 / 3

Trigger Term Quality

It includes the natural product term 'Linear' plus 'issues, cycles, projects', but omits common variations a user might actually say ('sprints', 'backlog', 'triage', 'tickets'), fitting the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

'Linear project management expert' ties the skill to a specific named product with distinct triggers, making it unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers' anchor.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
RightNow-AI/openfang
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.