mcpbeat

Ktlo

coinbase/ktlo

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

390 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
491
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/coinbase/cds --skill ktlo

The instruction itself

as written by the author

Use the Linear MCP server to get my assigned issues in the active cycle. Follow these steps exactly:

  • Call get_user with query "me" to retrieve my user info and the list of teams I belong to.
  • 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.
  • 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.
  • 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.

How to use it

Copy the folder

Take coinbase/ktlo from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.