Open Plannotator's annotation UI for a markdown file, HTML file, URL, or folder and then respond to the returned annotations.
67
84%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
!plannotator annotate $ARGUMENTS
The output above will be one of:
The user approved., an "Approved with Notes" message, OR a JSON object with "decision": "approved". The user approved the markdown file(s). If it is the Approved with Notes message, or that object also carries a "feedback" field, the user approved with notes: read them and carry them into subsequent work — they are non-blocking guidance, not a request to revise the file. Otherwise acknowledge with a single sentence ("Approved.") and stop. Either way, do not begin any work."decision": "dismissed". The user closed the session without requesting changes. Acknowledge with a single sentence ("Annotation session closed.") and stop. Do not begin any work."decision": "annotated" and a "feedback" field. Address the feedback. The user has reviewed the markdown file(s) and provided specific annotations and comments.plannotator annotate <path-or-url> yourself with that concrete target (keeping any flags the message echoes), then handle its output per cases 1-3.backnotprop/plannotator
bbcaa97
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.