CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

91

2.48x
Quality

88%

Does it follow best practices?

Impact

97%

2.48x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Evaluation results

100%

66%

Wallet Top-Up Failure Report

Bug report CLI format and labeling

Criteria
Without context
With context

Bug template used

70%

100%

No implementation details

83%

100%

Business-level description

90%

100%

Expected vs Actual present

100%

100%

Bug type label

0%

100%

Source:customer label

0%

100%

Description file flag

0%

100%

mktemp used

0%

100%

No-interactive flag

0%

100%

Team CON

0%

100%

Triage status

0%

100%

100%

56%

ACT Token Pricing Rollout

Feature split by business flow

Criteria
Without context
With context

Multiple issues created

100%

100%

Business flow splits

50%

100%

Feature template used

37%

100%

No implementation details

20%

100%

Flows listed in issues

25%

100%

Source:roadmap label

0%

100%

Feature type label

0%

100%

Parent created first

100%

100%

Children use --parent flag

100%

100%

save_issue relationships

70%

100%

No dependency text in descriptions

0%

100%

Team CON and --no-interactive

50%

100%

92%

51%

Cleaning Up a Backlog Issue

Improve existing issue

Criteria
Without context
With context

No file paths in improved issue

0%

100%

No function names in improved issue

0%

100%

Bug template used

62%

100%

Business-level acceptance criteria

25%

33%

Description file flag in update

0%

100%

mktemp in update script

0%

100%

Correct issue ID updated

100%

100%

save_issue for blocking relationship

75%

100%

save_issue for related relationship

80%

100%

No dependency text in improved issue

100%

100%

Repository
akash-network/console
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.