[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MAZ2N3M2GZ984YP0DEY3H8":3,"skill-same:01M6MAZ2N3M2GZ984YP0DEY3H8":91},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":31,"publishedAt":55,"linkOnly":56,"markdownContent":57,"markdownBody":58,"frontMatter":59,"refName":67,"commitSha":68,"skillDirectory":69,"forksCount":70,"repositoryHtmlUrl":71,"repositoryHomepageUrl":72,"ownerHtmlUrl":73,"ownerBlogUrl":74,"ownerDescription":75,"updatedAt":76,"install":77,"resources":90},"01M6MAZ2N3M2GZ984YP0DEY3H8","rebuttal-and-response-to-reviewers",null,"Plan and write responses to peer review, including journal \"response to reviewers\" letters for revise-and-resubmit, conference rebuttals under strict length limits (OpenReview\u002FICLR, NeurIPS, ICML, ACL ARR, CVPR), author responses to meta-reviews, and appeals. Use when a user receives reviews, must triage reviewer comments, draft point-by-point replies, decide what new experiments to run, disagree respectfully with a reviewer, or track manuscript changes for a revision. For authors answering reviews of their own manuscript; to write a review of someone else's paper, use peer-review instead.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Frebuttal-and-response-to-reviewers\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54],"rebuttal and response to reviewers","rebuttal","runtime","new","when","limits","track","for","manuscript","reviews","revision","journal","revise","writing","write","decide","reviewer","plan","peer review","Meta","run","experiments","review","2026-11-10 10:12:30",false,"---\nname: rebuttal-and-response-to-reviewers\ndescription: Plan and write responses to peer review, including journal \"response to reviewers\" letters for revise-and-resubmit, conference rebuttals under strict length limits (OpenReview\u002FICLR, NeurIPS, ICML, ACL ARR, CVPR), author responses to meta-reviews, and appeals. Use when a user receives reviews, must triage reviewer comments, draft point-by-point replies, decide what new experiments to run, disagree respectfully with a reviewer, or track manuscript changes for a revision. For authors answering reviews of their own manuscript; to write a review of someone else's paper, use peer-review instead.\nlicense: MIT\ncompatibility: No runtime dependencies.\nmetadata:\n  version: \"1.0\"\n  category: research-writing\n  maintainer: Kalaris Labs\n  author: Kalaris Labs (Sayan Chowdhury)\n  tags: peer review, rebuttal, response to reviewers, revise and resubmit, OpenReview, author response\n---\n\n# Responding to Reviewers\n\nThe audience of a response is the **editor or area chair**, who must decide\nquickly whether concerns were addressed. Make every reply easy to verify:\nquote the concern, answer it directly, show the change with a location.\n\n## Step 1: Triage (before writing anything)\n\nSplit every review into atomic comments and classify each in a table:\n\n| ID | Reviewer | Comment (short) | Type | Effort | Plan |\n|---|---|---|---|---|---|\n| R1.1 | 1 | Missing baseline X | Experiment | High | Run X on 2 datasets |\n| R2.3 | 2 | Claim in §4 overstated | Wording | Low | Soften + add limitation |\n\nTypes: *misunderstanding* (the text was unclear), *missing analysis\u002Fexperiment*,\n*wording\u002Fpresentation*, *disagreement on substance*, *out of scope*, *factual error by reviewer*.\n\nThen:\n- Identify the **2-3 concerns that drive the scores** (often shared across reviewers). These get\n  the most effort and appear first in a conference rebuttal.\n- Decide what is feasible in the revision window. Never promise experiments you will not run.\n- Note conflicts between reviewers so the editor can adjudicate.\n\n## Step 2: Do the work, then write\n\nRun the experiments and edit the manuscript **before** drafting replies, so every reply can\npoint to a concrete change. Keep a change log with section\u002Fpage\u002Fline numbers.\n\n## Step 3: Reply patterns\n\n**Journal response letter** (no strict length):\n\n```text\nReviewer 1, Comment 1: \"\u003Cquote or faithful summary of the concern>\"\n\nResponse: We thank the reviewer for ... [direct answer in the first sentence].\nWe have [action]. The new results (Table 3, p. 7, lines 210-224) show ...\n\nChange in manuscript: \"\u003Cquoted new\u002Frevised text>\" (Section 4.2, p. 7)\n```\n\nBest practices:\n- Answer in the first sentence (\"Yes, we have added...\", \"We agree and have...\", \"We respectfully disagree because...\").\n- Thanks once per reviewer, not before every comment.\n- Quote revised text so the reviewer need not hunt for it. Provide a tracked-changes\u002Fdiff version if the journal allows.\n- Number comments (R1.1, R1.2 ...) and cross-reference instead of repeating (\"see our response to R2.1\").\n\n**Disagreeing** (it is allowed and expected when justified):\n1. Acknowledge the underlying concern (\"We understand the concern that ...\").\n2. Give evidence: data, citations, a small additional analysis, or a precise explanation.\n3. Make a concession where honest: a clarification in the text or a stated limitation.\nNever be sarcastic, never say the reviewer \"failed to understand\". Rewrite the text so the next reader won't.\n\n**Conference rebuttal** (hard limits: characters\u002Fwords per reviewer or one page; check the venue):\n- Lead with a short **general response** covering shared concerns and new results.\n- Then per reviewer, only the comments that affect the decision, 2-5 sentences each.\n- Put new numbers in compact tables. State exactly what will change in the camera-ready.\n- Correct factual misreadings politely with pointers (\"Section 3.2, Eq. 4 defines ...\").\n- Respect the venue's rules on new experiments, links and supplementary material.\n  Many prohibit external links or new PDFs during rebuttal.\n- On OpenReview discussions: reply promptly and concisely, and summarize the resolved points for the AC near the end.\n\n## Step 4: Cover note to the editor (journals)\n\nSummarize the main changes in 3-6 bullets, flag any reviewer disagreements you could not\nresolve and why, and confirm all co-authors approved the revision.\n\n## Quality checklist\n\n- Every comment has a response. Count them against the triage table.\n- Every \"we have added\u002Fchanged\" is actually in the manuscript at the cited location.\n- New numbers match between response, manuscript, tables and abstract.\n- Tone: professional, specific, never defensive. Read it as the reviewer would.\n- No new claims beyond what the revised evidence supports.\n- Length within the venue limit (count it).\n\n## Related skills\n\n`peer-review` (reviewing others' work: useful to anticipate criticism), `scientific-writing`,\n`ml-paper-writing`, `scientific-critical-thinking`, `statistical-analysis`.\n","# Responding to Reviewers\n\nThe audience of a response is the **editor or area chair**, who must decide\nquickly whether concerns were addressed. Make every reply easy to verify:\nquote the concern, answer it directly, show the change with a location.\n\n## Step 1: Triage (before writing anything)\n\nSplit every review into atomic comments and classify each in a table:\n\n| ID | Reviewer | Comment (short) | Type | Effort | Plan |\n|---|---|---|---|---|---|\n| R1.1 | 1 | Missing baseline X | Experiment | High | Run X on 2 datasets |\n| R2.3 | 2 | Claim in §4 overstated | Wording | Low | Soften + add limitation |\n\nTypes: *misunderstanding* (the text was unclear), *missing analysis\u002Fexperiment*,\n*wording\u002Fpresentation*, *disagreement on substance*, *out of scope*, *factual error by reviewer*.\n\nThen:\n- Identify the **2-3 concerns that drive the scores** (often shared across reviewers). These get\n  the most effort and appear first in a conference rebuttal.\n- Decide what is feasible in the revision window. Never promise experiments you will not run.\n- Note conflicts between reviewers so the editor can adjudicate.\n\n## Step 2: Do the work, then write\n\nRun the experiments and edit the manuscript **before** drafting replies, so every reply can\npoint to a concrete change. Keep a change log with section\u002Fpage\u002Fline numbers.\n\n## Step 3: Reply patterns\n\n**Journal response letter** (no strict length):\n\n```text\nReviewer 1, Comment 1: \"\u003Cquote or faithful summary of the concern>\"\n\nResponse: We thank the reviewer for ... [direct answer in the first sentence].\nWe have [action]. The new results (Table 3, p. 7, lines 210-224) show ...\n\nChange in manuscript: \"\u003Cquoted new\u002Frevised text>\" (Section 4.2, p. 7)\n```\n\nBest practices:\n- Answer in the first sentence (\"Yes, we have added...\", \"We agree and have...\", \"We respectfully disagree because...\").\n- Thanks once per reviewer, not before every comment.\n- Quote revised text so the reviewer need not hunt for it. Provide a tracked-changes\u002Fdiff version if the journal allows.\n- Number comments (R1.1, R1.2 ...) and cross-reference instead of repeating (\"see our response to R2.1\").\n\n**Disagreeing** (it is allowed and expected when justified):\n1. Acknowledge the underlying concern (\"We understand the concern that ...\").\n2. Give evidence: data, citations, a small additional analysis, or a precise explanation.\n3. Make a concession where honest: a clarification in the text or a stated limitation.\nNever be sarcastic, never say the reviewer \"failed to understand\". Rewrite the text so the next reader won't.\n\n**Conference rebuttal** (hard limits: characters\u002Fwords per reviewer or one page; check the venue):\n- Lead with a short **general response** covering shared concerns and new results.\n- Then per reviewer, only the comments that affect the decision, 2-5 sentences each.\n- Put new numbers in compact tables. State exactly what will change in the camera-ready.\n- Correct factual misreadings politely with pointers (\"Section 3.2, Eq. 4 defines ...\").\n- Respect the venue's rules on new experiments, links and supplementary material.\n  Many prohibit external links or new PDFs during rebuttal.\n- On OpenReview discussions: reply promptly and concisely, and summarize the resolved points for the AC near the end.\n\n## Step 4: Cover note to the editor (journals)\n\nSummarize the main changes in 3-6 bullets, flag any reviewer disagreements you could not\nresolve and why, and confirm all co-authors approved the revision.\n\n## Quality checklist\n\n- Every comment has a response. Count them against the triage table.\n- Every \"we have added\u002Fchanged\" is actually in the manuscript at the cited location.\n- New numbers match between response, manuscript, tables and abstract.\n- Tone: professional, specific, never defensive. Read it as the reviewer would.\n- No new claims beyond what the revised evidence supports.\n- Length within the venue limit (count it).\n\n## Related skills\n\n`peer-review` (reviewing others' work: useful to anticipate criticism), `scientific-writing`,\n`ml-paper-writing`, `scientific-critical-thinking`, `statistical-analysis`.\n",{"name":5,"license":15,"metadata":60,"description":7,"compatibility":66},{"tags":61,"author":62,"version":63,"category":64,"maintainer":65},"peer review, rebuttal, response to reviewers, revise and resubmit, OpenReview, author response","Kalaris Labs (Sayan Chowdhury)","1.0","research-writing","Kalaris Labs","No runtime dependencies.","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Frebuttal-and-response-to-reviewers",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":78,"prompt":88,"zipAvailable":89},[79,82,85],{"tool":80,"command":81},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill rebuttal-and-response-to-reviewers",{"tool":83,"command":84},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill rebuttal-and-response-to-reviewers",{"tool":86,"command":87},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill rebuttal-and-response-to-reviewers","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Frebuttal-and-response-to-reviewers\u002FSKILL.md",true,[],[92,101,109,117,125,133],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":96,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":100},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":100},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":100},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":121,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":100},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":129,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":100},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":137,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":100},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]