Agent skill

Stage4 Refine Followup

by runtsang in runtsang/RebuttalStudio

Refine a Stage 4 follow-up response using condensed prior discussion context, current follow-up question, and the user's draft.

No licenceAuto-check passedResearch & Science

Install Stage4 Refine Followup

skills CLI
$ npx skills add runtsang/RebuttalStudio --skill stage4-refine-followup -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install runtsang/RebuttalStudio stage4-refine-followup --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/runtsang/RebuttalStudio.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/stage4/refine .claude/skills/stage4-refine-followup && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
stage4-refine-followup
GitHub stars
218
Token cost
~215 tokens
SKILL.md length
80 words
Files
1
Skills in repo
19
Repo updated
First seen
Licence
None found

At a glance

Refine a Stage 4 follow-up response using condensed prior discussion context, current follow-up question, and the user's draft.

  • Works in 5 steps: Keep claims grounded in provided context… → Address the follow-up question directly… → Maintain respectful, concise academic… → …
  • Research & Science work in your project
  • SKILL.md covers Goal, Inputs, Output and Rules
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Stage4 Refine Followup is an agent skill from runtsang/RebuttalStudio. Refine a Stage 4 follow-up response using condensed prior discussion context, current follow-up question, and the user's draft.

Its SKILL.md is about 220 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Research & Science. The repository describes itself as: A rebuttal editor for researchers to craft high-quality academic rebuttals — so you can focus on what to say, not how to format it.

When your agent uses it

  • Research & Science work in your project

Example prompts

  • “/stage4-refine-followup”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Keep claims grounded in provided context and draft.
  2. Address the follow-up question directly in the opening lines.
  3. Maintain respectful, concise academic tone.
  4. Avoid fabrication of data/citations/experiments.
  5. Preserve the core intent of user draft while improving clarity and flow.

What it can do on your machine

Read from SKILL.md and the folder at commit 1f81e2f. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are json).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Stage4 Refine Followup loads about 215 tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 80 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~38
When it runs · the whole SKILL.md, loaded when a task matches
~215

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Without a licence we can't republish the file, so here is its outline and opening line. It has 80 words (~215 tokens).

“Generate a polished follow-up response for multi-round reviewer discussion.”

— opening of SKILL.md by runtsang
name
stage4-refine-followup

Read the full SKILL.md on GitHub

Files

Just SKILL.md in skills/stage4/refine of runtsang/RebuttalStudio.

Open the folder on GitHubat commit 1f81e2f

Compare with similar skills

Stage4 Refine Followup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Stage4 Refine Followup compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Stage4 Refine Followup this skillruntsang/RebuttalStudio218—~215Automated safety check: PassNone
Hypothesis Generationspacering-net/codeg3.9k14 repos~3.6kAutomated safety check: NotesMIT
GitHub Deep Researchbytedance/deer-flow84k4 repos~1.3kAutomated safety check: PassMIT
Nature Paper CardYuan1z0825/nature-skills47k2 repos~2.1kAutomated safety check: PassApache-2.0
Content Research Writerweapp-tailwindcss/weapp-tailwindcss1.9k25 repos~3.5kAutomated safety check: PassMIT
Last30daysmvanhorn/last30days-skill64k—~7.9kAutomated safety check: NotesMIT

Similar skills

  • Hypothesis Generation

    spacering-net/codeg

    Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.

    3.9k GitHub starsUsed in 14 repos~3.6k tokens
    Research & ScienceAuto-check: notes
  • GitHub Deep Research

    bytedance/deer-flow

    Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.

    84k GitHub starsUsed in 4 repos~1.3k tokens
    Research & ScienceAuto-check passed
  • Nature Paper Card

    Yuan1z0825/nature-skills

    Builds a structured deep-reading card for one scientific paper, covering methods, how experiments support claims, limitations and research ideas, with a script to prepare the source.

    47k GitHub starsUsed in 2 repos~2.1k tokens
    Research & ScienceAuto-check passed
  • Content Research Writer

    weapp-tailwindcss/weapp-tailwindcss

    Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section.

    1.9k GitHub starsUsed in 25 repos~3.5k tokens
    Research & ScienceAuto-check passed
  • Last30days

    mvanhorn/last30days-skill

    Research what people actually say about any topic in the last 30 days.

    64k GitHub stars~7.9k tokensUpdated yesterday
    Research & ScienceAuto-check: notes
  • Peer Review

    spacering-net/codeg

    Structured manuscript/grant review with checklist-based evaluation.

    3.9k GitHub starsUsed in 17 repos~5.9k tokens
    Research & ScienceAuto-check: notes

