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의 Skill(지시 묶음) 1개, 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질문하고, 팁을 나누고, 안 되는 점을 알려 주세요. "도움이 됨"이 많은 순서예요.