agentsclimarketplace
Sign in

Package artifacts

Skill VincenzoImp/academic-research-skills/skills/package-artifacts

Use when packaging the artifacts of a paper for submission — assembling everything promised in the manuscript plus the venue's badge and artifact-evaluation requirements.From its SKILL.md

Install
npx -y skills add VincenzoImp/academic-research-skills --skill package-artifacts

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.1 KB, 426 tokens by cl100k_base, as published. Nobody here has run it

Package Artifacts

Assemble papers/<slug>/artifacts/: the self-contained bundle a reviewer or artifact-evaluation committee receives.

Read First

  • papers/<slug>/venue.md — the venue's badge/artifact requirements
  • papers/<slug>/manuscript/main.tex — what the paper promises
  • references/artifact-standard.md

Procedure

  1. List what must ship: every artifact promised in the manuscript (data, code, models, scripts) plus everything the venue's badge requirements demand.
  2. Stage by copying the relevant contributions/<slug>/ folders into artifacts/ — they are self-contained by construction. Never hand-edit the staged copies: fix problems at the source contribution and re-stage.
  3. Add the bundle-level files: an artifact README (claims-to-artifact map, setup, smoke test, expected outputs and runtime), license, citation file, and a MANIFEST.md listing every file with its sha256 checksum.
  4. Strip what must not ship: gitignored material, secrets, raw sensitive data, and — when the venue requires anonymization — identifying paths and names.
  5. Verify standalone: the bundle works without the surrounding repo (no ../ references, bibliography resolved, environment declared inside).
  6. Walk references/artifact-standard.md and the venue checklist item by item; record the mapping in the artifact README.

Rules

  • Never hand-edit staged contribution copies: fix problems at the source contribution and re-stage.
  • Strip gitignored material, secrets, and raw sensitive data before shipment.
  • The bundle is self-contained: environment, data provenance, and bibliography resolve inside it — no ../ references or external paths.

Done When

  • The bundle satisfies the venue requirements and the artifact standard, MANIFEST.md checksums are fresh, and a clean-room smoke test (fresh unzip elsewhere, follow only the bundle README) succeeds

What ships with it: 1 file

837 B alongside SKILL.md

references/

Keep looking

Skills are one crate of 326,499. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.