ccf-rebuttal-writer — Claude Code skill: what it does, how to install
ccf-rebuttal-writer — a skill for automating review rebuttals and revision tracking in academic submissions. It generates response letters, resubmission plans, and revision ledgers while adhering to formatting standards.
MIT 2,200 installs ★ 3,769 updated 2026-10-20
npx skills add mikubaka88/CCFA-Skills --skill ccf-rebuttal-writer -a claude-codeWhat ccf-rebuttal-writer does
This tool manages post-review communication and revision accountability. It drafts rebuttals, tracks changes in a canonical revision-ledger.md, and adapts manuscripts for resubmission while preserving scientific integrity. The skill groups reviewer comments by issue type and severity to propose response strategies based on feasible changes.
What it helps with
- draft a rebuttal letter to reviewers
- track action items in a revision ledger
- create a resubmission plan for a new venue
- organize reviewer comments into issue groups
Example prompts for the agent
- Write a rebuttal for the current manuscript comments
- Create a revision ledger based on reviewer feedback
- Draft a response letter for a resubmission using TeX templates
How to install ccf-rebuttal-writer
1Skills CLI (Vercel)
npx skills add mikubaka88/CCFA-Skills --skill ccf-rebuttal-writer -a claude-code2Manually: put the files in place
~/.claude/skills/ccf-rebuttal-writer/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/ccf-rebuttal-writer/
1Skills CLI (Vercel)
npx skills add mikubaka88/CCFA-Skills --skill ccf-rebuttal-writer -a codex2Manually: put the files in place
.agents/skills/ccf-rebuttal-writer/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add mikubaka88/CCFA-Skills --skill ccf-rebuttal-writer -a cursor2Manually: put the files in place
.cursor/skills/ccf-rebuttal-writer/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install mikubaka88/CCFA-Skills ccf-rebuttal-writer2Manually: put the files in place
.github/skills/ccf-rebuttal-writer/SKILL.md1Skills CLI (Vercel)
npx skills add mikubaka88/CCFA-Skills --skill ccf-rebuttal-writer -a gemini-cli2Platform CLI
gemini skills install https://github.com/mikubaka88/CCFA-Skills --path ccf-rebuttal-writerManually: put the files in place
.devin/skills/ccf-rebuttal-writer/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add mikubaka88/CCFA-Skills --skill ccf-rebuttal-writer -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about ccf-rebuttal-writer
How to install ccf-rebuttal-writer in Claude Code?
Run the command npx skills add mikubaka88/CCFA-Skills --skill ccf-rebuttal-writer -a claude-code in your terminal.
What does ccf-rebuttal-writer do?
It automates the drafting of reviewer responses, maintains a revision ledger, and assists in adapting papers for resubmission to different venues.
What is required to run ccf-rebuttal-writer?
It requires existing project-specific collaboration rules and proper configuration of the ccfa-workfiles/ directory for artifact management.
Source text
SKILL.md · MIT
---
name: ccf-rebuttal-writer
description: "Write CCF rebuttals, author responses, revision ledgers, response letters, and resubmission plans. Use for 审稿意见回复, rebuttal, revision ledger, and 重投迁移. Ground promises in feasible changes and actual evidence. Ordinary manuscript writing has a separate owner."
metadata:
ccf_skill_controls:
handoff_question_mode: partial
respect_session_denylists: true
protect_idea_scope_in_writing: true
private_material_safety: moderate
shared_controls: ../ccf-common/references/
---
# CCF Rebuttal Writer
## Family File Contract
Before file work, reuse canonical paths and one task/artifact working directory; default to project-root `ccfa-workfiles/<purpose>/<artifact-id>/`. Update in place, preserve inputs, and use UTF-8 with Chinese-text checks. Apply [artifact-contracts.md](../ccf-common/references/artifact-contracts.md) for naming, ownership, and task-created cleanup; handoffs inherit these paths.
## Collaboration Contract
Before specialist execution, read and apply [ccf-humanization](../ccf-humanization/SKILL.md) first, then [ccf-common](../ccf-common/SKILL.md). At every handoff, reuse their applicable active rules or refresh missing/changed ones. Both preflights are required even without prose; detailed editing, experiment, and maintenance modes run only when relevant.
Integrate necessary specialist contributions under one owner; reuse valid prerequisites and verify affected results. Follow the [cooperation routes](../ccf-common/references/routing.md) without duplicate reports.
## Core Rule
Handle post-review communication and revision accountability. Answer the actual concern with evidence and promise only feasible, authorized changes. Preserve the research during resubmission and use existing authorization: requested citation repair or positioning revision includes the necessary verified bibliography updates; response drafting alone does not start new experiments or redesign the method. Follow the user's requested response format: plain text, TeX, reviewer-by-reviewer, issue-grouped, table-first, or short response.
## Modes
- `rebuttal`: reviewer/AC response under a word or time budget.
- `revision-ledger`: reviewer comment -> action -> manuscript location -> owner -> status.
- `response-letter`: revision summary or camera-ready response letter.
- `resubmission`: adapt an already written paper to a new venue while preserving its science and carrying out authorized revisions.
## Workflow
1. Identify venue, response format, word budget, deadline, review scores/confidence, and whether this is rebuttal, revision, or resubmission.
2. Parse comments into issue groups by reviewer, concern type, severity, available evidence, response strategy, and promised paper change.
3. Load `references/response-strategy.md` for substantial responses and apply `../ccf-paper-writer/references/prose-quality-guardrails.md`; answer actual high-impact concerns first: soundness, novelty, missing evidence, incorrect assumptions, and shared concerns.
4. Load `references/revision-ledger.md` whenever promised edits, manuscript locations, resubmission actions, review rounds, or cross-version score changes must be tracked. Update one canonical ledger in place; do not create a separate ledger per round unless the user requests snapshots.
5. For full rebuttals, load `references/tex-templates.md` and use the TeX templates in `assets/templates/` when useful.
6. For resubmission, map old reviewer concerns to the new venue's constraints through `ccf-submission-checker`. Resolve citation or evidence actions within the requested revision scope through their owners; identify a material research change before expanding that scope.
7. Complete necessary contributions through their owners: paper writer for requested revisions, experiment designer for authorized evidence work, and submission checker for applicable venue/package rules. Use integrity auditor for unresolved claim/result conflicts and reviewer for a consequential unanswered criticism. Integrate returned evidence and verify actual changes before claiming completion in the response; a planned experiment or promised edit remains planned.
## Adaptive Output Contract
Put the requested response artifact first. For "write rebuttal", output the rebuttal text or TeX first. For "make a ledger", output the ledger first. Use the full structure below for standard multi-reviewer response planning or when the user asks for strategy plus draft:
```text
Mode:
Venue and constraints:
Issue table:
Response strategy:
Draft response or response file:
Promised paper changes:
Revision ledger:
Resubmission adaptation notes:
Claims/promises to avoid:
Next CCFA owner:
Checklist status:
```
## References
- `references/response-strategy.md`: response tactics.
- `references/response-checklists.md`: tone, evidence, promises, and word-budget checks.
- `../ccf-paper-writer/references/prose-quality-guardrails.md`: concise, non-defensive response prose and anti-pattern checks.
- `references/tex-templates.md`: reusable TeX response templates.
- `references/revision-ledger.md`: tracking reviewer comments and manuscript actions.
- `../ccf-paper-reviewer/references/version-comparison.md`: frozen scoring contract and issue provenance for cross-version review; rebuttal prose must not redefine that contract.
## Authorized Response Work
Follow `../ccf-common/references/handoff-modes.md` and `../ccf-common/references/task-modes.md`. A requested response plus revision authorizes both deliverables through their owners. Group duplicate comments while preserving reviewer attribution and answer coverage. Distinguish supplied results, planned experiments, promised revisions, and completed edits; verify an edit's location before claiming it was made. Preserve word budgets and respond to actual concerns without gratuitous apologies, imagined objections, or defensive repetition. A concise factual clarification is not a scientific concession. Reply drafting does not authorize posting or submission.
© mikubaka88 · MIT · mikubaka88/CCFA-Skills