Individual skill
ccf-rebuttal-writer
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.
ccf-rebuttal-writer/SKILL.md
Source commit 91ca9e2801698466f934b557a75ce46db8ba46b5
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 3,494
- Repository last updated
- Oct 31, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- writing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 6,068 bytesagents/openai.yamlasset · 481 bytesassets/templates/ac-focused-response.texasset · 2,116 bytesassets/templates/compact-response.texasset · 1,559 bytesassets/templates/default-general-common-reviewer.texasset · 4,103 bytesassets/templates/reviewer-specific-response.texasset · 2,070 bytesreferences/response-checklists.mddoc · 6,115 bytesreferences/response-strategy.mddoc · 9,150 bytesreferences/revision-ledger.mddoc · 3,019 bytesreferences/tex-templates.mddoc · 2,446 bytes
Read excerpt
# 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