SkillAgentSearch skills...

aistats-workflow

Use when planning an AISTATS project timeline from venue fit through abstract submission, full-paper upload, supplementary material, review release, author-reviewer discussion, decision, camera-ready, PMLR publication, registration, presentation, and artifact release, with backward-planning offsets…

Install / Use

npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aistats-workflow

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

83/100

Category

Automation

Supported Platforms

Universal

Our assessment of aistats-workflow

aistats-workflow scores 83/100 on our quality scale, 2259th of 2,889 Automation skills we index.

Its SKILL.md is 3.9 KB long, split into 6 sections with 1 code example: a solid amount of guidance for an agent.

With 1,158 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
15/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 21 days ago, so aistats-workflow is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands.

Automated pattern scan on 2026-10-06. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

aistats-workflow compared with similar skills

All 4 of these similar skills score higher than aistats-workflow; compare them before choosing.

SkillScoreStarsUpdatedFormat
aistats-workflow (this skill)by brycewang-stanford831.2k21d agoSKILL.md
Agent-Reachby Panniantong10092.1k20d agoCLAUDE.md
Scraplingby D4Vinci10085.9ktodayMCP Server
rufloby ruvnet10074.0ktodayMCP Server
algorithmic-artby anthropics100177.9k13d agoSKILL.md

Frequently asked questions

How do I install aistats-workflow?
Run npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aistats-workflow. The install tabs above show the steps for each supported agent.
Which AI agents does aistats-workflow work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is aistats-workflow safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is aistats-workflow still maintained?
The repository was last updated 21 days ago, so aistats-workflow is actively maintained.

name: aistats-workflow description: Use when planning an AISTATS project timeline from venue fit through abstract submission, full-paper upload, supplementary material, review release, author-reviewer discussion, decision, camera-ready, PMLR publication, registration, presentation, and artifact release, with backward-planning offsets for theory-plus-experiments papers.

AISTATS Workflow

Use this as the project-management skill for an AISTATS submission. Replace all dates with the current official timetable and work backwards from OpenReview cutoffs.

AISTATS is a conference, not a journal: it has no standing editor-in-chief and no article-processing charge. The rotating leadership is the per-edition General Chairs and Program Chairs (2026 General Chairs: Emtiyaz Khan and Yingzhen Li; Program Chairs: Arno Solin and Aaditya Ramdas, verified 2026-06-22), and the cost model is registration fees, not APCs — PMLR proceedings are open-access with no author fee. Conference organizers rotate yearly, so re-check the current CFP and organization page rather than carrying a name forward.

Milestones

  • Venue fit: confirm the contribution is genuinely at the AI, ML, and statistics interface.
  • Evidence lock: freeze theorem statements, assumptions, experiments, simulations, baselines, reproducibility checklist, and supplement contents.
  • Abstract deadline: submit real title, abstract, authors, subject areas, and conflicts.
  • Full-paper deadline: upload anonymous PDF and required OpenReview fields.
  • Supplement deadline: upload anonymized appendix/code/data if current cycle allows or requires separate supplementary material.
  • Review release: triage correctness, statistical validity, novelty, clarity, and reproducibility concerns.
  • Discussion period: draft concise anonymous text-only clarifications; avoid forbidden links or unsupported new results.
  • Decision: archive reviews, discussion, meta-review, decision, and submitted versions.
  • Acceptance: prepare PMLR camera-ready files, registration, in-person presentation, and public artifact release.

Backward plan from the paper deadline

| Weeks out (heuristic) | Theory-plus-experiments milestone | |---|---| | 8+ | Theorems proved, assumption set frozen | | 6 | Simulations designed against each theorem | | 4 | Real-data runs complete, seeds logged | | 3 | Full draft sitting in AISTATS two-column format | | 2 | Internal mock review by a statistics-minded reader | | 1 | Checklist pass, anonymity sweep, supplement assembly | | 0 | Abstract then full paper on OpenReview; supplement by its own cutoff |

These offsets are planning heuristics only — anchor every one of them to the current official timetable, never to a previous cycle's calendar.

Failure modes by stage

  • Theory still moving at week 3 forces last-minute theorem edits nobody has verified — the classic AISTATS correctness reject in the making.
  • Leaving format conversion to the final week surfaces overflow late, because two-column math is far tighter than a one-column working draft.
  • Skipping the mock review forfeits the only chance to hear "your experiments violate Assumption 2" from a friend instead of a reviewer.
  • Building the supplement after the paper deadline under time pressure is how anonymity leaks ship.

Coordination notes

  • Assign one named owner for the reproducibility checklist and another for the anonymity sweep; shared ownership is how both slip.
  • Archive the exact submitted PDF, supplement, and checklist, since discussion-phase replies must quote them precisely.

Output format

[Current stage] idea / experiments / writing / abstract / submission / supplement / discussion / accepted
[Next official deadline] <date and source, or unknown>
[Critical path] <three tasks that determine readiness>
[Risk register] <page/anonymity/statistical evidence/supplement/reproducibility/presentation>
[Owner map] <task -> person or role>

Related Skills

View on GitHub
GitHub Stars1.2k
CategoryAutomation
Updated21d ago
Forks153

Languages

Stata

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions