ktlo

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

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/ktlo/SKILL.md

Quality

Content

82%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 content is a tight, actionable MCP workflow with concrete tool calls and good edge-case handling. Minor gaps are the slight redundancy in step 3, absence of MCP-error recovery guidance, and lack of section headers.

Suggestions

Consolidate the duplicated 'do not pass current' warning in step 3 into a single clear statement to tighten conciseness.

Add a brief feedback step for MCP call failures (e.g., retry once, then report the failing call) to round out workflow clarity.

Add lightweight section headers (e.g. '## Fetch', '## Present', '## Plan mode') to improve navigation for the multi-phase flow.

Dimension	Reasoning	Score
Conciseness	The body is lean, assumes Claude knows Linear/cycles, and gives direct instructions; the only minor trim is the double restated warning in step 3 about not passing 'current' as the cycle value.	4 / 5
Actionability	Concrete MCP tool calls are specified with exact arguments (get_user query 'me', list_cycles type 'current' + teamId, list_issues assignee 'me' + explicit cycle id + team), covering the common cases fully.	5 / 5
Workflow Clarity	A clear numbered fetch sequence with explicit edge-case checkpoints (skip teams with no active cycle, deduplicate, handle empty assignment) is present, though there is no error-recovery feedback loop for failed MCP calls.	4 / 5
Progressive Disclosure	The under-50-line single-purpose skill appropriately keeps all content inline with no external references needed, but it lacks explicit section headers that would make the logical flow easier to navigate.	4 / 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 clearly states what the skill does but omits any explicit 'when to use it' trigger guidance, which caps completeness. Trigger terms are domain-specific but lack synonyms or natural variations.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when I ask to start my day, check my Linear cycle, or kick off work on an assigned issue.'

Broaden trigger terms with natural synonyms users would actually say (e.g. 'my Linear tasks', 'this cycle's issues', 'start work').

Drop the hedging 'potentially kick off' in favor of a concrete second action to lift specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ('Linear issues in the current cycle') and two concrete actions ('fetch assigned Linear issues' and 'kick off a development session'), but coverage is not comprehensive and 'potentially' weakens the second action.	3 / 5
Completeness	The 'what' is clear (fetch assigned issues in the active cycle, start a dev session), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Relevant domain keywords like 'Linear issues' and 'current cycle' appear, but there are no synonyms or variations a user might naturally say beyond these Linear-specific terms.	3 / 5
Distinctiveness Conflict Risk	The Linear-cycle niche is mostly distinct with clear specific triggers, though the generic 'kick off a development session' phrase carries minor overlap risk with general dev-workflow skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: edabef0

Reviewed: ~16 hours ago

Table of Contents

Discovery Implementation Validation

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.