submit-package

Automate creation of journal-ready replication packages with AEA-format documentation.

Updated Mar 28, 2026

Search Tags:#reproducible research #journal submission #replication package #AEA standard #code and data availability

Ready to run

npx skills add https://github.com/bgpopescu/popescu_claude --skill submit-package-bgpopescu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: submit-package
Source: https://github.com/bgpopescu/popescu_claude/tree/main/.claude/skills/submit-package
Command: npx skills add https://github.com/bgpopescu/popescu_claude --skill submit-package-bgpopescu

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation of journal-ready replication packages for research, ensuring reproducibility and standardization of research outputs.

Core Features & Use Cases

Replication Package Building: Automatically generates AEA-format README, master script, dependency documentation, data provenance, and verification checklist.
Project Inventory: Scans and documents all analysis scripts, data files, output files, manuscript files, and configuration files.
Master Script Creation: Builds a master script that runs all analysis scripts in the correct order, checks for required packages, and reports execution time.
README Creation: Creates a README following the AEA Data and Code Availability Standard, documenting data availability, computational requirements, instructions, file structure, and script descriptions.
Dependency Documentation: Documents software and hardware requirements, including installed packages and version numbers.
Data Provenance: Documents the source, access, and citation information for all datasets used.
Verification Checklist: Runs a 10-point verification checklist to ensure all components of the replication package are complete and functional.
Output Documentation: Saves all outputs to the project root and quality_reports/submission/, including the master script, README, dependency files, and verification report.

Quick Start

Run the submit-package skill on your project root directory to create a complete replication package.

Frequently Asked Questions about submit-package

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

FAQPage Schema

How do I create a journal-ready replication package for reproducible research?▼

To create a journal-ready replication package, automate project inventory, master script generation, README creation, dependency documentation, data provenance documentation, and verification checklist execution to ensure full reproducibility.

What is the AEA Data and Code Availability Standard for replication packages?▼

The AEA Data and Code Availability Standard is a formatting requirement for replication packages that documents data availability, computational requirements, instructions, file structure, and script descriptions within the project README.

How do I generate a master script to run analysis scripts in the correct order?▼

Generating a master script involves building a file that executes all analysis scripts sequentially, checks for required software packages, and reports execution time to automate the analysis pipeline.

Can I document data provenance and software dependencies automatically for my research project?▼

Yes, you can document data provenance and software dependencies automatically by scanning the project to map dataset sources and citations, and recording installed software packages and version numbers.

What is the best way to verify that all components of a replication package are complete?▼

The best way to verify replication package completeness is to run a 10-point verification checklist that ensures all components, including master scripts and README files, are complete and functional.

What file outputs do I get when automating replication package creation?▼

Automating replication package creation saves outputs to the project root and a quality_reports/submission/ directory, including the master script, README, dependency files, and verification report.