[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6QFSBMYXYJ1ZRCPE0KS3W31":3,"skill-same:01M6QFSBMYXYJ1ZRCPE0KS3W31":87},{"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":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":64,"commitSha":65,"skillDirectory":66,"forksCount":14,"repositoryHtmlUrl":67,"repositoryHomepageUrl":68,"ownerHtmlUrl":69,"ownerBlogUrl":70,"ownerDescription":71,"updatedAt":72,"install":73,"resources":86},"01M6QFSBMYXYJ1ZRCPE0KS3W31","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.","Tashima-Tarsh\u002FDisha6.6","Tashima-Tarsh","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F269906498?v=4","01M6PBH98X03XERH0HFT4PFB1P","NITISH KUMAR","01M6PBH9DA0M6KM3Z12P848F0K",0,"MIT","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fkal-rebuttal-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],"rebuttal and response to reviewers","rebuttal","point","writing","limits","track","manuscript","reviews","revision","journal","revise","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":57,"description":7,"compatibility":63},{"tags":58,"author":59,"version":60,"category":61,"maintainer":62},"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","0da4485785ee599388900be50db1635489d53056",".agents\u002Fskills\u002Fkal-rebuttal-and-response-to-reviewers","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6","https:\u002F\u002Fdisha6.6.thenitishkr.in\u002F","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh","www.thenitishkr","thenitishkr | AI • Cyber-security • Research\r\n","2026-11-08 03:33:25",{"source":8,"skillName":5,"commands":74,"prompt":84,"zipAvailable":85},[75,78,81],{"tool":76,"command":77},"npx","npx skills add Tashima-Tarsh\u002FDisha6.6 --skill rebuttal-and-response-to-reviewers",{"tool":79,"command":80},"bunx","bunx skills add Tashima-Tarsh\u002FDisha6.6 --skill rebuttal-and-response-to-reviewers",{"tool":82,"command":83},"pnpm","pnpm dlx skills add Tashima-Tarsh\u002FDisha6.6 --skill rebuttal-and-response-to-reviewers","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fkal-rebuttal-and-response-to-reviewers\u002FSKILL.md",true,[],[88,118,141,168,192,216],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":97,"publishedAt":52},"01M6QRD07D4TGNDK6VJ4EHF8BV","youtube-full","Use when the user needs YouTube transcripts, video search, channel browsing, playlist extraction, or content monitoring. Trigger phrases: 'get the transcript for', 'search YouTube for', 'what are the latest videos on', 'list this playlist', 'monitor this channel', or any request involving a YouTube URL, video ID, or @handle. Do NOT use for downloading video or audio files, YouTube engagement data (likes, comments), or private\u002Fage-restricted videos.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fyoutube-full\u002FSKILL.md",[94],{"categoryNo":95,"categoryName":96,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",[98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117],"youtube full","youtube","full","transcript","search","monitoring","data","Video","Audio","list","files","do","get","age","trigger","URL","for","browsing","request","youtube transcripts",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":52},"01M6QRCJ3112VYPA97YG7KGMC2","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[125,126,127,128,102,129,130,46,131,132,133,134,43,135,136,137,138,139,140,114],"twitter","x twitter growth","growth","research","content","engineering","web search","competitors","analyze","engine","strategy","use","platform","grow","posting","competitive",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":150,"publishedAt":52},"01M6QRBN3EHQNJY42RERP7A149","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, build, or author a new skill.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrite-a-skill\u002FSKILL.md",[147],{"categoryNo":148,"categoryName":149,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[151,43,152,153,154,155,156,157,136,158,159,64,160,161,162,163,164,165,166,167],"write a skill","github","create","https","productivity","matt pocock","direct","example","build","new skill","structure","new agent","resources","with","tree","progressive disclosure","author",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":174,"publishedAt":52},"01M6QRB6G8P33PNGAF9Y69EJ9T","wrap-up","Close out a launched Claude Managed Agent — recap every primitive the founder now owns, regenerate the single-file overview page, and suggest the next 1-2 upgrades. Use when the user says \"wrap up\", \"close this out\", \"what do I own now\", \"give me the summary\", \"recap the agent\", or when the orchestrator routes phase=wrap-up. primitives_inventory.py tables everything owned (agent, environment, session, memory, outcome, deployment); overview_page.py regenerates a self-contained .\u002Fmy-agent\u002Fagent-overview.html; upgrade_suggester.py ranks the next moves from recorded deferrals plus standing hardening steps. Companion to run-without-you; the last stop before phase=done.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrap-up\u002FSKILL.md",[],[175,176,177,178,179,49,180,181,182,136,183,109,184,185,186,187,188,189,190,191],"wrap up","up","wrap","gemini","deployment","file","hardening","closeout","stop","upgrade","founder","close","companion","you","tables","directions","phase",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":196,"categories":197,"keywords":199,"publishedAt":52},"01M6QRA5AYC1RBFZ39GTWGS3N8","workflow-builder","Design and write deterministic multi-agent workflow scripts (.js files in .claude\u002Fworkflows\u002F) for Claude Code's Workflow tool. Use when a user wants to build, create, author, scaffold, or run a custom Claude Code workflow, orchestrate sub-agents (fan-out, pipeline, loop, judge-panel), or automate a repeatable multi-step task across fresh-context agents.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fworkflow-builder\u002FSKILL.md",[198],{"categoryNo":148,"categoryName":149,"taxonomyType":21,"taxonomyTypeDesc":22},[200,201,202,203,204,153,49,205,206,207,208,209,43,210,108,211,212,213,214,215],"workflow","workflow builder","builder","design","workflows","code","orchestrate","pipeline","loop","multi-agent","context","across","fresh","scripts","judge","claude code workflow",{"skillNo":217,"name":218,"nameZh":6,"description":219,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":220,"categories":221,"keywords":222,"publishedAt":52},"01M6QR7QMCZESKQA0ERW1E657M","weekly-review","Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says \"\u002Fcs:weekly-review\". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweekly-review\u002FSKILL.md",[],[51,223,224,225,226,227,228,229,230,208,231,232,233,234,235,236,110,237,238,191],"weekly review","weekly","deterministic scripts","reflect","feeds","inventory","open","team","projects","project-management","scanner","conversation","back","project","sprint","cadence"]