Asq Rebuttal logo

Asq Rebuttal

Community
franklee16
asq-rebuttal

Use when drafting the response to an Administrative Science Quarterly (ASQ) R&R after the manuscript has been revised — structuring the response letter and handling reviewer/editor comments. Drafts the response; it does not perform the underlying revisions (do those first).

Overview

Publisherfranklee16
Repositoryacademic-research-skills
Skill nameasq-rebuttal
Stars
225
Forks
34
Bundled files
Instructions only
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by franklee16 on GitHub. Read the source before you install it.

Installation

Install the Asq Rebuttal AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/franklee16/academic-research-skills/tree/master/Awesome-Journal-Skills-main/Administrative-Science-Quarterly-Skills/skills/asq-rebuttal
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/franklee16/academic-research-skills.git /tmp/academic-research-skills
mkdir -p .claude/skills
cp -r /tmp/academic-research-skills/Awesome-Journal-Skills-main/Administrative-Science-Quarterly-Skills/skills/asq-rebuttal .claude/skills/asq-rebuttal
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Asq Rebuttal in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Asq Rebuttal on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Asq Rebuttal is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

R&R Rebuttal (asq-rebuttal)

When to trigger

  • You have an ASQ R&R and have already revised the manuscript
  • You need to structure a point-by-point response document
  • Reviewers disagree and you must navigate between them without contradicting yourself

Revise the paper first. The response letter documents changes you made; it is not a substitute for making them. If you have not revised yet, return to the relevant asq-* skill.

Mindset for an ASQ revision

ASQ's review is developmental — treat reviewers as collaborators who took the idea seriously. The winning posture is gracious, responsive, and intellectually serious: accommodate where they are right, and where you disagree, argue with evidence and respect rather than dismissal. The central question the handling editor (under Editor Beth Bechky, term began July 1, 2025) and reviewers will ask is "did the idea mature?" — consistent with ASQ's emphasis on curating papers that will endure. Foreground how the contribution got deeper, not just which boxes you ticked. A response letter that reads as a checklist of mechanical robustness additions — adequate at some quantitative-leaning journals — will underperform here if the theoretical insight has not sharpened.

Structure of the response

  1. Cover note to the editor. Thank the team; summarize the 3–5 most important changes and how the contribution is now sharper. Address the editor's central theoretical ask explicitly and up front.
  2. Point-by-point responses, grouped by reviewer, then by comment. For each:
    • Quote the comment verbatim (or faithfully paraphrase).
    • State your response: Accepted / Partially accepted / Respectfully disagree.
    • Describe the exact change and cite the new location (page, section, table).
    • Where you disagree, give the reasoned case with evidence, and offer a compromise if possible.
  3. A summary of major changes at the top is helpful for editors tracking a multi-round file.

Handling hard cases

  • Reviewers disagree: state both positions, explain your resolution, and let the editor see you reasoned it through. Do not silently side with one and ignore the other.
  • A request would harm the paper: explain why (theoretical or evidentiary cost), propose an alternative that meets the underlying concern, and defer to the editor.
  • "Deepen the contribution": this is the most common ASQ ask — show concretely how the theory is now sharper, the surprise clearer, the mechanism more specified. Mechanical additions alone will not satisfy it.
  • Out-of-scope requests: politely note scope and, if useful, flag them as future work.

Tone and craft

  • Respectful, specific, and confident — never defensive or dismissive.
  • Make the editor's job easy: clear navigation, change locations, and a quotable summary.
  • Keep the letter self-contained; a reviewer should not need the tracked-changes file to follow it.
  • Ensure consistency: a change made for Reviewer 1 must not contradict a response to Reviewer 2.

Checklist

  • Manuscript revised before writing the letter
  • Editor's central theoretical ask addressed first and explicitly
  • Every comment answered; none skipped or merged away
  • Each response states accept/partial/disagree + the exact change location
  • Disagreements argued with evidence and a proposed compromise
  • Reviewer conflicts navigated without internal contradictions
  • "Deepen the contribution" answered with substance, not just additions
  • Tone gracious and serious throughout; letter is self-contained

Anti-patterns

  • Writing the response before actually revising
  • Defensive or dismissive replies ("the reviewer misunderstood")
  • Claiming a change was made without pointing to where
  • Satisfying one reviewer in a way that contradicts another's response
  • Answering "deepen the contribution" with cosmetic additions
  • A letter that requires the editor to diff the manuscript to verify changes

Output format

【Round】1st / 2nd / later
【Editor's core ask addressed】how + where
【Comments handled】N / N (none skipped)
【Disagreements】[...] + evidence/compromise
【Contribution deepened】how the idea matured
【Consistency check】no cross-reviewer contradictions
【Next step】resubmit via the editorial system

Frequently asked questions

What does the Asq Rebuttal AI skill do?

Use when drafting the response to an Administrative Science Quarterly (ASQ) R&R after the manuscript has been revised — structuring the response letter and handling reviewer/editor comments. Drafts the response; it does not perform the underlying revisions (do those first).

Why use Asq Rebuttal on TypingMind?

Because you install it once and use it with any model. Asq Rebuttal is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Asq Rebuttal in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/franklee16/academic-research-skills/tree/master/Awesome-Journal-Skills-main/Administrative-Science-Quarterly-Skills/skills/asq-rebuttal. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Asq Rebuttal?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Asq Rebuttal?

As many as you like. As long as a model supports skills, you can use Asq Rebuttal with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Asq Rebuttal AI skill free?

It is published on GitHub by franklee16. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