linear-task-management

Creates and names Linear issues, assigns labels and priorities, manages status transitions, and links issues to PRs. Use when decomposing features into tasks or resuming interrupted sessions. Trigger terms: tickets, backlog, task breakdown, project board, sprint planning

Quality

87%

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

Quality

Content

86%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 lean, high-signal instruction-only skill: every gotcha is team-specific knowledge Claude would not otherwise have, and validation checkpoints exist for creates and resume. The main gaps are the absence of a concrete tool-invocation example and loosely sequenced steps.

Suggestions

Add one concrete example of an MCP tool invocation (e.g., a representative create-issue call with its arguments) to complement the 'read the tool list the server offers' guidance and lift actionability.

Group the gotchas into an ordered resume/create flow (e.g., resume: re-read statuses first; create: look up labels/verify ID) so the multi-step sequences carry explicit error-recovery loops.

Dimension	Reasoning	Score
Conciseness	Every line carries non-obvious, team-specific knowledge ("Blockers go in a comment on the issue, not in the description", "Tool names change between server versions: read the tool list the server offers"). There is no padding and no explanation of concepts Claude already knows. Clear level-5 match.	5 / 5
Actionability	Concrete guidance throughout: example titles ("Add schema: priceRange to place"), explicit P1–P4 definitions, a status flow, a description template with named sections, and a bug-creation procedure. It is not a 5 because there is no concrete tool-call example and "verify before delegating" does not state how to verify beyond checking for an issue ID.	4 / 5
Workflow Clarity	Validation checkpoints are present ("Treat a create as successful only if it returns an issue ID (TAS-42)", "On resume, re-read every issue status before acting"), which satisfies the batch-operation validation concern. It is not a 5 because steps are organized as gotchas and conventions rather than a sequenced workflow with explicit error-recovery loops.	4 / 5
Progressive Disclosure	The skill is under 50 lines with well-organized sections and no need for external reference files; the one external pointer (.opencastle/project/linear-config.md) is clearly signaled and one level deep. The under-50-line exception applies, matching the level-5 anchor.	5 / 5
	Total	18 / 20 Passed

Description

88%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 strong description: third-person voice, comprehensive concrete actions, an explicit 'Use when' clause, and natural trigger terms. The only weakness is trigger-term coverage missing a few common synonyms for issues/user stories.

Dimension	Reasoning	Score
Specificity	"Creates and names Linear issues, assigns labels and priorities, manages status transitions, and links issues to PRs" lists multiple specific concrete actions covering the skill comprehensively. It is not a 4 because there are no gaps in coverage of the capability set.	5 / 5
Completeness	It explicitly answers both "what" (create/name issues, labels, priorities, status transitions, PR links) and "when" ("Use when decomposing features into tasks or resuming interrupted sessions") with concrete trigger phrases, matching the level-5 anchor example. Not a 4 because the when-clause is fully explicit, not merely adequate.	5 / 5
Trigger Term Quality	"tickets, backlog, task breakdown, project board, sprint planning" are natural phrases a user would actually say. It falls short of the comprehensive level-5 anchor because common synonyms like "issues", "user stories", or "epics" are not included as trigger terms.	4 / 5
Distinctiveness Conflict Risk	The description is explicitly Linear-scoped ("Linear issues"), making it mostly distinct, but terms like "task breakdown" and "backlog" carry minor overlap risk with general project-management skills. Not a 5 due to that minor overlap; not a 3 because the tool domain is named and triggers are specific to issue tracking.	4 / 5
	Total	18 / 20 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: monkilabs/opencastle
Path: src/orchestrator/plugins/linear/SKILL.md
Commit: c0f4566

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.