Menu

Individual skill

ase-author-response

0upvotes

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.

ASE-Skills/skills/ase-author-response/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,400
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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
Back to top