skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
vincenzoimp/academic-research-skills80 installs

adversarial-review

Use when reviewing the survey, a contribution, or a paper draft as a severe but fair reviewer — claim audit, methodology critique, and venue-reviewer simulation before submission.

How do I install this agent skill?

npx skills add https://github.com/vincenzoimp/academic-research-skills --skill adversarial-review
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The 'adversarial-review' skill is a set of instructions for providing critical feedback on academic papers, surveys, and contributions. It reads local files and writes review reports to a specified directory. No malicious behavior, network activity, or unauthorized code execution was detected.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

What does this agent skill do?

Adversarial Review

Find the objections that would block acceptance before external reviewers do. Review; never fix. Findings go to a report beside the artifact; the artifact itself is never edited by this skill.

Read First

  • the artifact under review: survey/survey.tex + PDF, or a contribution README + report, or a manuscript + framing.md + venue.md
  • references/review-lanes.md, references/claim-audit.md

Procedure

  1. Identify the target and the standard it must meet:
    • survey → coverage vs sota/index.md, grouping logic, fairness, and the quality of the gaps section
    • contribution → badge-checklist truthfulness, methodology (the develop-contribution methodology standard), claim–evidence match
    • paper → venue fit and reviewer simulation per venue.md, novelty, soundness, clarity
  2. Read claim-first: contributions/claims, then the evidence offered.
  3. Run the claim audit on every acceptance-critical claim per references/claim-audit.md: verify each against the cited synthesis, contribution output, or PDF.
  4. Review through every lane in references/review-lanes.md; keep lane findings separate until the final synthesis.
  5. Write the report to reviews/<YYYY-MM-DD>-<scope>.md beside the artifact (survey/reviews/, contributions/<slug>/reviews/, papers/<slug>/reviews/ — create the folder on demand) with: executive summary and recommendation; strengths with evidence; weaknesses grouped by severity; the claim-audit table; questions the authors must answer; a prioritized revision roadmap.

Criticism Standard

Every major criticism carries: exact claim or location, why it matters, evidence, what would fix or weaken it, severity (fatal / major / moderate / minor), and confidence. No performative harshness; no objection without evidence; polish never excuses methodological weakness.

Done When

  • The report exists with all sections, every fatal/major finding is evidence-backed, and no lane finding was dropped during synthesis — if a finding is wrong, the report says why

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/vincenzoimp/academic-research-skills/adversarial-review">View adversarial-review on skillZs</a>