linear-issue
Plan, create, and improve Linear issues with business-level clarity. Use this skill whenever the user wants to create a Linear issue, improve an existing one, file a bug, plan a feature, create a chore/enabler, or mentions "linear issue", "file an issue", "create a ticket", "log a bug", "new issue", "plan this work", "improve this issue", or "clean up this ticket". Also trigger when the user says "I found a bug", "we need a ticket for...", "can you create an issue for...", "break this down into issues", or pastes a Linear issue URL/ID. This is the required way to create and maintain issues — it ensures every issue follows the team's format and is scoped for small PRs.
92
—
Does it follow best practices?
Impact
98%
2.33xAverage score across 3 eval scenarios
Passed
No known issues
Evaluation results
100%
76%Deployment Failure Bug Report
Bug issue creation with correct CLI pattern and labels
No implementation details
33%
100%
Business-level problem statement
100%
100%
Affected flow named
100%
100%
Source label: error-log
0%
100%
Type label: Bug
25%
100%
Both labels present
0%
100%
Uses --description-file
0%
100%
Uses mktemp
0%
100%
Uses --no-interactive
0%
100%
Team CON
0%
100%
Triage status
0%
100%
100%
59%New Payment Method: USDC to ACT Migration for Billing Flows
Multi-issue feature plan with splitting and native relationships
Issues split by business flow
100%
100%
No L-N. title prefixes
100%
100%
No implementation details in descriptions
10%
100%
Source label: roadmap
0%
100%
Type label: Feature
0%
100%
Native relationships over text
80%
100%
Parent issue created first
0%
100%
Uses --description-file with mktemp
0%
100%
Uses --no-interactive and --team CON
0%
100%
Default Triage status
0%
100%
Acceptance criteria present
100%
100%
96%
33%Clean Up a Technical Issue Description
Improve existing issue: remove impl details, native relationships
No file paths
100%
100%
No function names
100%
100%
No line numbers
100%
100%
No step-by-step implementation plan
100%
100%
Business-level problem statement
100%
100%
Dependencies removed from text
0%
100%
Native relationship commands
100%
60%
Uses --description-file with mktemp
0%
100%
Correct update command
50%
100%
Source label added
0%
100%
- Repository
- akash-network/console
- Commit
7b6a52e
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
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.