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
100
100%
Does it follow best practices?
Impact
Pending
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 communicates specific capabilities within the Linear issue management domain. It covers concrete actions, provides explicit 'Use when' guidance with two clear scenarios, and lists natural trigger terms. The description is concise, uses third person voice, and is well-differentiated from other potential 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 all distinct, concrete operations. | 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.' Also includes domain-specific terms like 'Linear issues', 'PRs', 'labels', and 'priorities' that naturally appear in user requests. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Linear as a specific tool, with distinct actions like issue creation, status transitions, and PR linking. The combination of 'Linear' plus project management trigger terms creates a clear niche unlikely to conflict with other skills. | 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 Claude how to manage Linear issues via MCP tools. It excels at providing concrete examples (including anti-patterns), clear workflows with validation steps, and appropriate separation of universal instructions from project-specific configuration. The Status Update Procedure with its UUID warning is a particularly valuable guardrail against a common failure mode.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. It avoids explaining what Linear is, what issues are, or how MCP tools work in general. Every section delivers specific, actionable information without padding. The tables, code blocks, and bullet points are all tightly written. | 3 / 3 |
Actionability | Provides concrete JSON examples for MCP tool calls (create, update, search), 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). The Status Update Procedure includes an explicit error recovery path (if tracker-config.md lacks UUIDs, skip and log warning; if creation fails, check UUIDs and retry). The transition rules clearly delineate agent vs. GitHub automation responsibilities. | 3 / 3 |
Progressive Disclosure | The skill is well-structured as an overview with clear one-level-deep references to tracker-config.md for project-specific UUIDs. Content is appropriately split — the skill contains the universal workflow knowledge while project-specific configuration lives in the referenced file. Sections are logically ordered and clearly signaled with headers. | 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
18c6f2c
- 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.