respond-to-referees

What problem does it solve? Drafting a response-to-referees document during a revise-and-resubmit round is tedious and error-prone: every referee comment must be matched to a specific change in the revised manuscript, classified, and answered politely, and any fabricated page or line reference can get a paper desk-rejected. ## Core Features & Use Cases - Comment-to-Revision Mapping: Parses referee reports into discrete concerns and locates each one in the revised manuscript via grep-based search across .tex, .pdf, .docx, .html, and Markdown sources. - Coverage Classification: Labels every concern as Addressed, Partially addressed, Deferred, or Disagreement, and flags anything unaddressed for author input. - Verified Claims: Runs a mandatory post-flight verification step with a claim-verifier subagent to confirm every "we added X on page Y" statement actually exists in the manuscript. - Use Case: After receiving referee reports on a journal submission, point the Skill at the report and your revised manuscript to produce a complete response-to-referees.md with a per-referee reply section and an editor-friendly concern matrix. ## Quick Start Ask the assistant to generate a response-to-referees document from your referee report PDF and revised manuscript file, classifying each comment and verifying every cited revision location.