Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Orgsci Rebuttal

ASecurity

Use after an Organization Science R&R to plan the revision and draft the point-by-point response letter, following the journal's codified author-response norms — verbatim italic quoting of each comment, no duplicated responses across reviewers, and a non-combative, non-effusive tone, while prioritizing the autonomous senior editor's concerns.

1,052 stars
0 votes
0 copies
0 views
Added 6/6/2026
ai-agentsgo

Security Analysis

A100/100

Scanned 6/6/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill orgsci-rebuttal --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Orgsci Rebuttal?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Orgsci Rebuttal
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-orgsci-rebuttal/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-orgsci-rebuttal)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: orgsci-rebuttal
description: Use after an Organization Science R&R to plan the revision and draft the point-by-point response letter, following the journal's codified author-response norms — verbatim italic quoting of each comment, no duplicated responses across reviewers, and a non-combative, non-effusive tone, while prioritizing the autonomous senior editor's concerns.
---

# R&R Revision & Response Letter (orgsci-rebuttal)

## When to trigger

- You received a major/minor R&R and need to plan revisions and write the response
- Reviewers disagree with each other or with the senior editor
- You are unsure how to format the response letter for this venue

## Revise the manuscript before you write the letter

A response letter is only as good as the revision behind it. Re-derive the **overall contribution** the SE asked for (`orgsci-contribution-framing`), strengthen the **mechanism and design logic** where identification is impossible (`orgsci-methods` / `orgsci-data-analysis`), and update the exhibits. Then write the letter to a manuscript you have actually changed.

## Follow the journal's codified author-response norms

Organization Science's official length policy spells out **how to write the response**, and editors expect it:

- **Quote each editor/reviewer comment verbatim, in italics**, immediately above your response, so the reader sees exactly what you are answering.
- **Do not duplicate responses across reviewers.** When two reviewers raise the same point, answer it once and cross-reference, rather than pasting the same paragraph repeatedly.
- **Avoid a combative tone.** Engage disagreements with evidence and theory, not defensiveness; concede where the reviewer is right.
- **Avoid effusive flattery** of editors and reviewers — the policy's own framing is that "we are neither oracles nor infallible." Be respectful and substantive, not fawning.

## Prioritize by who decides

The **Senior Editor decides** autonomously (accept/reject/R&R), so the SE's synthesis sets your priorities. When a reviewer's request conflicts with the SE's direction or the paper's contribution, follow the SE's framing and explain courteously. Group changes so the SE sees the contribution is sharper, the mechanism better supported, and the level-of-analysis logic clean.

## Mechanics

- Map every comment to a concrete change (text, new analysis, appendix material) or a reasoned, evidence-backed rebuttal, with page/line pointers.
- Keep the revised manuscript and the standalone appendix anonymized; house new robustness/sensitivity work in the **separate appendix**, mindful of the ~50-page main-text norm.
- Resubmit within the stated window (reported ~1 year, **待核实** — confirm in your letter).

## Anti-patterns

- Drafting the letter before the manuscript is actually revised.
- Pasting the same answer under multiple reviewers (the policy bars duplication).
- Defensive or combative replies; or, the opposite, effusive flattery.
- Treating all reviewer demands as equal and ignoring the SE's prioritization.

## Output format

```
【Revision done first】contribution re-sharpened, mechanism/design strengthened, exhibits updated
【Response format】verbatim italic quotes, one answer per shared point, courteous & substantive
【SE priority】SE concerns addressed first; reviewer conflicts adjudicated to SE framing
【New work】appendix-housed analyses; anonymization preserved
【Window】resubmit within stated timeframe (~1 year 待核实)
【Next step】orgsci-submission (resubmit) → orgsci-review-process
```

Attribution

brycewang-stanfordbrycewang-stanford
View sourceMore from brycewang-stanford →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1066601 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693161 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

651 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →