Skip to main content

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.

Informações da origem

Repositório
backnotprop/plannotator
Última atividade na origem
6 de outubro de 2026 às 03:38
Idioma detectado do SKILL.md
inglês
Estrelas
9.342
Forks
701

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Explorador de arquivos
2 arquivos

Exibindo SKILL.md

SKILL.md
Instruções da origem · Visualização somente leitura
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: ```bash plannotator annotate <path-or-url> ``` Run when the user asks to review, approve, accept, or gate a generated plan/spec/document: ```bash 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: 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. In a `--gate` session, an approval may still carry notes — a `"decision": "approved"` result with a `"feedback"` field (without `--json`, an "Approved with Notes" message). 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.
Ver no GitHub