Agent Skills
› backnotprop/plannotator
› plannotator-annotate
plannotator-annotate
GitHub用于打开 Plannotator 注释 UI 并处理用户反馈。支持 Markdown、HTML、URL 或文件夹,根据审批、驳回或具体意见执行相应操作。
Trigger Scenarios
需要获取用户对文档的审阅意见
接收自然语言描述的文件/链接并请求注释
Install
npx skills add backnotprop/plannotator --skill plannotator-annotate -g -y
SKILL.md
Frontmatter
{
"name": "plannotator-annotate",
"description": "Open Plannotator's annotation UI for a markdown file, HTML file, URL, or folder and then respond to the returned annotations.",
"allowed-tools": "Bash(plannotator:*)",
"disable-model-invocation": true
}
Plannotator Annotate
Markdown annotations
!plannotator annotate $ARGUMENTS
Your task
The output above will be one of:
- The exact text
The user approved., OR a JSON object with"decision": "approved". The user approved the markdown file(s). If 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. - Empty, OR a JSON object with
"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. - Plaintext annotation feedback, OR a JSON object with
"decision": "annotated"and a"feedback"field. Address the feedback. The user has reviewed the markdown file(s) and provided specific annotations and comments. - A message that the arguments could not be resolved to a file, URL, or folder. The user described what to annotate in natural language: work out which file, URL, or folder they mean, run
plannotator annotate <path-or-url>yourself with that concrete target (keeping any flags the message echoes), then handle its output per cases 1-3.
Version History
- 2ca55c8 Current 2026-08-20 12:32


