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
80
100%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly articulates specific capabilities (creating issues, assigning labels, managing status, linking PRs), provides explicit 'Use when' guidance with two concrete scenarios, and lists natural trigger terms. The description is concise, uses third-person voice, and is well-scoped to Linear issue management, making it easily distinguishable from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Creates and names Linear issues, assigns labels and priorities, manages status transitions, and links issues to PRs.' These are clearly defined, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (creates/names issues, assigns labels/priorities, manages status, links to PRs) and 'when' (decomposing features into tasks, resuming interrupted sessions) with explicit trigger terms listed separately. | 3 / 3 |
Trigger Term Quality | Includes explicit trigger terms that users would naturally say: 'tickets, backlog, task breakdown, project board, sprint planning.' These cover common variations of how users refer to issue tracking and project management tasks. Also includes 'Linear issues' and 'PRs' as natural keywords. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Linear as the specific platform, with distinct triggers like 'Linear issues', 'sprint planning', and 'task breakdown' that are unlikely to conflict with generic code or document skills. The combination of Linear + issue management creates a clear niche. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that efficiently teaches Linear task management with concrete MCP tool examples, clear workflow sequences, and explicit validation checkpoints. It respects Claude's intelligence by avoiding unnecessary explanations while providing critical gotchas (UUID vs name for stateId). The progressive disclosure to tracker-config.md for project-specific values is well-designed.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. It avoids explaining what Linear is or how MCP tools work conceptually, instead jumping straight into actionable patterns. Every section earns its place with concrete examples, tables, or specific rules. | 3 / 3 |
Actionability | Provides concrete JSON examples for MCP tool calls, specific naming conventions with before/after examples, a priority table with clear criteria, and explicit transition rules. The Status Update Procedure includes both correct and incorrect examples, making it copy-paste ready. | 3 / 3 |
Workflow Clarity | The Session Workflow section provides a clear numbered sequence with validation checkpoints (verify each returns a valid issue ID, verify all issues Done/Cancelled, run build/lint/test). Error recovery is explicit: retry on creation failure, re-read state on inconsistency. The Status Update Procedure includes a critical validation warning about UUIDs vs names with a fallback (skip and log warning). | 3 / 3 |
Progressive Disclosure | The skill cleanly separates project-specific configuration (team IDs, UUIDs) into a referenced tracker-config.md file, keeping the SKILL.md focused on workflow and patterns. References are one level deep and clearly signaled at the top and throughout. The content is well-organized into logical sections without being monolithic. | 3 / 3 |
Total | 12 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- monkilabs/opencastle
- Commit
7a69a05
- 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.