ktlo
SkillProductivityInstructions to fetch assigned Linear issues in the current cycle and potentially kick off a development session.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the ktlo skill
What this skill tells your AI
The instructions your AI receives, as published by coinbase/cds in .claude/skills/ktlo/SKILL.md and read by ahel’s review.
Use the Linear MCP server to get my assigned issues in the active cycle. Follow these steps exactly:
- Call
get_userwith query"me"to retrieve my user info and the list of teams I belong to. - For each of my teams, call
list_cycleswithtype: "current"and that team'steamIdto get the active cycle ID(s). Skip teams with no active cycle. - For each active cycle found, call
list_issueswithassignee: "me", the explicit cycleid(NOT the string "current"), and the correspondingteamID. Do NOT pass"current"as the cycle value — it must be the actual cycle ID returned in step 2. - Deduplicate and combine all results.
Present them to me as a list of options. It is possible that I have no issues assigned to me in the active cycle.
Also remind me to check the Jira Bug Sprint board for any bugs that may be assigned to me as they are still not tracked in Linear.
If I have any issues assigned to me in the active cycle, ask for the issue id/name/etc. that I may want to work on. If provided, fetch the rest of the issue's details and think about the best way to implement the feature/bug/etc. If there is not enough context on the issue, ask me clarifying questions.
You must always execute on designated issue in PLAN MODE. Never start coding a solution to the issue without consent from me on a well thought out plan.
Signals
- GitHub stars
- 504
- Forks
- 105
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
ktlo- Source
- github.com/coinbase/cds