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

Jacs Revision

ASecurity

Use after a decision letter/referee reports arrive for a Journal of the American Chemical Society (JACS) manuscript, to plan experiments and draft the point-by-point response. Structures the revision and rebuttal — it does not fabricate data or guarantee acceptance.

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

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Jacs Revision?

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

Security grade badge for Jacs Revision
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-jacs-revision/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-jacs-revision)

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

Download with Pro
Files
SKILL.md
---
name: jacs-revision
description: Use after a decision letter/referee reports arrive for a Journal of the American Chemical Society (JACS) manuscript, to plan experiments and draft the point-by-point response. Structures the revision and rebuttal — it does not fabricate data or guarantee acceptance.
---

# Revision and Response to Reviewers (jacs-revision)

## When to trigger

- A decision letter (major/minor revision, or reject-with-encouragement) arrived
- You need to triage referee comments into experiments vs edits vs rebuttals
- You are drafting the point-by-point response letter
- You must decide whether to appeal or to resubmit elsewhere

## Triage the reports first

Sort every numbered comment into one bucket:

| Bucket | Action |
|--------|--------|
| **Data-required** | A control, extra characterization, X-ray, kinetics, or scope substrate is genuinely needed → do the experiment |
| **Clarification** | A real point the text/figure can fix without new data → edit + point to the change |
| **Defensible disagreement** | Reviewer is mistaken or asks beyond scope → rebut politely with evidence |
| **Optional/over-reach** | Nice-to-have; address briefly or explain why out of scope |

Address the **rigor-critical** comments (purity, characterization, mechanism
support, reproducibility) first — these are the ones that block acceptance at JACS.

## Response-letter structure

1. **Opening** — thank the editor/reviewers; summarize the main changes and any new data/figures/SI added.
2. **Point by point** — quote each comment, then respond. For each: state the change, where it is in the revised manuscript/SI (section, figure, page), and the new evidence.
3. **Quote the new text** — paste added/changed passages so reviewers don't hunt.
4. **Rebuttals** — for disagreements, be respectful and evidence-based; concede where the reviewer improves the paper.
5. **Marked manuscript** — provide a tracked/colored version if requested.

## Doing the new chemistry well

- New experiments must meet the same rigor bar: full characterization, controls,
  CCDC deposition for any new structure, reproducible procedures (route to `jacs-methods`).
- New compounds → add full SI entries and spectra copies (route to `jacs-supplementary`).
- If a requested experiment fails or contradicts a claim, report it honestly and
  adjust the claim rather than hiding it.

## Tone

- Professional, specific, and complete; never dismissive even when disagreeing.
- Make the reviewer's job easy: cross-reference every change to a location.
- If a comment is based on a misreading, fix the text so the next reader can't misread it too.

## Checklist

- [ ] Every numbered comment has a response — none skipped
- [ ] Rigor-critical comments addressed with real data, not words
- [ ] New compounds/structures fully characterized and deposited (CCDC)
- [ ] Each response cites the exact location of the change
- [ ] Added/changed text quoted in the letter
- [ ] Disagreements rebutted with evidence and courtesy
- [ ] Claims softened or revised where new data require it
- [ ] Marked-up manuscript prepared if requested

## Anti-patterns

- Responding "we have addressed this" without saying where or how
- Adding new compounds without adding their SI characterization
- Arguing with a referee instead of fixing the ambiguous text
- Quietly dropping an inconvenient result instead of reporting it
- Over-claiming again in the revision after softening in round one
- Ignoring a rigor request and hoping the editor overrides the referee

## Output format

```
【Decision】major / minor / reject-with-encouragement
【Triage】data-required: [...]; clarify: [...]; rebut: [...]
【New experiments】done? characterized + deposited? Y/N
【Response letter】point-by-point complete? Y/N
【Claims adjusted】[...]
【Next】resubmit via Paragon Plus → await decision
```

## Related resources

- [`jacs-methods`](../jacs-methods/SKILL.md) — rigor bar for new experiments
- [`jacs-supplementary`](../jacs-supplementary/SKILL.md) — adding SI for new compounds
- [`jacs-referee-strategy`](../jacs-referee-strategy/SKILL.md) — anticipated objections to map onto the actual reports

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 →