CtrlK
BlogDocsLog inGet started
Tessl Logo

linear-automation

Automate Linear tasks via Rube MCP (Composio): issues, projects, cycles, teams, labels. Always search tools first for current schemas.

59

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/linear-automation/SKILL.md

The canonical home for this skill is linear-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, actionable reference for Linear's Rube MCP tools with clear workflow sequences and parameter guidance. It loses points mainly on conciseness due to redundant sections and a filler trailing line.

Suggestions

Remove the redundant "Known Pitfalls" section (its contents already appear under each workflow's Pitfalls) or fold unique items into the relevant workflow.

Delete or replace the filler "When to Use" line ("This skill is applicable to execute the workflow or actions described in the overview.") with concrete trigger guidance.

Add a post-action verification step to mutating workflows (e.g., after LINEAR_CREATE_LINEAR_ISSUE, fetch the returned issue to confirm creation) to strengthen workflow_clarity.

DimensionReasoningScore

Conciseness

Mostly efficient with no conceptual padding, but the "Known Pitfalls" section repeats per-workflow pitfalls, the Quick Reference table duplicates tool sequences, and the closing "When to Use" line is filler.

3 / 5

Actionability

Provides concrete tool slugs, numbered sequences, and params with types and enumerated values (e.g. priority 0-4); minor gaps include no full example tool-invocation payload.

4 / 5

Workflow Clarity

Sequences are clear with [Prerequisite]/[Optional]/[Required] markers and a setup validation checkpoint ("Confirm connection status shows ACTIVE"), though post-action verification feedback loops are absent.

4 / 5

Progressive Disclosure

Single self-contained file with well-organized sections and a useful Quick Reference table; no external references exist, and minor duplication (Known Pitfalls, filler When to Use) keeps it just below 5.

4 / 5

Total

15

/

20

Passed

Description

70%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and distinctive, clearly scoping Linear automation through Rube MCP, but it omits an explicit "Use when..." trigger clause, which limits its completeness. Keyword coverage is good though a few natural synonyms are missing.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to create, update, or query Linear issues, projects, cycles, teams, or labels."

Include natural synonyms like "sprints" (for cycles) and "tickets" (for issues) to broaden trigger-term coverage.

Replace the generic verb "Automate" with concrete action verbs (create, search, update, list) to lift specificity from 4 toward 5.

DimensionReasoningScore

Specificity

Lists several concrete capabilities ("issues, projects, cycles, teams, labels") covering Linear's domain comprehensively, though the only action verb is the generic "Automate".

4 / 5

Completeness

Provides a clear "what" (automate Linear tasks via Rube MCP) but has no "Use when..." clause or explicit trigger guidance, capping completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Includes natural Linear terms users say (issues, projects, cycles, teams, labels) but misses common synonyms like "sprints" (for cycles) and "tickets" (for issues).

4 / 5

Distinctiveness Conflict Risk

Tied to a specific product (Linear) and a specific integration (Rube MCP/Composio), giving it a clear niche with minimal conflict risk against other skills.

5 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.