Plannotator Annotate

backnotprop/plannotator/apps/skills/core/plannotator-annotate

by backnotpropeb9572ec8f648ff1cac54382b498465ac802a4c7No license9.2K starsListed Oct 9, 2026Updated Oct 9, 2026Repository updated today

Open Plannotator's annotation UI for a markdown file, plain-text config file (.yaml, .json, .toml, .ini, .csv, .log, …), HTML file, URL, or folder and then respond to the returned annotations.

Instructions onlyProductivity & Workflow
AI-generated overview

Opens Plannotator's annotation UI for a file, URL or folder and handles the returned annotations.

What it does
This skill launches the Plannotator annotation interface on a markdown file, plain-text config file, HTML file, URL or folder, then waits for the browser review to finish. It addresses any returned annotations, reports when a session closes without feedback, and can run in a gated mode that supports approval decisions, including approvals that carry notes. It also resolves an ambiguous target to a concrete path or URL and re-runs the command itself.
When to use it
Use it when the user wants a document annotated in Plannotator rather than reviewed inline in chat. Use the gated form when the user asks to review, approve, accept or gate a generated plan, spec or document.
Requirements
Requires the plannotator command-line tool to be installed and runnable via Bash, plus a browser for the review session. No scripts are shipped; instructions only.

Plannotator Annotate

Use this skill when the user wants to annotate a document in Plannotator instead of reviewing it inline in chat.

Run for ordinary annotation/feedback:

bash
plannotator annotate <path-or-url>

Run when the user asks to review, approve, accept, or gate a generated plan/spec/document:

bash
plannotator annotate <path-or-url> --gate --json

Plain annotate has no Approve button; it only supports feedback or closing the session. Never promise an approval action unless --gate is present. --json only changes the output format and does not enable approval by itself.

Behavior:

  1. Launch the command with Bash.
  2. Wait for the browser review to finish.
  3. If annotations are returned, address them directly.
  4. If the session closes without feedback, say so briefly and continue.
  5. In a --gate session, an approval may still carry notes — a "decision": "approved" result with a "feedback" field (without --json, an "Approved with Notes" message). Read those notes and carry them into subsequent work, but do not revise the document over them: they are guidance, not a change request.
  6. If the command reports that the arguments could not be resolved to a file, URL, or folder, work out which target the user means and re-run the command yourself with that concrete path or URL.

Do not ask the user to paste a shell command into the chat. Run the command yourself.

Source and attribution

Source:backnotprop/plannotatorinapps/skills/core/plannotator-annotateat commiteb9572e

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal