agentsclimarketplace

Humrel rebuttal

Skill brycewang-stanford/Awesome-Journal-Skills/Human-Relations-Skills/skills/humrel-rebuttal

Use when drafting the response to a Human Relations (HR) R&R after the manuscript has been revised — structuring the response letter and handling reviewer/editor comments in HR's developmental, theory-first culture. Drafts the response; it does not perform the underlying revisions (do those first).From its SKILL.md

Install
npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill humrel-rebuttal

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

5.0 KB, ~1.1k tokens by cl100k_base, as published. Nobody here has run it

R&R Rebuttal (humrel-rebuttal)

When to trigger

  • You have an HR R&R and have already revised the manuscript
  • You need to structure a point-by-point response document
  • Reviewers disagree and you must navigate between them without contradicting yourself
  • The editor's letter asks you to "deepen the theoretical contribution" and you must answer with substance

Revise the paper first. The response letter documents changes you made; it is not a substitute for making them. If you have not revised yet, return to the relevant humrel-* skill.

Mindset for an HR revision

HR review is developmental and theory-first. Reviewers and the handling editor (under Co-Editors-in-Chief Smriti Anand and Penny Dick, 检索于 2026-06;以官网为准) took the idea seriously; the winning posture is gracious, responsive, and intellectually serious. The central question they will ask is "did the theoretical contribution mature?" — consistent with HR's gate of a "unique and substantive theoretical contribution." A letter that reads as a checklist of mechanical robustness additions — adequate at some quantitative-leaning venues — will underperform here if the theoretical insight and the social-relational argument have not sharpened.

Structure of the response

  1. Cover note to the editors. Thank the team; summarize the 3–5 most important changes and how the contribution is now sharper. Address the editors' central theoretical ask explicitly and up front.
  2. Point-by-point responses, grouped by reviewer, then by comment. For each:
    • Quote the comment verbatim (or faithfully paraphrase).
    • State your response: Accepted / Partially accepted / Respectfully disagree.
    • Describe the exact change and cite the new location (page, section, table).
    • Where you disagree, give the reasoned case with evidence, and offer a compromise where possible.
  3. A summary of major changes at the top helps editors tracking a multi-round file.

Handling hard cases

  • "Deepen the contribution": the most common HR ask. Show concretely how the theory is now sharper, the mechanism more specified, the social-relational stakes clearer — not just more tables or more cases.
  • Reviewers disagree: state both positions, explain your resolution, and let the editor see you reasoned it through. Do not silently side with one and ignore the other.
  • A request would harm the paper: explain why (theoretical or evidentiary cost), propose an alternative that meets the underlying concern, and defer to the editors.
  • "It reads like a sibling-journal paper": answer by re-foregrounding the relational/theoretical contribution that makes it HR, not by adding managerial implications.
  • Out-of-scope requests: politely note scope and, if useful, flag as future work.

Tone, craft, and compliance

  • Respectful, specific, and confident — never defensive or dismissive ("the reviewer misunderstood").
  • Make the editors' job easy: clear navigation, change locations, a quotable summary.
  • Keep the letter self-contained; a reviewer should not need the tracked-changes file to follow it.
  • Ensure consistency: a change for Reviewer 1 must not contradict a response to Reviewer 2.
  • Keep the revised manuscript anonymized (double-anonymous), within the 13k word cap, and re-declare any AI use in the cover letter if applicable.

Checklist

  • Manuscript revised before writing the letter
  • Editors' central theoretical ask addressed first and explicitly
  • Every comment answered; none skipped or merged away
  • Each response states accept/partial/disagree + the exact change location
  • "Deepen the contribution" answered with theoretical substance, not just additions
  • Reviewer conflicts navigated without internal contradictions
  • Revised file still anonymized, within 13k, AI re-declared if used
  • Tone gracious and serious throughout; letter is self-contained

Anti-patterns

  • Writing the response before actually revising
  • Defensive or dismissive replies
  • Claiming a change was made without pointing to where
  • Answering "deepen the contribution" with cosmetic additions or extra robustness
  • Satisfying one reviewer in a way that contradicts another's response
  • Re-introducing author-identifying traces or busting the word cap during revision

Output format

【Journal】Human Relations
【Skill】humrel-rebuttal
【Round】1st / 2nd / later
【Editors' core ask addressed】how + where
【Comments handled】N / N (none skipped)
【Disagreements】[...] + evidence/compromise
【Contribution deepened】how the theory matured
【Compliance】anonymized, ≤13k, AI re-declared (yes/no)
【Next step】resubmit via ScholarOne

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.