Agent skill · Code Review & Quality

grounded-review

Review a research report draft with a structured scoring rubric, run a bounded repair loop when needed, and produce the final deliverable report.

Yiming Zhao438★ · 1 repos on radarProfile →
cursorships scriptsMIT
Install
npx skills add gaotiexinqu/OneResearchClaw --skill grounded-review --agent cursor

Same command for any agent — swap --agent for claude-code, codex, copilot.

Facts
Files in the skill folder: 7
SKILL.md size: 58 KB
Bundled scripts: yes
Path: .cursor/skills/grounded-review/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 438
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

Review
written from the skill's own SKILL.md · Aug 5, 2026

What it does

The skill performs the quality-gating and repair stage of the middle layer. It reads the grounded note, the literature result, the report draft, and optional supporting research artifacts, then outputs a review diagnosis and score report, a review state file, and a final deliverable research report. It acts as a gate between grounded-summary and the final rendering stage, not as a broad search or rendering tool.

How it works

  • It uses the inputs grounded.md, lit.md, summary.md (and optional artifacts) as sources of truth for evidence, scope, uncertainty, and technical detail recovery.
  • It produces: a review diagnosis and score report, a review state file, and a final deliverable research report.
  • The process follows a round-based archival structure: data/review_outputs/<ground_id>/round_<N>/ contains review_report.md and review_state.json for each round, with a final research_report.md in data/reports/<ground_id>/ after completion.
  • It preserves the core structure of the input draft, applies structured evaluation and bounded repair, performs re-checks, and finalizes the deliverable for downstream formatting/rendering steps.

When to use it

Use this skill when grounded.md, lit.md, and summary.md exist and you want a final deliverable research report for the current grounded item. Do not use when the report draft has not been written, the literature result is missing, or only a quick synthesis is required.

What it can touch

  • The skill reads: grounded.md, lit.md, summary.md, and optional supporting artifacts. It does not specify external editing beyond the bounded repair loop and structured evaluation.

Caveats

  • It is described as a quality-gate with bounded repair and should not perform unrestricted new literature search or radical direction changes.
  • The process uses a round-based archival system and finalizes the deliverable in data/reports/<ground_id>/research_report.md.
From the SKILL.md

# Grounded Review This skill performs the **quality-gating and repair stage** of the middle layer. It reads: 1. the grounded note, 2. the literature result, 3. the report draft, 4. optional supporting research artifacts, and produces: - a **review diagnosis and score report** - a **review state file** - a **final deliverable research report** This skill is **not** a broad search skill and **not**

More from OneResearchClaw
All skills →
About this skill
What does the grounded-review skill do?

Review a research report draft with a structured scoring rubric, run a bounded repair loop when needed, and produce the final deliverable report.

How do I install it?

Run `npx skills add gaotiexinqu/OneResearchClaw --skill grounded-review --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From gaotiexinqu/OneResearchClaw, a repository with 438 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going