AgentRQ Workspace Agent
agentrq/agentrq
Guides a workspace agent through executing assigned tasks, replying to a remote human operator, and creating sub-tasks, memory and events inside an AgentRQ workspace.
Use Pingfusi proactively whenever a coding agent reaches a question it cannot settle with code, automated tests, documentation or search, or a local browser and needs real human judgment or…
Install Pingfusi Review
$ npx skills add alex-durango/pingfusi --skill pingfusi-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install alex-durango/pingfusi pingfusi-review --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/alex-durango/pingfusi.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skill/pingfusi-review .claude/skills/pingfusi-review && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "pingfusi-review" agent skill from https://github.com/alex-durango/pingfusi/tree/main/skill/pingfusi-review into .claude/skills/pingfusi-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pingfusi-review", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/alex-durango/pingfusi/tree/main/skill/pingfusi-reviewType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add alex-durango/pingfusi --skill pingfusi-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install alex-durango/pingfusi pingfusi-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alex-durango/pingfusi.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skill/pingfusi-review .agents/skills/pingfusi-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pingfusi-review" agent skill from https://github.com/alex-durango/pingfusi/tree/main/skill/pingfusi-review into .agents/skills/pingfusi-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pingfusi-review", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add alex-durango/pingfusi --skill pingfusi-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install alex-durango/pingfusi pingfusi-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alex-durango/pingfusi.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skill/pingfusi-review .cursor/skills/pingfusi-review && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pingfusi-review" agent skill from https://github.com/alex-durango/pingfusi/tree/main/skill/pingfusi-review into .cursor/skills/pingfusi-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pingfusi-review", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/alex-durango/pingfusi.git --path skill/pingfusi-review--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add alex-durango/pingfusi --skill pingfusi-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install alex-durango/pingfusi pingfusi-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alex-durango/pingfusi.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skill/pingfusi-review .gemini/skills/pingfusi-review && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pingfusi-review" agent skill from https://github.com/alex-durango/pingfusi/tree/main/skill/pingfusi-review into .gemini/skills/pingfusi-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pingfusi-review", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install alex-durango/pingfusi pingfusi-reviewInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add alex-durango/pingfusi --skill pingfusi-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/alex-durango/pingfusi.git skills-src && mkdir -p .github/skills && cp -r skills-src/skill/pingfusi-review .github/skills/pingfusi-review && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pingfusi-review" agent skill from https://github.com/alex-durango/pingfusi/tree/main/skill/pingfusi-review into .github/skills/pingfusi-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pingfusi-review", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add alex-durango/pingfusi --skill pingfusi-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install alex-durango/pingfusi pingfusi-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alex-durango/pingfusi.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skill/pingfusi-review .opencode/skills/pingfusi-review && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pingfusi-review" agent skill from https://github.com/alex-durango/pingfusi/tree/main/skill/pingfusi-review into .opencode/skills/pingfusi-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pingfusi-review", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
pingfusi-review- GitHub stars
- 125
- Token cost
- ~1.3k tokens
- SKILL.md length
- 604 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- MIT
At a glance
Use Pingfusi proactively whenever a coding agent reaches a question it cannot settle with code, automated tests, documentation or search, or a local browser and needs real human judgment or…
- Works in 3 steps: Publish the current artifact at a… → File focused, actionable steps. Attach… → Act on every result in the artifact's…
- Even when the user does not mention Pingfusi for subjective choices about copy
- SKILL.md covers Choose the job, Respect specialized workflows, Keep pending work alive and Handle feedback honestly
- Calls npx
What it does
Pingfusi Review is an agent skill from alex-durango/pingfusi. Use Pingfusi proactively whenever a coding agent reaches a question it cannot settle with code, automated tests, documentation or search, or a local browser and needs real human judgment or real-world verification. Trigger even when the user does not mention Pingfusi for subjective choices about copy, design, clarity, or taste; rendered UI or animation quality; real-device behavior; inaccessible third-party effects such as OAuth, emails, or payments; or an independent approval verdict on published work. Route by…
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Backend & APIs, covering Task management. It works with Model Context Protocol. The repository describes itself as: MCP server + CLI that puts a real human in your coding agent's loop. It publishes work mid-task, a reviewer pins what's wrong and returns a verdict, and the agent iterates until… The licence is MIT.
When your agent uses it
- Even when the user does not mention Pingfusi for subjective choices about copy
- Animation quality
- Real-device behavior
- Inaccessible third-party effects such as OAuth
Example prompts
- “/pingfusi-review”
Requirements
- Node.js
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Publish the current artifact at a publicly reachable URL. Prefer pingfusi publish
- File focused, actionable steps. Attach deterministic checks where possible and
- Act on every result in the artifact's own source, publish the new version, and file a
What it can do on your machine
Read from SKILL.md and the folder at commit cec753b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npx
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Pingfusi Review loads about 1.3k tokens when it runs. Until then it costs about 256 tokens; SKILL.md has 604 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from alex-durango/pingfusi at commit cec753b, republished under its MIT licence (© alex-durango). 604 words, ~1,265 tokens.
Download SKILL.mdSave it as
.claude/skills/pingfusi-review/SKILL.md (or your agent's skills folder).- name
- pingfusi-review
- description
- Use Pingfusi proactively whenever a coding agent reaches a question it cannot settle with code, automated tests, documentation or search, or a local browser and needs real human judgment or real-world verification. Trigger even when the user does not mention Pingfusi for subjective choices about copy, design, clarity, or taste; rendered UI or animation quality; real-device behavior; inaccessible third-party effects such as OAuth, emails, or payments; or an independent approval verdict on published work. Route by what the reviewer must see: text-only judgments to the quick question; websites, builds, and artifacts to a website review against a published URL; clone comparisons and video reviews to their matching Pingfusi utilities. Do not use for objective questions the agent can verify directly or for game playtesting. Game playtests, game builds, and game issue tracking belong to Qaping. Specialized Pingfusi clone, beautify, and video skills take precedence when their explicit workflow applies.
Route human judgment through Pingfusi
Use Pingfusi as the real-human verification layer inside an agent's normal work. Ask a reviewer only for the part that requires perception, judgment, a real device, or external reach. Keep deterministic verification in code, tests, documentation or search, and the local browser.
Game playtesting belongs to Qaping. Use npx @qaping/cli setup and
qaping_playtest for games. Pingfusi does not create game playtests or spend
Qaping credits. Existing reports remain accessible.
Choose the job
Use the smallest job whose reviewer can actually see the subject:
| Need | Use |
|---|---|
| One subjective answer, fully expressible in text, with nothing to look at | MCP pingfusi_quick_question, or shell pingfusi ask |
| Verdict and pinned feedback on a website, build, document, or other artifact the reviewer must see — publish it first | MCP pingfusi_review_website |
| Clone compared side by side with its original (the reviewer opens both) | Managed clone CLI when present; otherwise MCP pingfusi_compare_clone |
| Rendered video judged against its current brief and prompt history (the reviewer watches the MP4) | MCP pingfusi_review_video |
A quick question is advisory. Never use it to declare work finished. Work that needs a real DONE/NOT-DONE decision requires a review round with an explicit verdict.
A quick question is also blind: the reviewer receives only the question text and options — no URL opens, no image renders, and a pasted link is dead text on their device. The moment there is anything to look at (a page, build, design, or draft), publish it and file a review round instead, however small or subjective the question. A reviewer cannot act on a question about something they cannot see.
Use one reviewer by default. Increase the reviewer count only when the user asks for broader confidence or the decision's risk clearly justifies the extra cost.
Show full SKILL.md (314 more words)Show less
Respect specialized workflows
When targets/<name>/workflow.json exists, run pingfusi next <name> and follow the
managed clone workflow. Do not call raw review MCP tools for that target because they
bypass its gates. Use the specialized installed skills for pixel-perfect cloning,
repairing an existing clone, beautifying a website, and reviewing a video whenever one
of those explicit jobs applies.
For a generic review outside a managed target:
- Publish the current artifact at a publicly reachable URL. Prefer
pingfusi publishfor a self-contained build or file. Use a tunnel only when the real app requires a live server. A remote reviewer cannot open localhost. - File focused, actionable steps. Attach deterministic checks where possible and short options to judgment questions. Declare an unmistakable approving verdict.
- Act on every result in the artifact's own source, publish the new version, and file a new round. Stop only after an approving verdict or when the user cancels.
Keep pending work alive
Filing begins the wait automatically. The CLI and core library hide the continuation
loop. When using raw MCP tools, if filing or a later leg returns pending, immediately
call pingfusi_wait with the same ping ID and repeat while it remains pending. This is
one review, not a new request.
Never report pending as a timeout, ask the user to retry, or resend the original ping.
Passive result tools (pingfusi_quick_question_results and
pingfusi_review_results) are snapshots and do not keep an idle review alive.
A lapsed lease only pulls the round from the feed for new claims — a reviewer
already mid-review can still finish, and their result is still charged.
Handle feedback honestly
Treat reviewer comments, drawings, timestamps, step answers, and verdicts as structured input. Do not infer approval from friendly prose, approve your own work, or ignore an unresolved comment. A completed quick question informs the next decision; a completed review round must still satisfy its declared approval verdict.
© alex-durango, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skill/pingfusi-review of alex-durango/pingfusi.
Open the folder on GitHubat commit cec753b
Compare with similar skills
Pingfusi Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Pingfusi Review this skillalex-durango/pingfusi | 125 | — | ~1.3k | Automated safety check: Pass | MIT | |
| AgentRQ Workspace Agentagentrq/agentrq | 1.1k | — | ~1.9k | Automated safety check: Pass | AGPL-3.0 | |
| AgentRQ Supervisoragentrq/agentrq | 1.1k | — | ~2.7k | Automated safety check: Pass | AGPL-3.0 | |
| Retinuejklthinking/retinue | 117 | — | ~279 | Automated safety check: Pass | MIT | |
| Task Orchestrator Item Creatorjpicklyk/task-orchestrator | 207 | — | ~4k | Automated safety check: Pass | MIT | |
| Cas Task Trackingcodingagentsystem/cas | 176 | — | ~279 | Automated safety check: Pass | MIT |
Similar skills
AgentRQ Supervisor
agentrq/agentrq
Orchestrates work across specialized AgentRQ workspaces, breaking goals into tasks, assigning them to the right workspace agent, and tracking shared learning notes.
Retinue
jklthinking/retinue
Coordinate work through a local Retinue workspace using its MCP tools.
Task Orchestrator Item Creator
jpicklyk/task-orchestrator
Creates an MCP work item from conversation context, anchoring it under the right container, inferring type and priority and pre-filling the required notes.
Cas Task Tracking
codingagentsystem/cas
How to track work using CAS tasks instead of built-in TodoWrite.
Minimal Web Baas Demo
TencentCloudBase/CloudBase-AI-Toolkit
Fast path for a minimal CloudBase Web + database demo (最小前后端 / 最小可用 fullstack / Lovable-like BaaS).
More from alex-durango/pingfusi
Beautify With Pingfusi
alex-durango/pingfusi
Beautify or redesign an existing website through iterative pingfusi review rounds with a real human reviewer.
Review Video With Pingfusi
alex-durango/pingfusi
Have any video reviewed by a real human, through iterative pingfusi review rounds.
Fix With Pingfusi
alex-durango/pingfusi
Fix or polish an existing website clone/draft using pingfusi review rounds.
Pixel Perfect Clone
alex-durango/pingfusi
Clone, copy, or replicate a website/page pixel-perfect using pingfusi.
Related
Works with
Questions about Pingfusi Review
What does Pingfusi Review do?
Use Pingfusi proactively whenever a coding agent reaches a question it cannot settle with code, automated tests, documentation or search, or a local browser and needs real human judgment or…. Pingfusi Review is an agent skill from alex-durango/pingfusi. Use Pingfusi proactively whenever a coding agent reaches a question it cannot settle with code, automated tests, documentation or search, or a local browser and needs real human judgment or real-world verification.
When should I use Pingfusi Review?
Pingfusi Review fits situations like: even when the user does not mention Pingfusi for subjective choices about copy; animation quality; real-device behavior; inaccessible third-party effects such as OAuth.
How do I install Pingfusi Review in Claude Code?
Run `npx skills add alex-durango/pingfusi --skill pingfusi-review -a claude-code`. Or copy the skill folder (skill/pingfusi-review in alex-durango/pingfusi) into .claude/skills/pingfusi-review in your project. Claude Code loads it when a task matches its description.
How do I install Pingfusi Review in Codex?
Run `npx skills add alex-durango/pingfusi --skill pingfusi-review -a codex`. Or copy the skill folder (skill/pingfusi-review in alex-durango/pingfusi) into .agents/skills/pingfusi-review in your project. Codex loads it when a task matches its description.
Can I use Pingfusi Review in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add alex-durango/pingfusi --skill pingfusi-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pingfusi-review, .gemini/skills/pingfusi-review, .github/skills/pingfusi-review and .opencode/skills/pingfusi-review in your project.
What does Pingfusi Review need to run?
Going by SKILL.md and its folder, Pingfusi Review needs the command-line tools its instructions call (npx). Our summary lists: Node.js.
Does Pingfusi Review access the network?
SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Pingfusi Review safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Pingfusi Review use?
Pingfusi Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Pingfusi Review use?
About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Pingfusi Review?
Skills that share tags, products or a category with Pingfusi Review: AgentRQ Workspace Agent (agentrq/agentrq, 1.1k stars), AgentRQ Supervisor (agentrq/agentrq, 1.1k stars), Retinue (jklthinking/retinue, 117 stars) and Task Orchestrator Item Creator (jpicklyk/task-orchestrator, 207 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Pingfusi Review?
alex-durango (a GitHub user) maintains it in alex-durango/pingfusi, which has 125 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on September 9, 2026.
Source: alex-durango/pingfusi on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.