skill-1b-unified-concern-extraction

Extract atomic concerns from OpenReview reviews and verify PDF resolution status.

1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/jinming99/reviewer-under-review --skill skill-1b-unified-concern-extraction
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-1b-unified-concern-extraction
Source: https://github.com/jinming99/reviewer-under-review/tree/main/.claude/skills/skill-1b-unified-concern-extraction
Command: npx skills add https://github.com/jinming99/reviewer-under-review --skill skill-1b-unified-concern-extraction

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extracts a structured concern sheet from OpenReview reviews and a paper PDF, enabling per-concern resolution verification against the evaluated manuscript.

Core Features & Use Cases

  • Unified extraction of atomic concerns with per-concern resolution status
  • PDF cross-verification to confirm whether fixes appear in the revised manuscript
  • Outputs schema-compatible data for downstream evaluation pipelines (OfficialConcernSheet v1) and supports additional per-concern fields.

Quick Start

Analyze an OpenReview page and the target paper PDF to produce a unified concern sheet.

Frequently Asked Questions about skill-1b-unified-concern-extraction

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract and verify OpenReview concerns against a paper PDF?

The unified concern extraction process identifies atomic issues from reviews and cross-verifies them against the evaluated paper PDF to output a schema-compatible sheet with per-concern resolution statuses.

What is the process for cross-verifying if review concerns are addressed in a revised manuscript?

Cross-verifying review concerns involves checking the evaluated paper PDF to determine if fixes appear in the manuscript, annotating each atomic concern with addressed_in_pdf status and pdf_evidence.

How do I generate a structured schema output from official academic reviews?

Generating a structured schema output involves parsing official reviews to extract atomic concerns, mapping them into an OfficialConcernSheet v1 format with per-concern fields for downstream evaluation pipelines.

Can I track per-concern resolution status and decision drivers from OpenReview data?

You can track per-concern resolution status and decision drivers from OpenReview data by extracting atomic concerns and annotating acceptance decision drivers alongside PDF cross-verification metadata.

Does the unified concern extraction output support downstream evaluation pipelines?

The unified concern extraction output supports downstream evaluation pipelines by providing a schema-compatible OfficialConcernSheet v1, which includes structured fields like pdf_evidence and pdf_is_revised metadata.