Next AI Draw.io
draw.io diagrams your AI agent draws on a live browser canvas that you can also edit by hand
A visual tool to edit HTML and Markdown files, leave comments like a Google Doc, and send feedback to your AI agent. Works inside your favorite AI harness.
Si lo creaste tú, pega este código en tu README. La insignia enlaza a esta página.
[](https://mcp.popnx.com/en/skills/petergyang-human-review)Servidores MCP que conectan la IA a servicios para el mismo trabajo
draw.io diagrams your AI agent draws on a live browser canvas that you can also edit by hand
Create, inspect, validate, and save editable 3D building scenes with Pascal's MCP server.
Verified React chart generation: select, validate, repair, render, and inspect charts through MCP.
Mismo tipo de trabajo, ordenadas como la lista de Skills
| Este human-review | impeccable | diagram-design | frontend-slides | guizang-ppt-skill | |
|---|---|---|---|---|---|
| Autor | petergyang | pbakaus | cathrynlavery | zarazhangrui | op7418 |
| Skills | 1 | 1 | 1 | 1 | 1 |
| Estrellas de GitHub | 1457 | 113.042 | 68.296 | 32.579 | 30.091 |
| Último cambio de código | 18 sept 2026 | 19 nov 2026 | 19 nov 2026 | 24 jun 2026 | 30 oct 2026 |
| Licencia | MIT | Apache-2.0 | MIT | MIT | AGPL-3.0 |
1 skills (conjuntos de instrucciones) de petergyang que la IA lee y sigue · no es un MCP server
MCP = las manos
Conecta la IA a un servicio o dato externo, como leer Notion o crear una factura. Necesita un programa o servidor en marcha.
Skill = el manual
Un archivo de texto que enseña a la IA cómo hacer una tarea. No se conecta a nada.
A veces se parecen: algunas Skills ejecutan scripts que llaman herramientas y algunos MCP solo envían conocimiento. Empieza por la tarea que quieres hacer.
Claude CodeCodex
Según el README del autor y las carpetas del repo
GitHub account petergyang (person), 14 years old
★ 1457 stars · code last changed 18 sept 2026
16 scripts that can run on a computer: cli.js, anchor-text.js, chrome-client.js, chrome-session.js and 12 more
Scripts that go online: cli.js, chrome-client.js, server.js, sdk.js
No hooks or writes to machine settings found
Checked automatically from the repo files at commit f9a5581 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
Primero: ¿qué IA usas?
Elige tu app y esta página mostrará solo cómo instalarlo en ella
Uploading to claude.ai would fail: the description is over 200 characters (347). Use "Let the AI install it" instead
Copia esta frase y pégala en un chat de Claude Code
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Vuelve a abrir Claude Code y escribe /src, o pide una tarea relacionada y Claude lo usará
Checked against official docs 12 nov 2026 · Source: code.claude.com
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
git clone --depth 1 https://github.com/petergyang/human-review.git /tmp/popnx-skill-petergyang-human-review-f9a5581 && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-petergyang-human-review-f9a5581/src' ~/.claude/skills/srcLa app de escritorio de ChatGPT incluye Codex, y Codex lee las skills de la carpeta ~/.agents/skills
Abre Codex en la app de escritorio de ChatGPT y pega esta frase en el chat
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Coloca la carpeta human-review en ~/.agents/skills/human-review
~ es tu carpeta de inicio ($HOME)
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
git clone --depth 1 https://github.com/petergyang/human-review.git /tmp/popnx-skill-petergyang-human-review-f9a5581 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-petergyang-human-review-f9a5581/src' ~/.agents/skills/srcChecked against official docs 15 nov 2026 · Source: learn.chatgpt.com
Las skills que instalas tú no funcionan aquí; solo las que vienen con un plugin del directorio
Para usar esta skill con ChatGPT, usa la app de escritorio de ChatGPT como se indica arriba
Checked against official docs 15 nov 2026 · Source: learn.chatgpt.com
Copia esta frase y pégala en un chat de Codex · Sirve en Codex dentro de la app de escritorio de ChatGPT, en Codex CLI y en la extensión del IDE
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex detecta solo las skills recién instaladas; si una no aparece, reinicia Codex · Para usarla: en ChatGPT escribe @ y elige la skill · en Codex CLI o la extensión del IDE ejecuta /skills o escribe $ y el nombre de la skill
Checked against official docs 15 nov 2026 · Source: learn.chatgpt.com
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
git clone --depth 1 https://github.com/petergyang/human-review.git /tmp/popnx-skill-petergyang-human-review-f9a5581 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-petergyang-human-review-f9a5581/src' ~/.agents/skills/srcCopia esta frase y pégala en un chat de Cursor
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
En el chat Agent de Cursor escribe / y elige src
Checked against official docs 12 nov 2026 · Source: cursor.com
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
git clone --depth 1 https://github.com/petergyang/human-review.git /tmp/popnx-skill-petergyang-human-review-f9a5581 && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-petergyang-human-review-f9a5581/src' ~/.cursor/skills/srcPara otras apps que leen skills. La frase incluye las rutas de Claude Code, Codex y Cursor para que la IA elija la de tu app · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs 12 nov 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
Otras apps con Agent Skills (como Gemini CLI o GitHub Copilot) usan otras carpetas. Mira la guía de esa app y copia allí la carpeta con el SKILL.md.
Carpetas de skills comprobadas con las guías oficiales de Claude Code, Codex y Cursor el 11 nov 2026
✓ Comandos revisados el 19 nov 2026
El texto siguiente viene del repo del autor, no de PopNx MCP
Se muestran los primeros 8000 caracteres · Abrir el archivo completo en GitHub
---
name: human-review
description: Open an HTML file, Markdown file, or localhost page in the browser so the user can edit text directly and leave comments on specific parts, then send all edits and comments back to you. Use after writing or updating something the user will read — specs, plans, reports, newsletter drafts, landing pages, slide decks, and locally running web pages.
---
# human-review
The user reviews your HTML, Markdown, or localhost page in a real browser: they fix small things
by typing, select anything to comment on it, and send you the whole batch at once.
Markdown files open rendered. Their quotes and edits reference the rendered text,
and the file itself is never touched — apply every change to the Markdown source,
keeping its formatting syntax.
## The loop
1. Write or update the HTML or Markdown file, or start the local page being reviewed.
2. Open it for the user:
```sh
npx -y human-review path/to/file.html
```
For a page served by a local development server, open the real route instead
of recreating it as a separate HTML file:
```sh
npx -y human-review http://localhost:3000/wiki
```
3. Wait for feedback. This command blocks until the user hits Send in the
browser, then prints their batch and exits:
```sh
npx -y human-review poll path/to/file.html
```
The command exits only when the user clicks Send or closes the review.
There is nothing to re-run, no interval to poll on, and no `--timeout` to
add. It survives the local server restarting, and feedback is saved even
if the poll dies, so nothing is ever lost. How you wait depends on your
harness:
- **Claude Code:** run it with `run_in_background: true` and end your turn.
Claude Code wakes you with the output the moment the command exits.
- **Codex, Cursor, and everything else:** run it in the **foreground**,
inside your active turn, and stay on it until it prints `feedback` or
`closed`. Do not detach it or start it as a background session: nothing
wakes you when a detached command finishes. While the review is active:
- If the user sends a message, answer it as commentary and immediately
resume the foreground poll in the same turn. Do not send a final
response until the poll returns `feedback` or `closed` — a final
response ends the turn and kills the wait.
- If your shell tool caps command duration, pass `--timeout` a little
under the cap and run bounded polls back to back in the same active
turn until one returns `feedback` or `closed`.
Know the limit: this is reliable only while your turn stays active. A
turn that has already ended is not woken when the user hits Send; the
user has to message you, and you then run `status` and `poll` to pick
the batch up. There is no integration that resumes an ended task when
the poll exits.
If it prints `{"status":"closed"}`, the review is over: the user ended it,
closed the tab, or never had one open (`reason` says which). Stop and do
not start another poll. `unsent` counts feedback they left behind; if it is
not zero, tell the user in one line that it is kept and they can restore or
discard it next time. `{"status":"superseded"}` means a newer poll of
yours owns the wait — stop this one silently. `{"status":"timeout"}` only
appears after 12 hours; run `status` and start the wait again if the
review is still open.
4. Apply what comes back, then start the next background poll. `--ack` clears
the batch you just handled:
```sh
npx -y human-review poll path/to/file.html --ack
```
Repeat 3–4 until the user says they are done.
Not sure whether feedback is already waiting — say, at the start of a new turn
with no poll running? This answers instantly without blocking:
```sh
npx -y human-review status path/to/file.html
```
It prints `{"status": "feedback-waiting"}` when a batch is ready for a poll,
plus counts of unsent comments and edits still in the browser.
## What you get
One batch covers every page the user visited, grouped by file or localhost URL.
```json
{
"status": "feedback",
"pages": [
{
"file": "/abs/path/to/page.html",
"edits_saved": true,
"comments": [
{ "id": "c_1", "kind": "selection", "quote": "the exact text they selected",
"anchor": { "prefix": "...", "quote": "...", "suffix": "..." },
"feedback": "what they want changed" }
],
"edits": [
{ "label": "Problem body", "kind": "edited",
"before": "the original wording",
"after": "their exact new wording",
"after_html": "their exact new wording with <strong>formatting</strong>" }
]
}
],
"overall_note": "feedback not tied to any one page"
}
```
## Rules
- **`edits` are changes the user already made.** `after` is their exact wording —
carry it across verbatim and never revert it. If the HTML was generated from
something else (MDX, Markdown, a template), apply `after` to the **source** too,
or their fix disappears on the next build.
- **`edits_saved: true` means those edits are already in the file on disk.**
Plain HTML files autosave as the user types, so your copy of the file is
stale. Re-read the file before touching it and make targeted changes only;
never regenerate it from what you wrote earlier, or their work disappears.
`edits_saved: false` (Markdown, localhost pages, self-rendering HTML) means the
edits exist only in this batch — apply them to the source yourself.
- An edit with `kind: "deleted"` means the user removed that whole block:
delete it from the source too, without asking why.
- An edit marked `truncated: true` had its text cut at 200k characters; read
the block from the page itself rather than from `after_html`.
- When `before_html`/`after_html` are present, the user changed formatting, not
just words — bold, italic, underline, links. Use the HTML version to carry the
formatting into the source, translated to its syntax (e.g. `<strong>` → `**`
in Markdown/MDX).
- A page with `kind: "url"` was edited directly in the review UI. Its `file`
and `url` fields name the localhost route, not a writable file. Find the
matching project source (such as MDX, TSX, or a template), apply every edit
and deletion there, then acknowledge so the route reloads. Never write the
rendered HTTP response back into the app.
- When an edit's `after_html` contains `<img src="assets/...">`, the user pasted
an image: the file already exists in an `assets/` folder next to the reviewed
file. Keep that relative path — in Markdown, reference it as
``. Never regenerate or inline the image.
- On a localhost page, a pasted image arrives under `staged_assets`. Copy its
local `path` into the app's appropriate asset folder, replace the temporary
preview URL in `after_html`, and preserve the image at the user's insertion
point. Never leave the temporary preview URL in source.
- An edit with `kind: "moved"` means the user relocated that whole block.
Reposition it in the source without rewriting its content: it now sits right
after the block whose text starts with `moved_after`, and right before the
block whose text starts with `moved_before` (both are clipped to 90
characters and may end in `…`). An empty `moved_after` means it is now the
first block in its container.
- Find each comment by its `quote`. It is the **rendered** text the user
selected, so in Markdown or templated HTML it may span formatting syntax or
tags; `anchor.prefix` and `anchor.suffix` give the surrounding text to
disambiguate.
- `kind: "element"` points at a whole block, so `quote` is its label, not body text.
- Copy any `staged_assets` files before you ack: `--ack` deletes them.
- A batch with only an `overall_note` has an empty `pages` array.
- Fix every page in `pages`, not just the first.
- **Do not write a reply.** There is no chat. The usPregunta, comparte un consejo o avisa de que no funciona. Ordenado por lo que la gente marcó como útil.
Aún no hay publicaciones. Sé la primera persona en preguntar o compartir.
Lo publicado aquí lo escriben usuarios, no el equipo de PopNx.