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.

75

1.97x
Quality

Does it follow best practices?

Impact

95%

1.97x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

57%

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

The body is well-structured and free of concept padding, with concrete tool/parameter mappings and a clear setup validation checkpoint. Its main gaps are duplicated content, missing example invocations, and absent verification steps for destructive mutations.

Suggestions

Remove the duplicated 'Known Pitfalls' section or the per-workflow Pitfalls blocks so pitfalls live in one place, cutting redundancy.

Add one or two example tool invocations showing a complete argument object (e.g. a LINEAR_CREATE_LINEAR_ISSUE call with team_id, title, priority filled in) to make guidance copy-paste ready.

Add a verify-after step to create/update/GraphQL workflows (e.g. re-fetch the issue to confirm changes applied) to introduce feedback loops for destructive operations.

DimensionReasoningScore

Conciseness

The body is lean and avoids explaining concepts Claude already knows, but it duplicates pitfalls (each workflow lists a Pitfalls section that is repeated verbatim in 'Known Pitfalls') and the Quick Reference table restates tool slugs already enumerated in the workflows, so it could be tightened.

2 / 3

Actionability

It gives concrete tool slugs, parameter names, and enum value mappings (e.g. priority 0-4), but provides no example invocations showing how arguments assemble into an actual tool call, leaving the guidance concrete but incomplete.

2 / 3

Workflow Clarity

Setup has an explicit validation checkpoint ('Confirm connection status shows ACTIVE') and workflows are numbered with prerequisites marked, but destructive mutations (create/update issue, GraphQL mutations) lack validate-after or verify-success steps, capping workflow clarity at 2.

2 / 3

Progressive Disclosure

No bundle files exist and the content is a single, well-organized file with clearly labeled sections and one clearly-signaled external link; navigation is easy with no nested references, satisfying progressive disclosure for a self-contained reference skill.

3 / 3

Total

9

/

12

Passed

Description

72%

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 to a clear niche and uses natural trigger terms, but it lacks an explicit 'when to use' clause and relies on one umbrella verb rather than distinct concrete actions. Adding a Use-when trigger and per-object action verbs would raise it.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user wants to create, search, update, or list Linear issues, projects, cycles, teams, or labels.'

Replace the single 'Automate' verb with distinct concrete actions per object (e.g. 'create and search issues, manage projects and cycles, resolve teams and labels').

Lead with the user-facing capability rather than the implementation detail 'via Rube MCP (Composio)', which is a how not a what.

DimensionReasoningScore

Specificity

It names the domain ('Automate Linear tasks via Rube MCP') and enumerates capability objects ('issues, projects, cycles, teams, labels'), but a single verb 'Automate' governs nouns rather than listing distinct concrete action verbs, so it stops short of the comprehensive multi-action anchor.

2 / 3

Completeness

It clearly answers 'what' (automate Linear tasks across issues/projects/cycles/teams/labels) but lacks any 'Use when...' clause; 'Always search tools first for current schemas' is a how-instruction, not a when-trigger, so completeness is capped at 2.

2 / 3

Trigger Term Quality

Terms like 'Linear tasks', 'issues', 'projects', 'cycles', 'teams', and 'labels' are exactly what a user would naturally say when needing this skill, giving good coverage of natural trigger keywords.

3 / 3

Distinctiveness Conflict Risk

It is tightly scoped to Linear via Rube MCP (Composio), a clear niche with distinct triggers unlikely to overlap with other skills.

3 / 3

Total

10

/

12

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
davepoon/buildwithclaude
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.