kanban-issues-karr-cli

Manages git-native kanban boards and agent task cards through the karr CLI.

1|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/Getty/p5-alien-libssh --skill kanban-issues-karr-cli-getty
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kanban-issues-karr-cli
Source: https://github.com/Getty/p5-alien-libssh/tree/main/.claude/skills/kanban-issues-karr-cli
Command: npx skills add https://github.com/Getty/p5-alien-libssh --skill kanban-issues-karr-cli-getty

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Coordinating multiple AI agents on shared work requires a persistent, conflict-safe task board; this Skill teaches agents to pick, claim, hand off, and create tickets on a git-native kanban board stored in repository refs. ## Core Features & Use Cases - Board Operations: Read boards with karr list, board, show, and pick to find and claim the most urgent available card. - Card Lifecycle: Create, edit, block, hand off, archive, and delete cards with claims, dependencies, and cross-board links. - Multi-Agent Coordination: Claim names via KARR_CLAIM, claim timeouts, and lock handling let several agents share one board safely. - Use Case: An agent finishing a fix runs karr handoff 12 --note "Implemented, needs QA" -t to move the card to review while preserving context for the next agent. ## Quick Start Ask the agent to list the unclaimed todo cards on this repository's karr board and pick the most urgent one to start working on.

Frequently Asked Questions about kanban-issues-karr-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I pick and claim a task with the karr CLI?

Run `karr pick --status todo --move in-progress` after exporting KARR_CLAIM with `karr agent-name`. Pick atomically finds the most urgent unblocked, unclaimed card and claims it under your name in one step.

How do multiple agents share one kanban board in git?

Each agent works in its own git worktree and exports KARR_CLAIM from `karr agent-name`, which derives a unique name from the directory. The board lives in shared refs/karr/* refs, so all agents see the same cards while claims stay distinct.

Does karr work on a fresh git clone?

Yes. Read commands like `list` and `board` automatically fetch refs/karr/* from the remote on first use, since git clone does not carry them. Mutating commands pull before and push after each change.

How do I create a card that depends on another repository?

Use `karr edit 5 --add-needs other-repo#7` to record a cross-board dependency, typically combined with `--block` and `--release`. Run `karr needs --resolve` later to settle links once the far card reaches a terminal status.

Why does karr move refuse to move a card to in-progress?

Columns marked require_claim, such as in-progress and review, refuse moves without a claim. Export KARR_CLAIM or pass `--claim NAME` explicitly; claims expire after the board's claim_timeout, defaulting to one hour.