How do I install the Do Tickets skill?

Run npx skillmds@latest add lukastk/do-tickets in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Do Tickets safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Do Tickets?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Do Tickets free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Do Tickets?

lukastk (@lukastk) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Do Tickets by lukastk — Agent Skill

Name: Do Tickets
Author: lukastk

Do Tickets

Use when you (an agent in a sesh thread) need to handle assigned work tickets — find your tickets, read a ticket's prompt/instructions, or update its status (e.g. mark it done). Covers the `sesh ticket` find → read → report loop.

lukastk 442d868 3.0 KB Updated Sep 17, 2026

File contents

do-tickets

A ticket is a unit of work in sesh. When one is bound to your thread it's assigned to you; its prompt is your instructions. Loop: find → read → report.

Statuses: triage (draft) → ready (final, unattached) → active (assigned to a thread) → done / dropped (terminal). An active ticket on your thread = your work; mark it done when finished.

# FIND — your thread's tickets (auto-detected via the pane marker / $SESH_THREAD_ID)
sesh ticket list --current                 # id  status  name  thread
sesh ticket list --current --json          # one JSON object per line

# READ — the instructions (raw, no trailing newline)
sesh ticket get --id <id> --field prompt   # --field: id|name|prompt|status|thread|created|closed|notes
sesh ticket get --id <id> --json           # whole record

# REPORT — close AND record what you did, in one call (ALWAYS leave a note on close)
sesh ticket set-status --id <id> --status done --note "what you did; closed by <commit-sha>"
sesh ticket set-status --id <id> --status active --thread <thread-id>

Always leave a note when you close a ticket. A ticket has a free-text notes field; when you mark a ticket done (or dropped), append a short note explaining what you did and — if there was a commit — which commit closed it. Write notes in markdown (headings, lists, fenced code, links) — they are rendered as markdown in the Obsidian ticket-note panel where Lukas reads them during consolidation. --note on set-status appends as part of the same call (each --note appends, blank-line separated). You can also append/replace notes independently:

sesh ticket set --id <id> --append-note "investigated; root cause is X"   # append
sesh ticket set --id <id> --notes "<full text>"                          # REPLACE
sesh ticket get --id <id> --field notes                                  # read them back

--id takes the full ticket UUID (from ticket list). Commands auto-route to wherever the ticket lives, so acting on your own thread's tickets just works.

A prompt may reference files/images as @blob(<hex>) tokens. When the prompt is delivered to you (send-prompt) these are already expanded to real paths you can read. If you read the prompt raw with ticket get --field prompt, the tokens are NOT expanded — pipe through sesh blob expand to resolve them to paths:

sesh ticket get --id <id> --field prompt | sesh blob expand   # @blob(..) → real file paths

Other ops: ticket create --name <n> [--prompt <t>], ticket set --id <id> [--name|--prompt|--notes|--append-note], ticket send-prompt --id <id> (type the prompt into the bound thread's pane), ticket delete --id <id>. (sesh ticket --help for the rest.)

---name: do-ticketsdescription: Use when you (an agent in a sesh thread) need to handle assigned work tickets — find your tickets, read a ticket's prompt/instructions, or update its status (e.g. mark it done). Covers the `sesh ticket` find → read → report loop.---# do-ticketsA **ticket** is a unit of work in `sesh`. When one is bound to your thread it's assignedto you; its **prompt** is your instructions. Loop: **find → read → report**.Statuses: `triage` (draft) → `ready` (final, unattached) → `active` (assigned to athread) → `done` / `dropped` (terminal). An `active` ticket on your thread = your work;mark it `done` when finished.```bash# FIND — your thread's tickets (auto-detected via the pane marker / $SESH_THREAD_ID)sesh ticket list --current # id status name threadsesh ticket list --current --json # one JSON object per line# READ — the instructions (raw, no trailing newline)sesh ticket get --id <id> --field prompt # --field: id|name|prompt|status|thread|created|closed|notessesh ticket get --id <id> --json # whole record# REPORT — close AND record what you did, in one call (ALWAYS leave a note on close)sesh ticket set-status --id <id> --status done --note "what you did; closed by <commit-sha>"sesh ticket set-status --id <id> --status active --thread <thread-id>```**Always leave a note when you close a ticket.** A ticket has a free-text **`notes`**field; when you mark a ticket `done` (or `dropped`), append a short note explaining whatyou did and — if there was a commit — which commit closed it. **Write notes in markdown**(headings, lists, fenced code, links) — they are rendered as markdown in the Obsidianticket-note panel where Lukas reads them during consolidation. `--note` on `set-status`appends as part of the same call (each `--note` appends, blank-line separated). You canalso append/replace notes independently:```bashsesh ticket set --id <id> --append-note "investigated; root cause is X" # appendsesh ticket set --id <id> --notes "<full text>" # REPLACEsesh ticket get --id <id> --field notes # read them back````--id` takes the full ticket UUID (from `ticket list`). Commands auto-route to whereverthe ticket lives, so acting on your own thread's tickets just works.A prompt may reference files/images as **`@blob(<hex>)`** tokens. When the prompt is*delivered* to you (`send-prompt`) these are already expanded to real paths you can read.If you read the prompt **raw** with `ticket get --field prompt`, the tokens are NOTexpanded — pipe through `sesh blob expand` to resolve them to paths:```bashsesh ticket get --id <id> --field prompt | sesh blob expand # @blob(..) → real file paths```Other ops: `ticket create --name <n> [--prompt <t>]`,`ticket set --id <id> [--name|--prompt|--notes|--append-note]`,`ticket send-prompt --id <id>` (type the prompt into the bound thread's pane),`ticket delete --id <id>`. (`sesh ticket --help` for the rest.)

Frequently asked questions