artifact-create

Package research code into a Docker artifact with pinned dependencies and clean-room verification.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/UnaryLab/ai-for-research --skill artifact-create
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: artifact-create
Source: https://github.com/UnaryLab/ai-for-research/tree/main/skills/artifact-create
Command: npx skills add https://github.com/UnaryLab/ai-for-research --skill artifact-create

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill packages your research code into a reproducible artifact that evaluators can run end-to-end, so your results can be validated and rerun in a clean room for artifact-evaluation badges.

Core Features & Use Cases

  • Clean-first, behavior-preserving packaging: runs code-clean and ensures the cleaned code still reproduces the same claimed results.
  • Pinned, Dockerized environments: bakes your code plus a fully pinned dependency stack into a Docker image using a fixed base (no latest tags) and no baked secrets.
  • Clean-room verification and AE paperwork: builds the image and reproduces the key results from scratch, while producing README/INSTALL, an Artifact Appendix, and a result-to-command map for Available/Functional/Reusable/Reproduced.

Quick Start

Use the artifact-create skill to package and verify your own project as a Docker-based, clean-room reproducible artifact for ACM/USENIX artifact evaluation.

Frequently Asked Questions about artifact-create

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

FAQPage Schema
How do I package research code into a reproducible artifact for artifact evaluation?

This Skill packages research code into a reproducible artifact by cleaning the project, baking a pinned Docker environment, and verifying results in a clean-room container to ensure evaluators can reproduce your claimed findings end-to-end.

What is clean-room verification for a Docker-based research artifact?

Clean-room verification builds your Docker image and reproduces key results from scratch in an isolated container, proving the artifact is self-contained and evaluator-ready for ACM or USENIX reproducibility badges.

How do I prepare an Artifact Appendix and result-to-command map for an ACM submission?

Preparing an Artifact Appendix and result-to-command map is handled by this Skill, which generates the necessary AE paperwork including README, INSTALL files, and access plans alongside your packaged Docker artifact.

Can I use Docker to handle large datasets and pinned dependencies for code reproducibility?

Yes, this Skill uses Docker with fully pinned dependencies and fixed base images to guarantee reproducibility, handling large data via mounts or checksummed downloads while avoiding baked secrets.

Does this packaging process preserve the original behavior of my cleaned research code?

Yes, the packaging process uses a clean-first, behavior-preserving approach that runs code-clean and verifies the cleaned code still reproduces the exact same claimed results before finalizing the Docker artifact.

What are the limitations when baking a Docker image for artifact evaluation?

Limitations include avoiding baked secrets and preventing the use of latest tags for base images; the process requires fixed base images, fully pinned dependencies, and explicit handling of large data via mounts or checksummed downloads.