ktlo
Instructions to fetch assigned Linear issues in the current cycle and potentially kick off a development session.
66
58%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/ktlo/SKILL.mdQuality
Discovery
32%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 identifies its domain (Linear issue tracking) but is weakened by vague language ('potentially kick off a development session') and the complete absence of explicit trigger guidance. It would benefit from concrete action lists and a 'Use when...' clause to help Claude reliably select this skill.
Suggestions
Add an explicit 'Use when...' clause with natural trigger terms like 'my Linear tickets', 'current sprint', 'what's assigned to me', 'start working on issues'.
Replace the vague 'potentially kick off a development session' with specific actions, e.g., 'creates a branch, checks out code, and opens the relevant files for each issue'.
Include common user phrasing variations such as 'sprint tasks', 'assigned tickets', 'cycle work', or 'Linear backlog' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Linear issues, current cycle) and some actions (fetch assigned issues, kick off development session), but 'potentially kick off a development session' is vague and non-committal. It doesn't list concrete sub-actions. | 2 / 3 |
Completeness | Describes what it does (fetch Linear issues, kick off dev session) but lacks any explicit 'Use when...' clause or trigger guidance. Per the rubric, a missing 'Use when' clause caps completeness at 2, and the 'what' is also weak due to the vague 'potentially kick off' phrasing, bringing it to 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Linear issues', 'current cycle', and 'development session', but misses common user phrasings like 'my tasks', 'sprint', 'backlog', 'what should I work on', or 'assigned tickets'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Linear issues' and 'current cycle' provides some specificity, but 'kick off a development session' is generic enough to overlap with other workflow or project management skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill that provides clear, actionable MCP tool call sequences with specific parameter guidance. The workflow is logically sequenced with appropriate constraints (especially the critical note about not passing 'current' as a cycle value). Minor verbosity around repeated warnings and the tangential Jira reminder slightly reduce token efficiency.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient with clear steps, but includes some unnecessary elaboration (e.g., repeating the 'do NOT pass current' warning twice, the Jira reminder is tangential context). Could be tightened slightly. | 2 / 3 |
Actionability | Provides specific MCP tool calls with exact parameter names and values (e.g., `get_user` with `"me"`, `list_cycles` with `type: "current"` and `teamId`, `list_issues` with explicit cycle `id`). The instructions are concrete and directly executable without ambiguity. | 3 / 3 |
Workflow Clarity | Clear sequential steps (1-4) with explicit constraints at each stage (skip teams with no active cycle, deduplicate results). Includes a decision tree for post-retrieval behavior (ask for issue, fetch details, plan mode). The 'PLAN MODE' constraint serves as a validation checkpoint before destructive action (coding). | 3 / 3 |
Progressive Disclosure | This is a simple, single-purpose skill under 50 lines with no need for external references. The content is well-organized with a clear numbered workflow followed by post-workflow interaction guidance. No bundle files are needed. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- coinbase/cds
- Commit
f79a780
- 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.