add-linear

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

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

77%Weight 40%Scale 1-3

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 a clearly sequenced, validated workflow and concrete executable directives. Its main weaknesses are a monolithic single-file structure with no progressive disclosure to bundle references and time-sensitive version pinning that slightly penalizes conciseness.

Suggestions

Move stable but bulky material (Channel Info, Troubleshooting, credential/env templates) into a references file linked one level deep from the body to improve progressive disclosure.

Isolate the pinned dependency version ('@chat-adapter/linear@4.29.0') in a small 'versions' or 'pinned deps' block and note it may drift, so time-sensitive data does not penalize the main conciseness.

Trim a few of the rationale prose passages (e.g. the wiring 'sender policy' and engage-mode explanations) to the essential rule, keeping the actionable directive front and center.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and assumes Claude's competence (no condescending explanations of what Linear or webhooks are), but the pinned version '@chat-adapter/linear@4.29.0' is time-sensitive information not placed in a deprecated/old-patterns section, and several prose passages around wiring rationale could be tightened, fitting the 'mostly efficient but includes some unnecessary explanation or could be tightened' anchor rather than fully lean.	2 / 3
Actionability	Guidance is fully executable and copy-paste ready: exact 'nc:' directives, precise commands ('pnpm run build', 'ncl messaging-groups create --channel-type linear ...' with full flags), concrete env-var names, and real URLs, matching the 'fully executable code/commands; specific examples; copy-paste ready' anchor.	3 / 3
Workflow Clarity	The Apply/Credentials/Wiring/Next Steps flow is clearly sequenced with explicit validation checkpoints ('Both must be clean before proceeding', build-before-test gating, the registration test as a drift detector) plus a Troubleshooting recovery section, matching the 'clear sequence with explicit validation steps; feedback loops for error recovery' anchor.	3 / 3
Progressive Disclosure	The skill is well-organized into clear sections but is a monolithic ~200-line SKILL.md with no bundle files (references/scripts/assets are absent) and no one-level-deep external references; content that could be split out (Channel Info, Troubleshooting, credential templates) is all inline, fitting the 'some structure but content that should be separate is inline' anchor rather than a 3.	2 / 3
	Total	10 / 12 Passed

Description

57%Weight 40%Scale 1-3

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 distinctive but lacks an explicit 'Use when...' trigger clause, which caps completeness and leaves trigger-term coverage partial. It clearly communicates what the skill does but not precisely when Claude should invoke it.

Suggestions

Add a 'Use when...' clause naming natural trigger phrases, e.g. 'Use when the user asks to add Linear integration, wire Linear issue comments to an agent, or set up a Linear channel.'

Broaden trigger terms with common variations users would actually say ('Linear issues', 'Linear comments', 'Linear webhook', 'Linear bot').

Expand the capability list slightly to be more comprehensive (e.g. mention webhook setup and credential storage) to lift specificity toward a level-3 anchor.

Dimension	Reasoning	Score
Specificity	Names a concrete domain ('Add Linear channel integration via Chat SDK') and a specific behavior ('Issue comment threads as conversations'), but stops at two actions rather than a comprehensive list of concrete capabilities, matching the 'names domain and some actions, but not comprehensive' anchor.	2 / 3
Completeness	It answers 'what' (add Linear channel integration, issue comment threads as conversations) but provides no 'when should Claude use it' / 'Use when...' trigger guidance; per the judging guidelines a missing explicit trigger clause caps completeness at 2, so it does not reach the level-3 anchor.	2 / 3
Trigger Term Quality	'Linear channel integration', 'Chat SDK', and 'comment threads' are relevant terms a user might say, but common natural variations ('Linear issues', 'Linear comments', 'Linear bot') are missing, fitting the 'some relevant keywords but missing common variations' anchor rather than full coverage.	2 / 3
Distinctiveness Conflict Risk	'Add Linear channel integration via Chat SDK' targets a clearly distinct niche (Linear integration) with specific triggers unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers; unlikely to conflict' anchor.	3 / 3
	Total	9 / 12 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: nanocoai/nanoclaw
Path: .claude/skills/add-linear/SKILL.md
Commit: 641963c

Reviewed: 6 days 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.