More from runtsang/RebuttalStudio

All 19 skills in this repo
  • Citation Verification

    runtsang/RebuttalStudio

    Verification guide for citations added during rebuttal writing.

    218 GitHub stars~1.5k tokensUpdated 6 mo ago
    Auto-check passed
  • Review Response

    runtsang/RebuttalStudio

    Systematic review response strategy guide for RebuttalStudio.

    218 GitHub stars~1.6k tokensUpdated 6 mo ago
    Auto-check passed
  • Stage5 Final Remarks

    runtsang/RebuttalStudio

    Fill a Stage5 final remarks template using condensed discussion markdown from all reviewers and optional rating changes.

    218 GitHub stars~342 tokensUpdated 6 mo ago
    Auto-check passed
  • Document Memory Summarize

    runtsang/RebuttalStudio

    Summarize extracted paper text into concise Markdown memory for later Stage 2 and Stage 4 background use, with fixed section headings and no fabricated claims.

    218 GitHub stars~277 tokensUpdated 6 mo ago
    Auto-check passed
  • Text Condense

    runtsang/RebuttalStudio

    Condense rebuttal prose into fewer words without changing the original meaning.

    218 GitHub stars~465 tokensUpdated 6 mo ago
    Auto-check passed
  • Rebuttal Self Review

    runtsang/RebuttalStudio

    Systematic quality check for a completed rebuttal document before submission.

    218 GitHub stars~1.5k tokensUpdated 6 mo ago
    Auto-check passed

Questions about Stage4 Refine Followup

What does Stage4 Refine Followup do?

Refine a Stage 4 follow-up response using condensed prior discussion context, current follow-up question, and the user's draft. Stage4 Refine Followup is an agent skill from runtsang/RebuttalStudio. Refine a Stage 4 follow-up response using condensed prior discussion context, current follow-up question, and the user's draft.

When should I use Stage4 Refine Followup?

Stage4 Refine Followup fits situations like: research & Science work in your project.

How do I install Stage4 Refine Followup in Claude Code?

Run `npx skills add runtsang/RebuttalStudio --skill stage4-refine-followup -a claude-code`. Or copy the skill folder (skills/stage4/refine in runtsang/RebuttalStudio) into .claude/skills/stage4-refine-followup in your project. Claude Code loads it when a task matches its description.

How do I install Stage4 Refine Followup in Codex?

Run `npx skills add runtsang/RebuttalStudio --skill stage4-refine-followup -a codex`. Or copy the skill folder (skills/stage4/refine in runtsang/RebuttalStudio) into .agents/skills/stage4-refine-followup in your project. Codex loads it when a task matches its description.

Can I use Stage4 Refine Followup in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add runtsang/RebuttalStudio --skill stage4-refine-followup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/stage4-refine-followup, .gemini/skills/stage4-refine-followup, .github/skills/stage4-refine-followup and .opencode/skills/stage4-refine-followup in your project.

What does Stage4 Refine Followup need to run?

SKILL.md names no scripts, command-line tools or credentials: Stage4 Refine Followup is instructions for the agent only.

Does Stage4 Refine Followup access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Stage4 Refine Followup safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Stage4 Refine Followup use?

No licence was found for Stage4 Refine Followup or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.

How many tokens does Stage4 Refine Followup use?

About 215 tokens (SKILL.md is roughly 860 characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Stage4 Refine Followup?

Skills that share tags, products or a category with Stage4 Refine Followup: Hypothesis Generation (spacering-net/codeg, 3.9k stars), GitHub Deep Research (bytedance/deer-flow, 84k stars), Nature Paper Card (Yuan1z0825/nature-skills, 47k stars) and Content Research Writer (weapp-tailwindcss/weapp-tailwindcss, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Stage4 Refine Followup?

runtsang (a GitHub user) maintains it in runtsang/RebuttalStudio, which has 218 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on April 3, 2026.

Source: runtsang/RebuttalStudio on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.