ase-author-response
Use when drafting ASE (IEEE/ACM Automated Software Engineering) author responses, covering the double-anonymous rebuttal that must first survive the early-rejection gate and — distinctively — the criteria-bound revision-round summary-of-changes that maps every stated revision criterion to a concrete change and is re-checked against those criteria.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ase-author-response --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# ASE Author Response Use this after ASE reviews are released. ASE has **two distinct speaking turns**, and conflating them is a common mistake: a short **rebuttal** (for papers that survive the early-rejection gate), and — if you receive a **Revision** — a **summary-of-changes** accompanying a revised paper that is re-checked against the reviewers' explicitly stated criteria. Both must respect double-anonymity: no author names, institutions, or revealed repository ownership, even to strengthen a point. ## Triage (both turns) - Answer what affects the decision: significance and soundness of the automation, evaluation quality on real subjects, threats to validity, clarity, and the Data Availability / artifact posture. - Use evidence that already exists or that the revision will concretely add — never a vague promise. - Correct factual misreadings first; a reviewer who misread your tool's configuration or a table is often persuadable. - Keep every word anonymous. Do not name your tool's real name, institution, grant, or a private repository. ## Turn 1 — the rebuttal (only if you survived early rejection) If your paper reached the rebuttal stage, at least one reviewer saw value; a uni
- Triage (both turns)
- Turn 1 — the rebuttal (only if you survived early rejection)
- Turn 2 — the revision summary-of-changes (the distinctive ASE move)
- Reviewer pushback patterns (automated-SE flavored)
- Anonymity in the response (easy to slip)
- Calibration
- Output format
What does the ase-author-response skill do?
Use when drafting ASE (IEEE/ACM Automated Software Engineering) author responses, covering the double-anonymous rebuttal that must first survive the early-rejection gate and — distinctively — the criteria-bound revision-round summary-of-changes that maps every stated revision criterion to a concrete change and is re-checked against those criteria.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ase-author-response --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.