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.
Profile →npx skills add backnotprop/plannotator --skill plannotator-annotate --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Plannotator Annotate Use this skill when the user wants to annotate a document in Plannotator instead of reviewing it inline in chat. Run: ```bash plannotator annotate <path-or-url> ``` 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. 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.
plannotator annotate <path-or-url>
What does the plannotator-annotate skill do?
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.
How do I install it?
Run `npx skills add backnotprop/plannotator --skill plannotator-annotate --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From backnotprop/plannotator, a repository with 7,510 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.