Menu
Quick captures to the Things 3 inbox. Not for reads (things:jxa), scheduled tasks, updates, or projects (things:url).
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Query Claude Code session history via a DuckDB index over `~/.claude/projects/`. Use when asked about Claude Code activity ("how many tokens today?", "what did I work on this week?") or instead of reading, grepping, or jq-ing session transcripts. Not for codebase search, git log queries, or arbitrary databases.
Creating and optimizing Claude Code Skills including activation patterns, content structure, and development workflows. Use when creating new skills, converting memory files to skills, debugging skill activation, or understanding skill architecture and best practices.
Read and query Things 3 data (lists, todos, projects, tags, logbook). Not for writes. Use things:url to create/update, things:inbox for quick captures.
Triage and batch-implement Claude-tagged Things todos as PRs for the claude config repo, discover improvement candidates from session history, or watch open PRs to implement review feedback and close shipped todos. Use when the user wants to work on their Claude Code improvement backlog, process Things todos tagged claude-code, batch-implement configuration changes, mine session history for grounded config-change candidates (Discover mode), or watch this skill's open PRs for review feedback and merges (Watch mode).
Fetch, reply to, and resolve review threads on a GitHub pull request. Use when checking what review feedback needs addressing, whether threads are resolved, replying to review comments, or clearing AI-reviewer threads after acting on them.
Live tmux inbox for reviewing inbound pull requests across GitHub and GitLab. Use when reviewing multiple PRs, checking the review queue, batch reviews, or managing your review inbox. Pass --queue to spawn an already-ordered queue.
| name | things:inbox |
| description | Quick captures to the Things 3 inbox. Not for reads (things:jxa), scheduled tasks, updates, or projects (things:url). |
| argument-hint | <text> |
| allowed-tools | ["Bash(bun ${CLAUDE_PLUGIN_ROOT}/scripts/inbox.ts:*)"] |
Add todos to the Things 3 inbox.
$ARGUMENTS is the capture text, passed as title. Multiple lines become multiple todos via titles. See Add a Todo.
bun ${CLAUDE_PLUGIN_ROOT}/scripts/inbox.ts --session-id ${CLAUDE_SESSION_ID} title="Buy milk"
The script handles URL encoding, session attribution, and the Claude tag. Add extra tags via the --tag flag (repeatable): --tag claude-code adds the claude-code tag to all captured todos. Multiple tags: --tag foo --tag bar.
The script always prints a confirmation to stdout on success. When the x-callback-url plugin is installed, xcall returns the todo ID and the script outputs https://things.bendrucker.me/show?id=.... Present this URL to the user so they can click to open the todo. Without xcall (or when xcall succeeds but returns no ID), the script prints captured: <title>. No stdout output means the call failed; read stderr and surface the cause to the user rather than retrying.
title (string) — todo titletitles (newline-separated) — multiple todosnotes (string, max 10,000 chars) — additional notes (session attribution appended as footer)tags (comma-separated) — extra tag names (Claude is always included)checklist-items (newline-separated, max 100) — checklist items# Simple inbox item
bun ${CLAUDE_PLUGIN_ROOT}/scripts/inbox.ts --session-id ${CLAUDE_SESSION_ID} title="Call dentist"
# With additional notes
bun ${CLAUDE_PLUGIN_ROOT}/scripts/inbox.ts --session-id ${CLAUDE_SESSION_ID} title="Review PR #456" tags=Work notes="Check error handling"
# Multiple items at once
bun ${CLAUDE_PLUGIN_ROOT}/scripts/inbox.ts --session-id ${CLAUDE_SESSION_ID} titles="Buy milk
Pick up dry cleaning
Walk dog"
# With checklist
bun ${CLAUDE_PLUGIN_ROOT}/scripts/inbox.ts --session-id ${CLAUDE_SESSION_ID} title="Prepare presentation" checklist-items="Create slides
Prepare talking points
Practice delivery"
Things supports Markdown in notes:
#, ##, ###**text**[title](url)- or 1.The script always prints to stdout on success. If you see no output, the call failed. Read stderr, surface the cause to the user, and only retry once the root cause is understood. Silent retries have created duplicate todos.
If stderr mentions procNotFound, -10810, or LSOpenURLsWithRole, the macOS sandbox blocked the URL handoff to Things. Launch Services handoff is covered by sandbox.allowAppleEvents in user/settings.json. If this still happens, verify that key is set rather than disabling the sandbox manually.