CtrlK
BlogDocsLog inGet started
Tessl Logo

add-linear

Add Linear channel integration via Chat SDK. Issue comment threads as conversations.

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/add-linear/SKILL.md
SKILL.md
Quality
Evals
Security

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 body is highly actionable with executable directives, concrete commands, and explicit validation checkpoints, and it is structured into a clear sequenced workflow. It is concise with only minor redundancy, and relies entirely on inline content since no bundle files are present.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete directives and minimal padding; a few explanatory passages (e.g. the OAuth-vs-API-key rationale repeated across sections) could be trimmed slightly.

4 / 5

Actionability

Fully executable throughout: copy/append/dep/run directives with exact paths, copy-paste-ready CLI commands, and concrete env templates covering both the OAuth and Personal API-key paths.

5 / 5

Workflow Clarity

Clear multi-step sequence (Apply → Credentials → Wiring → Next Steps) with explicit validation ('Both must be clean before proceeding', the registration test as a feedback loop) and recovery guidance in Troubleshooting.

5 / 5

Progressive Disclosure

Well-organized single-file skill with clear section headers and inline directive fences acting as navigation; no external bundle files exist, so most content is appropriately inline with only minor cases (e.g. GitHub skill cross-reference) that could be clearer.

4 / 5

Total

18

/

20

Passed

Description

51%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 clearly names its Linear-specific niche and a concrete action, but omits any explicit 'when to use' trigger guidance. Specificity is adequate rather than comprehensive, listing only one concrete action.

Suggestions

Add an explicit 'Use when...' clause (e.g. 'Use when adding Linear as a messaging channel or when the user wants the agent to respond in Linear issue comments').

Broaden the concrete actions beyond one (e.g. mention webhook setup, credential wiring, and team routing) to raise specificity.

Include natural synonyms users might say such as 'Linear issues', 'Linear app', or 'Linear bot' to improve trigger coverage.

DimensionReasoningScore

Specificity

Names the domain (Linear, Chat SDK) and one concrete action ('Issue comment threads as conversations') but does not list multiple specific actions like creating webhooks or wiring credentials.

3 / 5

Completeness

It states what the skill does but contains no 'Use when...' clause or equivalent trigger guidance, so the 'when' is missing; per the rubric a missing explicit trigger caps completeness at 3 and the bare 'what' alone sits at 2.

2 / 5

Trigger Term Quality

Strong natural terms ('Linear', 'channel integration', 'comment threads', 'conversations') that a user would naturally say, with only minor variations (e.g. 'issues', 'Linear app') missing.

4 / 5

Distinctiveness Conflict Risk

A clear Linear-specific niche with distinct triggers; minimal risk of confusing it with other channel-integration skills.

5 / 5

Total

14

/

20

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
nanocoai/nanoclaw
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.