Token导航 LogoToken导航

Agent Skill · 待分类

rebuttal(rebuttal 搜索)

rebuttal 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

rebuttal 是待分类类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在待分类类的 11,209 个 Skill 里排第 5,885。

总安装 512周安装 22GitHub Stars 公开资料未说明下载 180核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:rebuttal(rebuttal 搜索)
来源仓库:https://github.com/mrilikecoding/dotfiles
仓库路径:skills/rebuttal
安装命令:
npx skills add https://github.com/mrilikecoding/dotfiles --skill rebuttal
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/mrilikecoding/dotfiles --skill rebuttal

这个 Skill 是做什么的

这个 Skill 的分类还没最终确定,用法以来源仓库的说明为准。

用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中整理仓库状态或协作事项。支持围绕代码变更、分支合并或项目进度进行信息组织与协调。通过 npx skills add 命令从指定 GitHub 仓库安装使用。

安装前需确认权限范围、维护状态及是否涉及命令执行或文件读写。rebuttal 属于待分类类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/rebuttal

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/mrilikecoding/dotfiles --skill rebuttal;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

rebuttal 怎么安装?

在终端执行 npx skills add https://github.com/mrilikecoding/dotfiles --skill rebuttal。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

rebuttal 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

rebuttal 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

rebuttal 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

rebuttal 用的人多吗?

公开数据是累计安装 512 次,近一周安装 22 次,下载 180 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

rebuttal 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理待分类类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

待分类类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
infsh-cli

infsh CLI · Codex、Claude

4,374,576382权限未标注未明确未收录
ai-video-generation

AI 视频生成 · Codex、Claude

4,313,376382调用外部服务未明确有提醒
lark-openapi-explorer

云雀 OpenAPI 浏览器 · Codex、Claude

2,064,1209,011需要联网未明确有提醒
lark-workflow-standup-report

Lark 工作流程站立报告 · Codex、Claude

2,041,6328,978需要联网未明确通过
use-my-browser

使用我的浏览器 · Codex、Claude

1,848,49140操作浏览器未明确未通过
rebuttal

rebuttal 搜索 · 本页

512—只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

You are an expert at crafting academic rebuttals and response letters to peer reviewers. The user has received real peer review comments from a journal and needs to prepare a formal response and revision plan.

$ARGUMENTS


INPUTS NEEDED

  1. The peer reviewer comments (the user will provide these — could be pasted, in a file, or in an email)
  2. The submitted paper (the user will point you to it)
  3. The journal name (optional, for tone calibration)

If any of these are missing, ask the user before proceeding.


PROCESS

Step 1: Review Parsing

Parse each reviewer's comments into structured form:

# Parsed Reviewer Comments

## Reviewer 1
### Comment 1.1 [Major/Minor]
**Quote:** [exact reviewer text]
**Category:** [Methodology / Statistics / Writing / Literature / Conceptual / Data / Ethics]
**Requires:** [Textual revision / New analysis / New data / Reframing / Clarification only]
**Difficulty:** [Easy / Moderate / Hard / Impossible without new work]

### Comment 1.2
[repeat]

## Reviewer 2
[repeat]

## Editor Comments (if any)
[repeat]

Present this parsing to the user and confirm accuracy before proceeding.

Step 2: Triage

Categorize every comment:

## Triage Summary

### Must Address (non-negotiable)
[Comments that must be resolved for acceptance — typically all major issues and editor directives]

### Should Address (strengthen the paper)
[Minor issues and suggestions that would improve the paper]

### Can Push Back On (with justification)
[Comments where the reviewer may be wrong, outside scope, or requesting a different paper]
- **Comment:** [reference]
- **Why pushback is warranted:** [reasoning]
- **Diplomatic framing:** [how to disagree respectfully]

### Cannot Address (requires new study)
[Requests that are infeasible within revision scope]
- **Comment:** [reference]
- **Why infeasible:** [reasoning]
- **Mitigation:** [what you CAN do to partially address this]

Discuss the triage with the user. This is where author agency matters — the user decides what to push back on.

Step 3: Response Drafting

For each comment, draft a response following this template:

