CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ktlo

Instructions to fetch assigned Linear issues in the current cycle and potentially kick off a development session.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/ktlo/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 tight, well-sequenced instruction set with exact MCP call parameters and good edge-case handling. Its main gaps are the missing tool name for fetching full issue details and the absence of any error-recovery guidance for failed MCP calls.

Suggestions

Name the specific MCP call for the follow-up step (e.g. 'call get_issue with the chosen issue ID') so 'fetch the rest of the issue's details' is fully executable.

Add a brief error-recovery instruction for failed MCP calls (retry, or surface the error and ask how to proceed).

Consolidate the duplicated warning in step 3 into one statement to remove the only redundancy.

DimensionReasoningScore

Conciseness

The body is a lean ~15 lines of pure instructions with no explanation of concepts Claude already knows; the only trimmable redundancy is that step 3 states the same 'do not pass "current"' constraint twice ('(NOT the string "current")' and 'Do NOT pass "current" as the cycle value'). This fits anchor 4 (efficient with minor instances that could be trimmed) rather than anchor 5's 'every token earns its place'.

4 / 5

Actionability

The steps name exact MCP calls with parameters ('get_user with query "me"', 'list_cycles with type: "current" and that team's teamId', 'list_issues with assignee: "me"'), which is concrete, copy-paste-ready guidance for an instruction-only skill. It falls short of anchor 5 only because later steps are underspecified ('fetch the rest of the issue's details' names no tool) and 'think about the best way to implement' is open-ended.

4 / 5

Workflow Clarity

Steps 1-4 are explicitly sequenced ('Follow these steps exactly') with conditional branches ('Skip teams with no active cycle', 'It is possible that I have no issues assigned') and a deduplicate/combine step. The read-only workflow needs no destructive-operation validation, but error-recovery checkpoints (e.g. what to do if an MCP call fails) are absent, matching anchor 4's 'most checkpoints present; minor validation gaps' rather than anchor 5's explicit feedback loops.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, with no external references needed, and no bundle files exist (references/, scripts/, assets/ are absent). Per the rubric's simple-skill guidance, well-organized content alone qualifies for 5; the numbered steps plus a clearly separated 'what happens after selection' paragraph make navigation trivial.

5 / 5

Total

17

/

20

Passed

Description

53%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 communicates a specific, single-purpose capability but omits any 'when to use' trigger guidance and lacks natural synonyms users might say. It is serviceable for a user-invoked command (disable-model-invocation: true) but would be weak for model-driven triggering.

Suggestions

Append an explicit trigger clause, e.g. 'Use when I ask about my Linear issues, tickets, or sprint work, or want to start a development session.'

Include common synonyms such as 'tickets', 'sprint', and 'backlog' so natural user phrasings match the description.

State the outcome concretely (e.g. 'presents them as options to pick from and plans the chosen issue in plan mode') instead of the vague 'potentially kick off a development session'.

DimensionReasoningScore

Specificity

The description names the domain ('assigned Linear issues in the current cycle') and 1-2 concrete actions ('fetch' and 'kick off a development session'), but coverage is not comprehensive and the second action is softened by 'potentially'. It clearly exceeds anchor 2 (domain only, generic actions) but lists too few concrete actions for anchor 4.

3 / 5

Completeness

The 'what' is clear ('fetch assigned Linear issues in the current cycle and potentially kick off a development session'), but there is no 'Use when...' clause or any trigger guidance, so per the judging guidelines completeness is capped at 3. It is not a 2 because the 'what' is specific, and not a 4 because 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

It contains relevant keywords ('Linear', 'issues', 'cycle', 'assigned', 'development session'), but misses natural variations users would say such as 'tickets', 'sprint', 'backlog', or 'my Linear work'. This matches anchor 3 ('some relevant keywords but missing common variations or synonyms') rather than anchor 4's 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

Naming the Linear tool and cycle scoping gives it a clear niche that would not collide with unrelated skills, matching 'mostly distinct; minor overlap risk'. It is not a 5 because 'kick off a development session' is broad phrasing that could overlap with general dev-workflow skills.

4 / 5

Total

13

/

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.

Validation — 15 / 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

coinbase/cds

Path

.claude/skills/ktlo/SKILL.md

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.