Agent Skills › backnotprop/plannotator › plannotator-annotate

plannotator-annotate

GitHub

用于在 Plannotator UI 中打开并标注文档，支持普通反馈或带审批门禁的审查。自动执行命令、处理浏览器交互及解析返回结果，无需用户手动输入命令。

apps/skills/core/plannotator-annotate/SKILL.md backnotprop/plannotator

Trigger Scenarios

用户希望使用 Plannotator 对文档进行标注用户要求审查、批准或验收生成的计划或文档

Install

npx skills add backnotprop/plannotator --skill plannotator-annotate -g -y

More Options

Non-standard path

npx skills add https://github.com/backnotprop/plannotator/tree/main/apps/skills/core/plannotator-annotate -g -y

Use without installing

npx skills use backnotprop/plannotator@plannotator-annotate

指定 Agent (Claude Code)

npx skills add backnotprop/plannotator --skill plannotator-annotate -a claude-code -g -y

安装 repo 全部 skill

npx skills add backnotprop/plannotator --all -g -y

预览 repo 内 skill

npx skills add backnotprop/plannotator --list

SKILL.md

Frontmatter

{
    "name": "plannotator-annotate",
    "description": "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.",
    "disable-model-invocation": true
}

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:

Launch the command with Bash.
Wait for the browser review to finish.
If annotations are returned, address them directly.
If the session closes without feedback, say so briefly and continue.
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.
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.