Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Use when assembling the data, code, and experiment materials for a Journal of Risk and Uncertainty (JRU) manuscript and writing its Data Availability Statement. Builds a transparent, reproducible package; it does not invent evidence or citations.
Use when packaging code, datasets, configs, and deployment evidence for a KDD paper, where the repository cited in the submission is the only artifact reviewers can reach because rebuttals ban links. Covers anonymized repo construction, scale-claim harnesses, ADS evidence without production data, and post-acceptance release.
Use when assembling the data-and-code replication package required by 《管理世界》 after conditional acceptance, drafting the README in Chinese, or auditing a deposit before editorial-office submission. Implements 《管理世界》"数据可获得性政策" (effective 2023, updated 2025), with explicit handling for CSMAR / Wind / 国泰安 等受限商业数据库 and Chinese government micro-data. 本技能服务于《管理世界》(Management World, MW)。
Use when meeting open-science and reproducibility obligations for a Perspectives on Psychological Science (PoPS) piece — repository deposit for any original data, a documented and ideally preregistered systematic protocol for meta-science, and exemplary disclosure (PoPS is an open-science leader). Builds the transparency layer; it does not draft the synthesis (ppsych-organizing-framework) or run the submission preflight (ppsych-submission).
Use to assemble a Quantitative Economics (QE) replication package that passes the Econometric Society Data Editor's pre-acceptance reproducibility check — raw data, code, documentation, README, and any exemption requests — under the DCAS-compatible ES Data and Code Availability Policy (NOT the JAE archive). Builds and audits the package; it does not run the estimation.
Use when assembling the data and code replication package for a Quarterly Journal of Economics (QJE) manuscript — required for accepted empirical papers under QJE's data-availability policy. Builds a reproducible deposit; it does not perform the analysis itself.
Use when building or auditing the quantitative analysis behind a Review of Economic Dynamics (RED) manuscript — calibration, moment-matching, structural estimation, and numerical-solution discipline for dynamic models, plus reproducible-computation hygiene that the RED code-first culture expects. Lighter on raw empirics for purely theoretical papers; focused on numerical examples and reproducible computation there.
Use when assembling the data and code deposit for an accepted empirical The Review of Economic Studies (REStud) manuscript, writing the README, or auditing reproducibility before the journal's Data Editor runs the pre-publication reproducibility check. Builds a deposit-ready package; does not run the analysis. Verify the current REStud/OUP data policy on the official page.
Use when packaging code, run files, test collections, or judgments for a SIGIR submission — deciding between an artifact inside a full/short paper and a standalone Resources track paper, building reviewer-runnable IR repositories, run-file and qrels hygiene, licensing and datasheets, and single- vs double-anonymous handling.
Use when packaging the artifacts behind a UIST paper — code, toolkits, hardware design files, and datasets — first as anonymous review-time evidence that the system is real, then as a public release engineered for reuse, in a venue with no formal badge committee doing the checking for you.