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

Ci Revision And Response

ASecurity

Use when revising a Critical Inquiry (CI) essay after a decision and writing the response to readers and editors. CI acceptance typically follows author revisions, and the editors-in-chief read closely, so the revision must strengthen the intervention and the response must address every point without diluting the argument. Structures the revision and response; it does not fabricate new readings or evidence.

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

Works with

api

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Ci Revision And Response?

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

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

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

Download with Pro
Files
SKILL.md
---
name: ci-revision-and-response
description: Use when revising a Critical Inquiry (CI) essay after a decision and writing the response to readers and editors. CI acceptance typically follows author revisions, and the editors-in-chief read closely, so the revision must strengthen the intervention and the response must address every point without diluting the argument. Structures the revision and response; it does not fabricate new readings or evidence.
---

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

A request to revise from *Critical Inquiry* is an encouraging signal — acceptance typically **follows
author revisions**, and the **editors-in-chief read closely**. The revision must make the intervention
sharper and the readings more earned; the response letter must address every point while **protecting
the argument** that drew the invitation in the first place.

## When to trigger

- A decision arrived asking for revisions before (re)consideration
- Readers' reports disagree and you must reconcile them
- A reader asks for a change that would blunt the central claim
- Writing the cover note to the editors summarizing the revision

## Strategy

1. **Read the editors' letter as the rubric.** The editors-in-chief signal which points are decisive;
   solve those first. They adjudicate disagreements among readers.
2. **One point-by-point response, every comment addressed.** Quote each comment, then respond — never
   skip one; silence reads as non-compliance.
3. **Concede or argue, explicitly and with reasons.** For each point: say what you changed and where
   (section/page/figure), or **disagree respectfully** on grounds of argument, object, or theory.
   Editors of a theory journal respect a well-argued disagreement over a hollow capitulation.
4. **Strengthen the intervention.** Use the revision to make the claim bolder and clearer and the
   readings deeper — resist changes that dilute the interdisciplinary stakes (see
   `ci-argument-and-intervention`).
5. **Reconcile conflicting readers openly.** When one reader wants the opposite of another, say so,
   choose a principled path, and explain the tradeoff to the editors.
6. **Keep the apparatus in order.** Hold the line on the **9,500-word** cap (notes count), keep
   **Chicago footnotes** clean, and confirm **image permissions** for any new figures (see
   `ci-citation-and-style`, `ci-submission`).

## Response-letter format

For each comment:

```
> [Quoted reader/editor comment]

Response: [What we did / why we respectfully disagree].
Change: [Section / page / figure number where the revision appears].
```

Open with a short **summary of the main changes** for the editors; group by reader; end each entry
with the location of every change so the editors can verify quickly.

## Anti-patterns

- Ignoring or quietly merging away a comment without a visible response
- Capitulating to a request that breaks the argument just to please a reader
- A defensive or dismissive tone toward readers
- "We thank the reader" with no actual change or argued reason
- Letting the revision spill past the word cap because notes were not counted
- Adding new figures without clearing permissions

## Output format

```
【Editors' decisive points】addressed first? [list]
【Coverage】every comment answered? [Y/N]
【Concede vs argue】each tagged with reason + change location
【Reader conflicts】reconciled and explained to editors? [Y/N]
【Intervention protected】no dilution of the claim/stakes? [Y/N]
【Apparatus】within cap, Chicago notes clean, new images cleared? [Y/N]
【Next】resubmit via Editorial Manager
```

## Supplementary resources

- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — review model and revision expectations
- [`../../resources/external_tools.md`](../../resources/external_tools.md) — word-count rule, Chicago tooling, image specs

Attribution

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

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

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

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

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 →