SkillAgentSearch skills...

rebuttal-guidance

Provides actionable peer-review rebuttal guidance (not full rebuttal prose) using conditional persuasion P(Z|X,Y): match reviewer mindset X, recommend strategy Y, optionally ground in manuscript evidence and similar successful historical (review, rebuttal) pairs

Install / Use

npx skills add HKUSTDial/Supervisor-Skills --skill rebuttal-guidance

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

88/100

Supported Platforms

Universal

Our assessment of rebuttal-guidance

rebuttal-guidance scores 88/100 on our quality scale, 1819th of 4,700 Development & Engineering skills we index (top 39%).

Its SKILL.md is 5.2 KB long, well organised into 14 sections with 1 code example: a solid amount of guidance for an agent.

With 7,505 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
17/20
Description
15/15
Adoption
16/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so rebuttal-guidance is actively maintained.
  • Our last check on 2026-10-31 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-28. Automated pattern scan on 2026-09-28. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

rebuttal-guidance compared with similar skills

All 4 of these similar skills score higher than rebuttal-guidance; compare them before choosing.

SkillScoreStarsUpdatedFormat
rebuttal-guidance (this skill)by HKUSTDial887.5k2mo agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md
lobehubby lobehub10085.6ktodayMCP Server

Frequently asked questions

How do I install rebuttal-guidance?
Run npx skills add HKUSTDial/Supervisor-Skills --skill rebuttal-guidance. The install tabs above show the steps for each supported agent.
Which AI agents does rebuttal-guidance work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is rebuttal-guidance safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is rebuttal-guidance still maintained?
The repository was last updated about 2 months ago, so rebuttal-guidance is actively maintained.

name: rebuttal-guidance description: >- Provides actionable peer-review rebuttal guidance (not full rebuttal prose) using conditional persuasion P(Z|X,Y): match reviewer mindset X, recommend strategy Y, optionally ground in manuscript evidence and similar successful historical (review, rebuttal) pairs. Use when the user pastes reviewer comments, asks for rebuttal help, rebuttal guidance, response to reviewers, how to reply to R1.W2, OpenReview rebuttal, or the reviewer ignored the rebuttal.

Rebuttal Guidance

Overview

This skill delivers executable rebuttal guidance per concern: structured plans, evidence pointers, tone and strategy priorities. It does not produce ready-to-paste rebuttal prose; the author writes the final text.

The core model is conditional persuasion P(Z=1 | X, Y):

  • X: reviewer mindset (behavior cluster inferred from review text)
  • Y: rebuttal strategy vector (which tactics to emphasize)
  • Z: success (score increase or paper accepted)

When to use

  • User pastes Weaknesses / Questions from ICLR, NeurIPS, ICML, EMNLP, etc.
  • User asks how to respond to a specific reviewer comment.
  • User wants a structured plan before writing rebuttal prose.
  • User asks which tone or evidence strategy fits a harsh vs. open reviewer.
  • User says "reviewer ignored my rebuttal" and wants to recalibrate.

When NOT to use

  • User wants full rebuttal text copied verbatim → output guidance first; warn against blind LLM paste.
  • User asks to evaluate a research idea → use idea-evaluator.
  • User asks for pre-submission paper review → use pre-submission-reviewer.
  • No review text provided → ask for it first.

Core procedure

Step 1: Inventory concerns

Extract every numbered Weakness and Question from the pasted review. If the user pasted only one reviewer's block, ask whether other reviewers exist.

Output a short table:

| ID | Type | One-line summary | |----|------|-----------------| | R1.W1 | W | ... | | R1.Q1 | Q | ... |

Step 2: Classify each concern

See: references/concern-classification.md

Tag each item as one of: misunderstanding | evidence_gap | novelty | baseline_fairness | scope_claim | writing_clarity | theory | efficiency | other

Step 3: Match reviewer mindset (X)

See: references/mindset-matching-heuristics.md

Score the review on 5–7 behavior signals (openness, severity, constructiveness, specificity, skepticism, harshness, actionability). Map scores to a cluster in references/mindset-library.md.

State: matched cluster name, confidence (high / medium / low), and the specific phrases that triggered the match.

Step 4: Strategy priorities for this mindset (Y)

From the matched cluster in references/mindset-library.md, read:

  • Historical up-rate: calibrate how likely a score increase is.
  • Rule-stat diffs (success vs. failure %): boost tactics with positive diff.
  • Cohen's d effects: highlight dimensions with d > 0.8 in success group.
  • Success / failure patterns: concrete do's and don'ts from data.
  • Key strategy: one-sentence summary for this cluster.

Cross-check dimensions in references/strategy-dimensions.md.

Step 5: Per-concern guidance

For each concern, emit a guidance block (not final prose):

### R?.W?: [short title]
- **Concern type**: ...
- **Mindset-aware strategy**: ...
- **Recommended structure**: Acknowledge → Response → Evidence → Revision note
- **Clarify from paper?**: yes/no: where to look (section, table, appendix)
- **New experiment needed?**: yes/no: what exactly (no fabricated numbers)
- **Tone note**: ...
- **Template**: A / B / C: see references/response-templates.md
- **Avoid**: ...

Do not fabricate experimental numbers. Mark anything unverified as [TO VERIFY].

Step 6: Integrity gate

Before finalizing, run through references/checklist.md.

Key flags:

  • Every W/Q has a guidance block.
  • No fabricated numbers.
  • Defensive phrases (e.g., "you misunderstood") flagged.
  • Overpromise risk flagged for scope_claim and evidence_gap types.

Step 7: Output format

Deliver a ## Rebuttal Guidance section containing:

  1. Reviewer mindset summary: cluster name, confidence, identifying phrases.
  2. Global strategy priorities: 3–5 bullets from mindset data.
  3. Per-concern guidance: Step 5 blocks for each W/Q.
  4. Checklist highlights: pass/fail on key integrity items.

Reference map

| Purpose | File | |---------|------| | Concern type → response priority | concern-classification.md | | Reviewer signal → mindset cluster | mindset-matching-heuristics.md | | Mindset clusters with stats & patterns | mindset-library.md | | 10 strategy dimensions (Y) | strategy-dimensions.md | | Response templates A / B / C | response-templates.md | | Pre-submit integrity checklist | checklist.md |

Related Skills

View on GitHub
GitHub Stars7.5k
CategoryDevelopment
Updated2mo ago
Forks465

Languages

Python

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium