CtrlK
BlogDocsLog inGet started
Tessl Logo

plannotator-annotate

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.

67

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./apps/skills/core/plannotator-annotate/SKILL.md
SKILL.md
Quality
Evals
Security

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:

plannotator annotate <path-or-url>

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

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 --json session, an approval may still carry notes — a "decision": "approved" result with a "feedback" field. 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.

Repository
backnotprop/plannotator
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.