Loading...
Loading...
Found 7 Skills
Plan and write strategic rebuttals after real paper reviews arrive. Use this skill whenever the user has OpenReview reviews, reviewer comments, scores, confidence ratings, meta-reviews, author response windows, or wants to decide which experiments to run, infer reviewer intent, draft point-by-point responses, prepare follow-up discussion replies, or improve wording after reviews for ML/AI venues such as NeurIPS, ICML, ICLR, CVPR, ACL, EMNLP, or similar conferences.
Drafts peer-review rebuttals and author responses in the three real venue formats - (a) strict one-page LaTeX rebuttal PDFs (CVPR-style), (b) OpenReview threaded per-review replies under 10,000-character budgets (NeurIPS/ICML/ICLR), and (c) revise-and-resubmit packages with a change-log response document (CHI, SIGMOD/ICDE revision rounds, journals). Anchors every response to paper sections, tables, figures, and line numbers; enforces character/page budgets and point-by-point coverage with bundled checker scripts; ships a one-page rebuttal LaTeX template. Use when the user says "write my rebuttal", "respond to reviewers", "author response", "reviews came back", "reviewer 2 says", "revise and resubmit", "response letter", "rebuttal deadline", or needs to fit a response into an OpenReview character limit or a one-page PDF. Drafts files on disk only; never posts, uploads, or submits.
Step-by-step camera-ready prep for accepted papers — the error-prone final stage before publication. Use when a researcher says "camera-ready", "final version", or "my paper got accepted, now what", or mentions ACM eRights / rights form / TAPS / ORCID / DOI block, IEEE PDF eXpress / conference ID / eCF copyright form / Xplore, OpenReview final upload, de-anonymization, or extra camera-ready pages. Resolves the venue's rail from a machine-readable profile and walks it end to end across ACM eRights, ORCID, rights/DOI block, TAPS source upload, IEEE PDF eXpress, conference IDs, file naming, eCF exact-title match, registration/no-show, NeurIPS-style [final] recompile, and OpenReview upload. Generates an ordered checklist with deadlines and +page rules, and lints the final .tex for leftover anonymization and missing rights blocks via bundled stdlib-only scripts. Advisory — it prepares, explains, and lints, but never completes a form or submits anything.
Monitor arXiv, OpenReview, conference feeds, labs, projects, and competitor papers for new work that may overlap with a user's idea. Use for arxiv-watch, novelty-check, trend-scouting, competitor-tracking, paper tracking, 竞品监控, 新论文追踪, 论文跟踪, 类似 idea 监控. Link findings to ccf-literature-searcher, ccf-idea-reviewer, ccf-idea-optimizer, ccf-paper-writer, and ccf-integrity-auditor.
Builds a backwards submission timeline from a conference deadline - days remaining (AoE-aware), abstract-registration offsets, author-list freeze, OpenReview/CMT/EasyChair/HotCRP/PCS account lead times and per-system steps, supplementary-material and code size limits, reciprocal-reviewing duties, and a dual-submission audit. Use when the user wants to plan a submission, asks how long until a deadline, mentions abstract registration, submission checklist, deadline countdown, "what do I need before the NeurIPS/ICML/CHI deadline", or asks what happens after submitting (rebuttal window, notification, camera-ready). Phase-aware - produces pre-submission, under-review, and camera-ready plans from venues/ profiles and flags overdue steps.
Turns raw peer reviews into a prioritized triage matrix before any rebuttal is written. Use it when reviews come back from OpenReview, EasyChair, CMT, or HotCRP and the researcher says "my reviews are in", "triage these reviews", "how do I respond to Reviewer 2", "plan my rebuttal", or pastes raw review text with ratings and confidence scores. Splits each review into individual concerns; classifies every concern as misunderstanding vs real flaw vs requested experiment (plus clarification and disagreement); scores severity x response effort; and produces a prioritized response strategy with per-review character or word budgets matched to the venue's rebuttal format (10k-char OpenReview threads, CVPR one-page PDF, journal revise-and-resubmit). Deterministic parsing and matrix rendering run in bundled stdlib Python scripts. Hands off to write-rebuttal for drafting; treats review text as confidential and never submits anything.
Workflow 4: Submission rebuttal pipeline. Parses external reviews, enforces coverage and grounding, drafts a safe text-only rebuttal under venue limits, and manages follow-up rounds. Use when user says "rebuttal", "reply to reviewers", "ICML rebuttal", "OpenReview response", or wants to answer external reviews safely.