Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

human-review Skill

Repository ↗

by petergyang★ 1,4571 skills

Install

What it does

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.

  • Connects Instruction files the AI reads
  • Account or key Not confirmed (README mentions a key or .env file)
  • Category Design and web UI
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/skill/petergyang-human-review.svg)](https://mcp.popnx.com/en/skills/petergyang-human-review)

Use together with

MCP servers that connect the AI to services for the same work

Next AI Draw.io

draw.io diagrams your AI agent draws on a live browser canvas that you can also edit by hand

by DayuanJiangWidely used↓ 21.7K/wk★ 37.1K Stars for the whole repoUpdated 6 days ago

MCP · Connects a serviceRuns on your computer

Pascal 3D Editor

Create, inspect, validate, and save editable 3D building scenes with Pascal's MCP server.

by pascalorgWidely used↓ 1K/wk★ 25.6K Stars for the whole repoUpdated 2 days ago

MCP · Connects a serviceComputer or cloud✓ service owner · pascal.app

Semiotic

Verified React chart generation: select, validate, repair, render, and inspect charts through MCP.

by nteractWidely used↓ 8.5K/wk★ 2.7KUpdated yesterday

MCP · Connects a serviceComputer or cloud

Similar Skills

Same kind of work, ordered like the Skills list

Compared with similar ones
This one
human-review
impeccablediagram-designfrontend-slidesguizang-ppt-skill
Makerpetergyangpbakauscathrynlaveryzarazhangruiop7418
Skills11111
GitHub stars1,457113,04268,29632,57930,091
Last code changeSep 18, 2026Nov 19, 2026Nov 19, 2026Jun 24, 2026Oct 30, 2026
LicenseMITApache-2.0MITMITAGPL-3.0

1 skills (instruction sets) by petergyang that an AI reads and follows · not an MCP server

How a Skill differs from MCP

MCP = the hands

Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.

Skill = the manual

A text file that teaches the AI how to do a task. It connects to nothing.

Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.

Works with

Claude CodeCodex

From the maker’s README and the folders in the repo

Install

Is it safe?

  • Who made it

    GitHub account petergyang (person), 14 years old

  • Use and upkeep

    ★ 1,457 stars · code last changed Sep 18, 2026

  • Any scripts?

    16 scripts that can run on a computer: cli.js, anchor-text.js, chrome-client.js, chrome-session.js and 12 more

  • Uses the internet?

    Scripts that go online: cli.js, chrome-client.js, server.js, sdk.js

  • Changes machine-wide settings?

    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

First: which AI do you use?

Pick your app and this page shows only how to install it there

Option 1Upload to claude.ai (web and app)

Uploading to claude.ai would fail: the description is over 200 characters (347). Use "Let the AI install it" instead

Option 1Let Claude Code install it

Copy this sentence and paste it into a Claude Code chat

Where to install
Please install the skill human-review from https://github.com/petergyang/human-review folder src (commit f9a5581) for all my projects, at ~/.claude/skills/human-review. First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill human-review from https://github.com/petergyang/human-review folder src (commit f9a5581) into the project this chat is open in (at .claude/skills/human-review). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

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

Restart Claude Code, then type /src or ask for a matching task and Claude picks it up

Checked against official docs Nov 12, 2026 · Source: code.claude.com

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.claude/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a 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/src
  3. Restart Claude Code, then type /src or ask for a matching task and Claude picks it up

Skills you install yourself work in the ChatGPT desktop app, Codex CLI and the Codex IDE extension · ChatGPT on the web and mobile cannot use skills you install yourself, only skills that come with a plugin from the directory

ChatGPT desktop app

The ChatGPT desktop app has Codex built in, and Codex reads skills from ~/.agents/skills

Option 1Let ChatGPT install it

Open Codex in the ChatGPT desktop app and paste this sentence into the chat

Where to install
Please install the skill human-review from https://github.com/petergyang/human-review folder src (commit f9a5581) for all my projects, at ~/.agents/skills/human-review. First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill human-review from https://github.com/petergyang/human-review folder src (commit f9a5581) into the project this chat is open in (at .agents/skills/human-review). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

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

Option 2Put the folder there yourself

Put the human-review folder at ~/.agents/skills/human-review

~ is your home folder ($HOME)

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.agents/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a 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

After installing

  • ChatGPT desktop app: open Skills in the sidebar to see that the skill is there
  • To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
  • Codex picks up newly installed skills by itself; if one does not show up, restart Codex

Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com

ChatGPT on the web and mobile

Skills you install yourself do not work here; only skills that come with a plugin from the directory

To use this skill with ChatGPT, use the ChatGPT desktop app as above

Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com

Option 1Let Codex install it

Copy this sentence and paste it into a Codex chat · Works in Codex inside the ChatGPT desktop app, Codex CLI and the IDE extension

Where to install
Please install the skill human-review from https://github.com/petergyang/human-review folder src (commit f9a5581) for all my projects, at ~/.agents/skills/human-review. First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill human-review from https://github.com/petergyang/human-review folder src (commit f9a5581) into the project this chat is open in (at .agents/skills/human-review). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

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 picks up newly installed skills by itself; if one does not show up, restart Codex · To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name

Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.agents/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a 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
  3. Restart Codex, then ask for a matching task; Codex lists the skill

Option 1Let Cursor install it

Copy this sentence and paste it into a Cursor chat

Where to install
Please install the skill human-review from https://github.com/petergyang/human-review folder src (commit f9a5581) for all my projects, at ~/.cursor/skills/human-review. First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill human-review from https://github.com/petergyang/human-review folder src (commit f9a5581) into the project this chat is open in (at .cursor/skills/human-review). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

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

In Cursor’s Agent chat, type / and pick src

Checked against official docs Nov 12, 2026 · Source: cursor.com

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.cursor/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a 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/src
  3. In Cursor’s Agent chat, type / and pick src

Option 1Let the AI install it

For other apps that read skills. The sentence gives the paths for Claude Code, Codex and Cursor so the AI picks the one for your app · Copy this sentence into the app’s chat

Where to install
Please install the skill human-review from https://github.com/petergyang/human-review folder src (commit f9a5581) for all my projects, at ~/.claude/skills/human-review (in Codex use ~/.agents/skills/human-review, in Cursor ~/.cursor/skills/human-review). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill human-review from https://github.com/petergyang/human-review folder src (commit f9a5581) into the project this chat is open in (at .claude/skills/human-review; in Codex use .agents/skills/human-review, in Cursor .cursor/skills/human-review). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

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 Nov 12, 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com

For Terminal users

Other apps that support Agent Skills (such as Gemini CLI or GitHub Copilot) use different folders. Check that app’s guide, then copy the folder with the SKILL.md there.

View on GitHub ↗

Skill folders checked against the official Claude Code, Codex and Cursor guides on Nov 11, 2026

✓ Commands checked Nov 19, 2026

View the original SKILL.md

The text below comes from the maker’s repo, not from PopNx MCP

Showing the first 8,000 characters · Open the full file on 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
  `![](assets/...)`. 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

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

From GitHub

GitHub stars
1,457
Maker
petergyang
License
MIT
Last code change
Sep 18, 2026
SKILL.md files in the repo (including translated copies and templates)
1
Topics
ai-agents, claude-code, cli, codex, feedback, html, human-in-the-loop, markdown, review