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

Jaar Revision And Response

ASecurity

Use when revising a Journal of the American Academy of Religion (JAAR) article after a revise-and-resubmit and writing the response to readers' reports. Reviewers come from different traditions and methods, so the response must satisfy each on its own terms while protecting the article's argument and its broad significance. Plans the revision and response; it does not fabricate sources.

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

Works with

cliapi

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill jaar-revision-and-response --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Jaar Revision And Response?

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

Security grade badge for Jaar Revision And Response
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-jaar-revision-and-response/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-jaar-revision-and-response)

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

Download with Pro
Files
SKILL.md
---
name: jaar-revision-and-response
description: Use when revising a Journal of the American Academy of Religion (JAAR) article after a revise-and-resubmit and writing the response to readers' reports. Reviewers come from different traditions and methods, so the response must satisfy each on its own terms while protecting the article's argument and its broad significance. Plans the revision and response; it does not fabricate sources.
---

# Revision & Response (jaar-revision-and-response)

A JAAR **R&R** is a genuine opening at a journal that rejects ~90%. But the readers may come from very
different corners of the study of religion (a textual scholar, a theorist, an ethnographer), and they
will ask for different things. The response letter must answer each report on its own terms while
keeping the **argument** and its **broad significance** intact — and the revision stays double-blind.

## When to trigger

- An R&R / revise decision arrived and you are planning the revision + response letter
- Readers' reports pull in different methodological directions
- A reader asks for engagement with a literature or source base that would reshape the article
- Writing the cover note to the editor

## Strategy

1. **Read the editor's letter as the rubric.** The editor distills which points are decisive; address
   those first. The editor — not any single reader — adjudicates.
2. **Point-by-point, every comment.** Quote or paraphrase each reader comment, then respond; do not skip
   any, even ones you decline.
3. **Concede or reply with reasons.** Where a reader is right, revise and say where (section/page);
   where you disagree, make the scholarly case (evidence, method, or framing) — a well-argued reply
   beats a capitulation that weakens the argument.
4. **Reconcile cross-method readers.** When a textual reader and a theorist want different emphases,
   choose a principled path that keeps the essay coherent **in its own method**, and explain the
   tradeoff to the editor rather than trying to be every kind of article at once.
5. **Protect broad significance.** Many R&Rs push toward more specialist detail; add it where it
   strengthens the argument, but do not let the article slide back into a subfield-only piece (the very
   thing JAAR screens against). Keep the field-level stakes front and center.
6. **Keep it submittable.** Maintain anonymity in the revised main document (third-person self-cites);
   keep in-text author-date citations; respect the word budget as notes grow.

## Response-letter format

For each reader comment:

```
> [Quoted / paraphrased reader comment]

Response: [What we revised / why we respectfully disagree, with the scholarly reason].
Change: [Section/page where the revision appears].
```

Open with a brief note to the editor summarizing the main changes and how the revision preserves the
article's broad significance; group by reader; end each entry with the change location.

## Anti-patterns

- Ignoring or quietly merging away a comment
- Capitulating to a request that erodes the argument or its field-level significance
- Over-specializing the revision until it no longer reads for the whole field
- Defensive or dismissive tone toward readers
- Letting anonymity or in-text citation style lapse in the revised file

## Output format

```
【Editor's decisive points】addressed first? [list]
【Coverage】every reader comment answered? [Y/N]
【Concede vs reply】each tagged with scholarly reason + change location
【Cross-method conflicts】reconciled and explained to editor? [Y/N]
【Broad significance protected】not narrowed to a subfield? [Y/N]
【Anonymity + in-text citations intact】[Y/N]
【Next】resubmit via Manuscript Central
```

## Supplementary resources

- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — review model and decision categories

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', ...

686011 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 →