# Plannotator Inbox

Open the Plannotator Inbox in the browser (starting it if needed), say its address, and...

- Repository: https://github.com/backnotprop/plannotator (9810 stars)
- Category: Engineering
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add backnotprop/plannotator --skill plannotator-inbox -g -a claude-code -y`
Codex: `npx skills add backnotprop/plannotator --skill plannotator-inbox -g -a codex -y`
Cursor: `npx skills add backnotprop/plannotator --skill plannotator-inbox -g -a cursor -y`
Gemini CLI: `npx skills add backnotprop/plannotator --skill plannotator-inbox -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add backnotprop/plannotator`

## Description

Open the Plannotator Inbox in the browser (starting it if needed), say its address, and learn how to use the Inbox for the rest of the session.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Plannotator Inbox

## Inbox address

!`plannotator inbox --open`

## Using the Inbox

The Plannotator Inbox is one window on this computer where you leave the person messages, `:::question` blocks they answer with a click, and files. They answer when they can. Nothing blocks: you send, then keep working or end your turn.

- Use it for a decision only they can make (a :::question block; go on with other work), finished long work (a short summary, files in `attachments`), or when they ask.
- One thread per work stream, unless the person says otherwise.
- Send with a `plannotator_inbox` tool when you have one (it can be listed with a prefix and may need loading through tool search first): `action` `send_message`, with a markdown `body`. Otherwise call `send_message` on the Inbox's MCP server, `plannotator inbox mcp`.
- send_message's result says whether the person's reply arrives in this session by itself. When it does, do not wait or poll for it: end your turn or go on with other work. When it does not, call wait_for_reply when you need the answer.
- A decision in the Inbox stays there: when the person writes in the chat, say what waits and link its thread, but never also ask it in the chat with a blocking question tool (AskUserQuestion or similar). Ask in the chat only about something new they raised there that needs no pictures or files, or when they ask.
- Be proactive about Inbox updates and about replying to the person through the Inbox when you think they would want you to. Don't withhold important updates or decisions, and don't batch updates to send later: proactivity is better than procrastination.
- Never run `plannotator inbox` just to send: send_message starts a stopped Inbox itself, and bare `plannotator inbox` opens the window for the person.
- Before your first send, run `plannotator inbox --help` and read it: every field, the full question syntax, and how to connect the MCP server.
- The `plannotator` skill, where you have it, has more.

The rest: https://github.com/backnotprop/plannotator/blob/HEAD/apps/skills/claude/plannotator-inbox/SKILL.md