Automate Linear tasks via Rube MCP (Composio): issues, projects, cycles, teams, labels. Always search tools first for current schemas.
63
45%
Does it follow best practices?
Impact
95%
1.97xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/linear-automation/SKILL.mdIssue creation workflow and priority encoding
RUBE_SEARCH_TOOLS first
0%
100%
RUBE_MANAGE_CONNECTIONS call
0%
100%
Connection ACTIVE check
0%
100%
GET_ALL_LINEAR_TEAMS prerequisite
40%
100%
LIST_LINEAR_STATES prerequisite
0%
100%
Priority as integers
100%
100%
Correct urgent priority value
100%
100%
label_ids as array
100%
100%
Team ID passed to CREATE_LINEAR_ISSUE
80%
100%
State ID resolution shown
0%
100%
Cycle and team scoping, connection setup
RUBE_SEARCH_TOOLS first
0%
0%
RUBE_MANAGE_CONNECTIONS setup
0%
100%
ACTIVE connection verification
0%
100%
GET_ALL_LINEAR_TEAMS for team IDs
33%
100%
Team-scoped cycle lookup
41%
100%
Both teams handled
100%
100%
Team name to ID resolution
100%
100%
No hardcoded team IDs
100%
100%
Pagination awareness
100%
100%
Correct tool sequence order
28%
57%
Multi-team project creation and custom GraphQL
RUBE_SEARCH_TOOLS first
0%
100%
RUBE_MANAGE_CONNECTIONS included
0%
100%
ACTIVE status check
0%
100%
GET_ALL_LINEAR_TEAMS prerequisite
40%
100%
team_ids as array
100%
100%
Multi-team array shown
100%
100%
LINEAR_RUN_QUERY_OR_MUTATION used
25%
100%
GraphQL query provided
100%
100%
Variables object included
37%
100%
Project creation tool used
62%
100%
7cc63f3
Table of Contents
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.