replication-package

Automate preparation of publication-ready replication packages for academic journals.

21|4|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/HaipingXu/social-science-claude-scholar --skill replication-package
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: replication-package
Source: https://github.com/HaipingXu/social-science-claude-scholar/tree/main/skills/replication-package
Command: npx skills add https://github.com/HaipingXu/social-science-claude-scholar --skill replication-package

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill streamlines the complex process of preparing and organizing research data, code, and documentation to meet the stringent replication package requirements of top academic journals.

Core Features & Use Cases

  • Standardized Structure: Provides a clear, journal-compliant directory structure for replication files.
  • Automated Scripting: Offers master script templates (Stata/Python) to orchestrate the entire replication process.
  • Documentation Guidance: Details requirements for README files, data descriptions, and software version capture.
  • Journal Compliance: Addresses specific standards for AER, AEJ, QJE, APSR, AJPS, and JOP.
  • Use Case: A researcher needs to submit their paper to AER and must include a replication package. This Skill guides them through creating the necessary README, organizing code and data, and ensuring all journal requirements are met for submission to openICPSR.

Quick Start

Use the replication-package skill to prepare a replication package for submission to AER, following the provided structure and README guidelines.

Frequently Asked Questions about replication-package

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prepare a replication package for journal submission?

To prepare a replication package for journal submission, you must structure your data, code, and documentation into a journal-compliant directory, generate README files, and ensure software version compatibility for repositories like openICPSR.

What should be included in a README file for academic reproducibility?

A README file for academic reproducibility should include detailed data descriptions, instructions for running master scripts, and captured software versions. This documentation guides reviewers through orchestrating the entire replication process step by step.

Does this replication package preparation support Stata and Python master scripts?

Yes, replication package preparation supports Stata and Python master scripts by providing automated templates. These templates orchestrate the entire replication process, ensuring code quality and meeting specific journal standards like AER and APSR.

Can I use this workflow to meet AER and APSR data management standards?

Yes, you can use this workflow to meet AER and APSR data management standards. It addresses specific requirements for AER, AEJ, QJE, APSR, AJPS, and JOP, guiding the upload of structured replication files to openICPSR and Harvard Dataverse.

What's the best way to organize code and data for open science repositories?

The best way to organize code and data for open science repositories is using a standardized directory structure with master scripts and a comprehensive README. This ensures publication-ready compliance for platforms like Harvard Dataverse.

Why does my journal submission require specific software version documentation?

Your journal submission requires specific software version documentation to guarantee reproducibility across different computing environments. Capturing these versions in your replication package README ensures reviewers can successfully execute the provided Stata or Python scripts.