rigor-worker

Validates that paper claims in LaTeX manuscripts match raw results.tsv data.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/Its-Atharva-Gupta/forge-researcher --skill rigor-worker-its-atharva-gupta
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rigor-worker
Source: https://github.com/Its-Atharva-Gupta/forge-researcher/tree/main/skills/rigor_worker
Command: npx skills add https://github.com/Its-Atharva-Gupta/forge-researcher --skill rigor-worker-its-atharva-gupta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Scientific manuscripts often contain claims that drift from the underlying experimental data, leading to hallucinated percentages, fabricated results, or unsupported conclusions. This Skill audits a LaTeX paper against its raw results file to catch such discrepancies before publication. ## Core Features & Use Cases - Claim-to-Data Auditing: Calls the audit_scientific_claims MCP tool to compare every claim in paper.tex against the raw results.tsv data. - Structured Validation Output: Writes a machine-readable validation summary to workspace/rigor_audit.json for downstream review. - Manuscript Rejection Loop: If the audit fails, it rejects the manuscript and instructs the write-worker to correct discrepancies. - Use Case: In an autonomous ML research pipeline, after a write-worker drafts a paper from experiment results, run this audit to verify no fabricated percentages or false claims slipped into the manuscript. ## Quick Start Audit the claims in workspace/paper.tex against workspace/results.tsv and write the validation summary to workspace/rigor_audit.json.

Frequently Asked Questions about rigor-worker

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

FAQPage Schema
How do I verify that paper claims match experimental results?▼

Run the audit_scientific_claims MCP tool with the paths to paper.tex and results.tsv. It compares each claim in the manuscript against the raw data and writes a validation summary to workspace/rigor_audit.json.

How to detect hallucinated results in AI-generated research papers?▼

Use a claim-level audit that cross-references the manuscript text against the raw results file. This Skill flags hallucinations, false claims, and fabricated percentages, then rejects the manuscript until the write-worker corrects the discrepancies.

What input files does the rigor audit require?▼

The audit requires two inputs: the path to workspace/paper.tex containing the drafted manuscript, and the path to workspace/results.tsv containing the raw experimental data. Both must exist before the audit tool is invoked.

What happens when the scientific rigor audit fails?▼

When the audit fails, the manuscript is rejected and the write-worker is instructed to correct the discrepancies. The validation details are recorded in workspace/rigor_audit.json so the issues can be traced and fixed.

Can the rigor audit run without the MCP audit tool?▼

No, the audit depends on the audit_scientific_claims MCP tool to perform the claim-to-data comparison. Without that tool available in the FastMCP gateway, the validation protocol cannot execute.