Open Plannotator's annotation UI for a file, folder, or URL, then address the returned annotations.
SkillScore29Maintained
On-demandOn-demand: invoked explicitly — never occupies your agent's context until called.
◆Doc Ops pack
Last verified 9/8/2026
What it changes
Passed 2 of 8 test cases with the skill, and 2 of 8 without it.
Without skill25%
With skill29%
Checks it passed that the model alone missed
States that approved feedback serves as guidance.
States that the `--gate` flag is required for approval functionality.
2 fixed5 passed either way16 still failing1 broke
Pass-rate lift
+4 pp
Tokens
-25%
Agent turns
0%
Response time
-26%
Model gemini-3.6-flashMeasured 9/8/2026v7 · latest is v87 of 24 cases passed with skill · 8 comparable
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.6-flash on 10/2/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
See it in action
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 2
Prompt
I opened `docs/roadmap.md` with `plannotator annotate docs/roadmap.md`. Will I see an Approve button in the browser UI to officially gate this roadmap?
What was checked, without and with the skill
Checked
Without skill
With skill
States that plain annotate mode lacks an Approve button.
Passed
Passed
States that the `--gate` flag is required for approval functionality.
Missed
Passed
case-08 · gemini-3.6-flash · 9/8/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
$ARGUMENTS should be a markdown or plain-text config file path (.md, .txt, .yaml, .json, .toml, .ini, .csv, .log, …), folder path, html file path, or URL.
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.
Review Renovate bot PRs that update GitHub Actions dependencies. Verifies supply chain integrity by checking pinned commit SHAs against upstream tagged releases, reviews changelogs for breaking changes, and confirms compatibility with existing workflow configurations. Use when a Renovate PR updates GitHub Actions in .github/workflows/.