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.
作者の方は、このコードを README に貼れます。バッジはこのページにリンクします。
[](https://mcp.popnx.com/en/skills/petergyang-human-review)同じ作業で AI をサービスにつなぐ MCP
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.
同じ種類の作業。Skill 一覧と同じ並び
| これ human-review | impeccable | diagram-design | frontend-slides | guizang-ppt-skill | |
|---|---|---|---|---|---|
| 作者 | petergyang | pbakaus | cathrynlavery | zarazhangrui | op7418 |
| Skill 数 | 1 | 1 | 1 | 1 | 1 |
| GitHub スター | 1,457 | 113,042 | 68,296 | 32,579 | 30,091 |
| 最終コード更新 | 2026年9月18日 | 2026年11月19日 | 2026年11月19日 | 2026年6月24日 | 2026年10月30日 |
| ライセンス | MIT | Apache-2.0 | MIT | MIT | AGPL-3.0 |
petergyang による 1 個の Skill(指示セット)。AI が読んでそのとおりに作業します · MCP server ではありません
MCP = 手
AI を外部のサービスやデータにつなぎます(例:Notion を読む、請求書を作る)。プログラムやサーバーが動いている必要があります。
Skill = 手順書
作業のやり方を AI に教えるテキストファイル。どのサービスにもつながりません。
重なる部分もあります。ツールを呼ぶスクリプト付きの Skill や、知識だけを渡す MCP もあります。やりたい作業から選んでください。
Claude CodeCodex
提供元の README と repo のフォルダから判断
GitHub account petergyang (person), 14 years old
★ 1,457 stars · code last changed 2026年9月18日
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
まず:どの AI を使っていますか
使っているアプリを選ぶと、そのアプリでのインストール方法だけが表示されます
Uploading to claude.ai would fail: the description is over 200 characters (347). Use "Let the AI install it" instead
この文をコピーして 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
Claude Code を開き直し、/src と入力するか関連する作業を頼むと Claude が自動で使います
Checked against official docs 2026年11月12日 · Source: code.claude.com
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、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/srcChatGPT デスクトップアプリには Codex が組み込まれていて、Codex は ~/.agents/skills フォルダから Skill を読み込みます
ChatGPT デスクトップアプリで Codex を開き、この文をチャットに貼り付けます
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
human-review フォルダを ~/.agents/skills/human-review に置きます
~ はホームフォルダ($HOME)です
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、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 2026年11月15日 · Source: learn.chatgpt.com
自分でインストールした Skill は使えません。ディレクトリのプラグインに含まれる Skill だけが使えます
この Skill を ChatGPT で使うには、上の方法で ChatGPT デスクトップアプリを使ってください
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
この文をコピーして Codex のチャットに貼り付けます · ChatGPT デスクトップアプリ内の Codex、Codex CLI、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 は新しくインストールした Skill を自動で見つけます。表示されない場合は Codex を再起動してください · 使い方:ChatGPT では @ を入力して Skill を選びます · Codex CLI や IDE 拡張機能では /skills を実行するか、$ に続けて Skill 名を入力します
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、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/srcこの文をコピーして 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
Cursor の Agent チャットで / を入力し src を選ぶ
Checked against official docs 2026年11月12日 · Source: cursor.com
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、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/srcSkill を読めるほかのアプリ向けです。この文には Claude Code、Codex、Cursor のパスが入っていて、AI が使っているアプリに合わせて選びます · 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 2026年11月12日 · Source: code.claude.com, learn.chatgpt.com, cursor.com
Gemini CLI や GitHub Copilot など Agent Skills 対応の他のアプリはフォルダが違います。そのアプリのガイドを見て、SKILL.md のあるフォルダをコピーしてください。
2026年11月11日 に Claude Code、Codex、Cursor の公式ガイドで skill フォルダを確認
✓ コマンド確認済み 2026年11月19日
以下は提供元の repo の文章で、PopNx MCP の指示ではありません
最初の 8,000 文字を表示 · 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 us質問、コツの共有、使えないことの報告ができます。「役に立った」の多い順です。