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
80%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./apps/skills/core/plannotator-annotate/SKILL.mdUse 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 --jsonPlain 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:
--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.Do not ask the user to paste a shell command into the chat. Run the command yourself.
8f2a8a8
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.