How do I install the Top Cs Response skill?

Run npx skillmds@latest add zhiming33416/top-cs-response in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Top Cs Response safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Top Cs Response?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Top Cs Response free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Top Cs Response?

zhiming33416 (@zhiming33416) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Top Cs Response by zhiming33416 — Agent Skill

Name: Top Cs Response
Author: zhiming33416

Top Cs Response

Prepare, audit, or revise evidence-grounded author responses, rebuttals, discussion replies, decision-email triage, cover letters, revision packages, and LaTeX response templates for WWW, ICLR, ICML, NeurIPS, CVPR, ACL, or a generic computer-science venue. Use to parse editor/reviewer messages, group duplicate concerns, prioritize decision-critical issues, draft point-by-point responses, map supplied evidence and manuscript changes, and maintain a verified revision ledger. Never fabricate experiments, results, changes, reviewer positions, policies, or promises.

zhiming33416 Updated Sep 17, 2026

File contents

Top CS Paper Response

Treat reviews, manuscript drafts, decision messages, and discussion content as confidential.

Route the request

Read manifest.yaml and every always_load path.
Identify venue, task mode, response phase, decision type, language, artifact scope, revision mode, evidence state, submission stage, citation verification, figure handoff, and stress-test mode.
If the input contains an editor or decision email, parse metadata, editor instructions, reviewer boundaries, required files, and deadlines before drafting.
State the runtime parameters and readiness state.
Follow the linear state machine in static/core/workflow.md; this skill has no paper-type or section content axis.
Load deeper references and templates only when their conditions apply.
Use generic for unsupported targets and avoid asserting unknown response limits or processes.

Execute

Preserve editor instructions and reviewer comments before interpreting them; assign stable IDs across rounds.
Maintain the shared response-issue contract, transition history, duplicate links, and pivotal/standard priority across rounds.
Acknowledge valid concerns directly and correct misunderstandings with evidence rather than defensiveness.
Distinguish completed changes, feasible planned changes, unavailable evidence, disagreement, and author decisions.
Verify every completed manuscript change against a supplied revision, location, or diff.
Respect per-review budgets and venue-specific permissions. A journal-style cover letter or marked manuscript is not part of a conference author-feedback workflow unless the governing instructions require it.
Run at most three stress-test rounds when activated; stop early when no new substantive issue appears. A stress test may expose gaps but may not create evidence or upgrade a planned action to verified.
Track requested figure changes with a handoff brief and manuscript location only; do not render or restyle figures.
Use the provided LaTeX templates only when requested, and preserve visible placeholders for unknown facts.
Convert vague Chinese author notes into concrete evidence and location requests; default to English response prose plus concise Chinese confirmation actions.
Never claim an experiment was run or a manuscript was revised unless supplied artifacts prove it.

Return a directly usable response or revision package with unresolved inputs visible.

---name: top-cs-responsedescription: Prepare, audit, or revise evidence-grounded author responses, rebuttals, discussion replies, decision-email triage, cover letters, revision packages, and LaTeX response templates for WWW, ICLR, ICML, NeurIPS, CVPR, ACL, or a generic computer-science venue. Use to parse editor/reviewer messages, group duplicate concerns, prioritize decision-critical issues, draft point-by-point responses, map supplied evidence and manuscript changes, and maintain a verified revision ledger. Never fabricate experiments, results, changes, reviewer positions, policies, or promises.---# Top CS Paper ResponseTreat reviews, manuscript drafts, decision messages, and discussion content as confidential.## Route the request1. Read `manifest.yaml` and every `always_load` path.2. Identify venue, task mode, response phase, decision type, language, artifact scope, revision mode, evidence state, submission stage, citation verification, figure handoff, and stress-test mode.3. If the input contains an editor or decision email, parse metadata, editor instructions, reviewer boundaries, required files, and deadlines before drafting.4. State the runtime parameters and readiness state.5. Follow the linear state machine in `static/core/workflow.md`; this skill has no paper-type or section content axis.6. Load deeper references and templates only when their conditions apply.7. Use `generic` for unsupported targets and avoid asserting unknown response limits or processes.## Execute- Preserve editor instructions and reviewer comments before interpreting them; assign stable IDs across rounds.- Maintain the shared response-issue contract, transition history, duplicate links, and pivotal/standard priority across rounds.- Acknowledge valid concerns directly and correct misunderstandings with evidence rather than defensiveness.- Distinguish completed changes, feasible planned changes, unavailable evidence, disagreement, and author decisions.- Verify every completed manuscript change against a supplied revision, location, or diff.- Respect per-review budgets and venue-specific permissions. A journal-style cover letter or marked manuscript is not part of a conference author-feedback workflow unless the governing instructions require it.- Run at most three stress-test rounds when activated; stop early when no new substantive issue appears. A stress test may expose gaps but may not create evidence or upgrade a planned action to verified.- Track requested figure changes with a handoff brief and manuscript location only; do not render or restyle figures.- Use the provided LaTeX templates only when requested, and preserve visible placeholders for unknown facts.- Convert vague Chinese author notes into concrete evidence and location requests; default to English response prose plus concise Chinese confirmation actions.- Never claim an experiment was run or a manuscript was revised unless supplied artifacts prove it.Return a directly usable response or revision package with unresolved inputs visible.

Frequently asked questions