Individual skill

aistats-author-response

Use when drafting AISTATS author responses or author-reviewer discussion replies under OpenReview, covering text-only discussion, no-link guidance, no revised-paper upload, anonymity requirements, statistician-reviewer pushback patterns, and decision-focused clarification strategy for theory-plus-experiments papers.

AISTATS-Skills/skills/aistats-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,405
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

# AISTATS Author Response

Use this after AISTATS reviews are released. Reopen the current OpenReview instructions and
author-discussion policy before drafting because response mechanics are cycle-specific.

## Triage

- Answer concerns that affect correctness, novelty, statistical validity, clarity,
  reproducibility, or fit for AISTATS.
- Use existing submitted evidence: paper sections, appendices, supplementary material,
  theorem statements, experiments, checklist entries, and code/data descriptions.
- Keep the reply anonymous. Do not reveal institution, authorship, grants, private URLs, or
  repository ownership.
- Treat discussion as clarification, not revision. Do not depend on uploading a revised paper
Back to top