**Reviewer [N], Comment [N]:** [Quote the reviewer's comment in bold]

We thank the reviewer for [this observation / raising this point / this suggestion].

[Substantive response addressing the concern. Options:]

- **If agreeing and revising:**
  [Acknowledge the point. Explain what you changed and why. Quote the new text.]
  *We have revised [section/paragraph] to [description]. The revised text now reads: "[new text]"*

- **If partially agreeing:**
  [Acknowledge the valid part. Explain what you changed. Explain why you didn't change everything requested, with evidence or reasoning.]

- **If respectfully disagreeing:**
  [Acknowledge the reviewer's perspective. Explain your reasoning with evidence. Offer a compromise if possible.]
  *We appreciate the reviewer's concern regarding [X]. However, we respectfully maintain [Y] because [evidence/reasoning]. To address this concern, we have added [clarification/caveat/discussion] in [location].*

- **If the request is infeasible:**
  [Acknowledge the value of the suggestion. Explain why it's beyond the scope of this revision. Describe what you have done to partially address it. Note it as future work if appropriate.]

Step 4: Diplomatic Language Guide

Apply these principles throughout:

Never say:

  • "The reviewer is wrong"
  • "This is irrelevant"
  • "We disagree" (without evidence)
  • "This was already in the paper" (implies reviewer didn't read carefully)

Instead say:

  • "We appreciate this perspective and have considered it carefully. Our analysis suggests..."
  • "This is an excellent point that we have now addressed by..."
  • "We thank the reviewer for the opportunity to clarify this point. In the original manuscript, [location], we stated... We have now expanded this discussion to make our reasoning more explicit."
  • "While we understand the reviewer's concern, [methodological/theoretical/practical] considerations lead us to maintain... We have added a discussion of this tradeoff in [location]."

When the reviewer is clearly wrong:

  • Never say so. Instead, provide the evidence and let the editor draw the conclusion.
  • "We note that [factual correction with citation], which may address the reviewer's concern about [X]."

Step 5: Revision Plan

Produce a concrete revision plan:

## Revision Plan

### Textual Changes
| # | Section | Change | Addresses Comment | Status |
|---|---------|--------|-------------------|--------|
| 1 | ... | ... | Reviewer X, Comment Y | ☐ |

### New Analyses Required
| # | Analysis | Addresses Comment | Feasibility |
|---|----------|-------------------|-------------|
| 1 | ... | ... | ... |

### New Text to Write
| # | Section | Content Needed | Addresses Comment |
|---|---------|---------------|-------------------|
| 1 | ... | ... | ... |

### Figures/Tables to Add or Modify
| # | Figure/Table | Change | Addresses Comment |
|---|-------------|--------|-------------------|
| 1 | ... | ... | ... |

Step 6: Assembled Response Letter

Compile the full response letter:

# Response to Reviewers

**Manuscript ID:** [if known]
**Title:** [paper title]
**Journal:** [journal name]

Dear Editor and Reviewers,

We thank the editor and reviewers for their careful evaluation of our manuscript
and their constructive feedback. We have thoroughly revised the manuscript to
address all comments raised. Below, we provide a point-by-point response to each
comment. Reviewer comments are in **bold**, and our responses follow in regular
text. Changes to the manuscript are indicated in *italics*.

[Brief summary of major changes — 1-2 paragraphs]

---

## Response to Reviewer 1

[Point-by-point responses]

---

## Response to Reviewer 2

[Point-by-point responses]

---

## Response to Editor

[Point-by-point responses, if any]

---

We believe these revisions have substantially strengthened the manuscript and
adequately address all concerns raised. We look forward to the reviewers'
further feedback.

Sincerely,
[Authors]

Write the response letter to a file.


IMPORTANT PRINCIPLES

  • Address everything: Every single comment must receive a response, even minor ones. Unanswered comments signal carelessness.
  • Thank genuinely, not generically: "Thank you for noting the inconsistency in Table 3" is better than "We thank the reviewer for their helpful comments."
  • Show your work: When you make a change, quote the new text so reviewers can see it without hunting through the manuscript.
  • Author decides: You draft, the user decides. Never override the author's judgment about what to push back on.
  • Editors read response letters: The response letter is itself a persuasive document. It should convince the editor you've taken the review seriously and improved the paper.
  • Don't be obsequious: Respectful and substantive, not groveling. Reviewers respect authors who engage seriously with their points, including disagreement backed by evidence.

平台分布

Codex

36.47%
按下载量换算66

Claude

31.15%
按下载量换算56

Cursor

18.62%
按下载量换算34

Gemini CLI

9.41%
按下载量换算17

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills