Ktlo
- 10 installs
- 493 repo stars
- Updated July 31, 2026
- coinbase/cds
Fetches the user's assigned Linear issues in the active cycle via the Linear MCP and optionally starts a plan-mode development session.
About
Queries the Linear MCP for issues assigned to the user in each team's current cycle, deduplicates them, and presents them as options. A developer uses it to review keep-the-lights-on work and pick an issue to plan.
- Uses explicit cycle IDs, never the string 'current'
- Reminds to check the Jira bug sprint board
Ktlo by the numbers
- 10 all-time installs (skills.sh)
- Ranked #2,198 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/coinbase/cds --skill ktloAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 10 |
|---|---|
| repo stars | ★ 493 |
| Last updated | July 31, 2026 |
| Repository | coinbase/cds ↗ |
What it does
Fetches the user's assigned Linear issues in the active cycle via the Linear MCP and optionally starts a plan-mode development session.
Files
Use the Linear MCP server to get my assigned issues in the active cycle. Follow these steps exactly:
1. Call get_user with query "me" to retrieve my user info and the list of teams I belong to. 2. For each of my teams, call list_cycles with type: "current" and that team's teamId to get the active cycle ID(s). Skip teams with no active cycle. 3. For each active cycle found, call list_issues with assignee: "me", the explicit cycle id (NOT the string "current"), and the corresponding team ID. Do NOT pass "current" as the cycle value — it must be the actual cycle ID returned in step 2. 4. 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.
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493k