SkillAgentSearch skills...

aistats-reproducibility

Use when strengthening AISTATS reproducibility evidence, including the official reproducibility checklist, statistical assumptions, proofs, datasets, hyperparameters, random seeds, compute, uncertainty estimates, baselines, code/data release statements, and checklist-to-claim consistency audits.

Install / Use

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

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

83/100

Supported Platforms

Universal

Our assessment of aistats-reproducibility

aistats-reproducibility scores 83/100 on our quality scale, 3184th of 4,702 Development & Engineering skills we index.

Its SKILL.md is 3.4 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 about 2 months ago, so aistats-reproducibility is actively maintained.
  • Our last check on 2026-11-07 found the source still online.
  • 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. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

aistats-reproducibility compared with similar skills

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

SkillScoreStarsUpdatedFormat
aistats-reproducibility (this skill)by brycewang-stanford831.2k2mo agoSKILL.md
taste-skillby Leonxlnx100117.6k9d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.3ktodayCLAUDE.md
claude-howtoby luongnv8910047.4k3d agoCLAUDE.md
lobehubby lobehub10085.7ktodayMCP Server

Frequently asked questions

How do I install aistats-reproducibility?
Run npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aistats-reproducibility. The install tabs above show the steps for each supported agent.
Which AI agents does aistats-reproducibility 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-reproducibility safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. 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-reproducibility still maintained?
The repository was last updated about 2 months ago, so aistats-reproducibility is actively maintained.

name: aistats-reproducibility description: Use when strengthening AISTATS reproducibility evidence, including the official reproducibility checklist, statistical assumptions, proofs, datasets, hyperparameters, random seeds, compute, uncertainty estimates, baselines, code/data release statements, and checklist-to-claim consistency audits.

AISTATS Reproducibility

Use this before submission and again before camera-ready. Reopen the current CFP and OpenReview forms to confirm whether a reproducibility checklist is required.

Evidence map

  • Map each theorem, algorithmic claim, simulation claim, and empirical claim to a verifiable location in the paper, appendix, supplement, or artifact package.
  • For theory, state assumptions, proof dependencies, convergence conditions, constants, and failure modes clearly enough for statistical readers.
  • For experiments, report datasets, splits, preprocessing, evaluation metrics, baselines, hyperparameter ranges, final selected settings, seeds, repeated runs, compute, and runtime.
  • For small performance differences, add uncertainty estimates: standard errors, confidence intervals, paired tests, bootstrap intervals, or repeated trials as appropriate.
  • Explain missing code/data honestly and describe how a reader could reproduce the analysis in principle.
  • Keep the checklist consistent with the manuscript; contradictions between checklist and paper are review-risk multipliers.

Checklist-to-claim audit table

| Checklist item | Pure-theory answer | Theory-plus-experiments answer | |---|---|---| | Code availability | NA only if there is literally no computation | Anonymous archive, or an honest stated reason | | Assumptions stated | Every theorem lists its conditions inline | Plus a note on which experiments satisfy them | | Error bars | NA for deterministic results | Required for every stochastic figure and table | | Compute resources | NA | Hardware, runtime, and total number of runs |

Marking NA on an item the paper actually triggers is a recognizable AISTATS red flag, because reviewers cross-check checklist answers against the PDF and read contradictions as carelessness about the rest of the paper.

Vignette: a rates-plus-simulation paper

Consider a submission proving posterior contraction rates for a Bayesian nonparametric model, validated by MCMC simulation. Its reproducibility spine: prior hyperparameters and their selection rule, chain length, burn-in, convergence diagnostics, replication seeds, and a statement of which contraction-theorem conditions the simulated model satisfies — plus one honest sentence about the condition it does not.

Degrees of reproducibility

  • Turnkey: one command regenerates each figure from logged seeds.
  • Scripted: scripts exist but require documented manual steps or external data access.
  • Descriptive: prose detailed enough that a competent reader could rebuild the pipeline.

For AISTATS, simulations should be turnkey because statistician reviewers actually rerun them; large real-data pipelines may stay scripted with deviations documented. Stating the achieved level honestly beats overpromising turnkey behavior that fails on a clean machine.

Output format

[Claim inventory] <claim -> evidence location>
[Checklist status] complete / inconsistent / missing
[Statistical reproducibility gaps] <assumptions/seeds/uncertainty/hyperparameters/compute>
[Paper fixes] <must appear in main PDF>
[Supplement fixes] <appendix or artifact additions>

Related Skills

View on GitHub
GitHub Stars1.2k
CategoryDevelopment
Updated2mo 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
aistats-reproducibility — Universal Skill: Install & Safety Check | SkillAgent