Use when building the replication package for an American Journal of Political Science (AJPS) manuscript. AJPS is famous for MANDATORY third-party PRE-publication verification — an independent verifier re-runs your deposited code and confirms it reproduces the numerical results in the main text before the article is published, with materials deposited to the AJPS Dataverse on Harvard Dataverse. Prepares the package; it does not waive requirements.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
Instruções da origem · Visualização somente leitura
name
ajps-replication-and-verification
description
Use when building the replication package for an American Journal of Political Science (AJPS) manuscript. AJPS is famous for MANDATORY third-party PRE-publication verification — an independent verifier re-runs your deposited code and confirms it reproduces the numerical results in the main text before the article is published, with materials deposited to the AJPS Dataverse on Harvard Dataverse. Prepares the package; it does not waive requirements.
This is AJPS's signature differentiator. Unlike journals that check reproducibility in-house (or not at
all), AJPS sends your deposited materials to an independent third party that actually re-runs the
code and confirms it reproduces the numerical results reported in the main text — before
publication. If it does not reproduce, the article does not publish until it does. Build the package as
you analyze (ajps-data-analysis); it cannot be improvised at acceptance.
When to trigger
Building the replication / verification package
A manuscript is accepted and you have received upload instructions (after final draft, during the
technical check, before copyediting)
Data cannot be fully shared (privacy, ethics, provider restriction) and you need a path
A qualitative or multi-method paper whose evidence needs a documented verification route
How AJPS verification actually works (official baseline checked 2026-06-20)
Deposit to the AJPS Dataverse. Materials go into a Dataset within the AJPS Dataverse on the
Harvard Dataverse Network — not a personal site or generic cloud link. Other copies may exist
elsewhere as long as everything needed is in the AJPS Dataverse Dataset.
Independent third-party verification. A verifier re-runs the code and confirms it reproduces the
numerical results in the main text. The published article carries a statement: "The Cornell
Center for Social Sciences verified that the data and replication code submitted to the AJPS
Dataverse replicates the numerical results reported in the main text of this article." MPSA also
identifies Cornell Center for Social Sciences as the contracted replication-and-verification provider.
Qualitative path. Qualitative / multi-method materials follow the AJPS verification guidelines
and qualitative checklist: document collection procedures, instruments, analytic operations, source
fragments or access restrictions, and any exemption route needed for human-subjects, copyright, or
legal constraints.
Timing. It happens after the final draft is submitted, during the technical check, before
copyediting — late enough that fixing an unscripted analysis under deadline is painful.
Build-as-you-go checklist (so the re-run matches)
readme.txt lists and describes every file (group as "Data files", "Stata .do files", "Files
to Reproduce Table 1", ...)
One master script runs the modular scripts in order and sets the working directory once
set seed for every stochastic step (Monte Carlo, bootstrap, randomization inference, jitter)
