release-research-artifacts
From the author
Use when packaging the code and data a reader or reviewer will download, including releasing the code for a paper, building an anonymized repository for double-blind submission, preparing an archive with a DOI for a journal, writing citation metadata, producing a data card or model card, or preparing a submission for artifact evaluation. Use once the results are frozen, so that what ships is what produced them.
Install
npx skills add gxCaesar/open-research-skills --skill release-research-artifacts -a claude-code
Installs to .claude/skills/release-research-artifacts/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
- Ships scripts we have not reviewedLow
Why 74
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- refactor-research-codeShaishavMaisuria/research-paper-lifecycle-skillsClean research code for public release while preserving reported results. Uses release_audit.py to separate safe mechanical cleanup from ask-first behavior risks and identity leaks. Use for release-ready repos, dead experiment branches, config extraction, documented entrypoints, and double-blind code cleanup.Science★ 60
- release-governanceyha9806/academic-writing-toolkitUse when preparing, auditing, releasing, PDF-hardening, or rebuttal-hardening academic manuscripts, datasets, artifacts, reviewer packets, or claim registers involving multiple refs, local assets, human labels, agent-assisted drafts, wide tables, figure provenance, submission PDFs, or evidence-boundary checks.Documents★ 54
- prepare-journal-manuscriptsgxCaesar/open-research-skillsUse when preparing, drafting, revising, polishing, auditing, or packaging a journal manuscript, abstract, statistical or evaluation report, cover letter, editor-facing submission pack, data availability statement, peer-review response, revise and resubmit package, clean manuscript, marked manuscript, or final accepted-paper files. Also use for single-section or section-by-section polish and resuming the next section. Includes manuscript-context figures and journal-package checks without requiring another skill; disputed experiment evidence must be resolved before changing manuscript prose.Science★ 63
- verify-artifactpedrohcgs/claude-code-my-workflowProve that the file you are about to send, publish, or hand off IS the thing you mean — before it leaves your hands. Rebuild from source, check integrity, diff the derived artifact against its source, and require the recipient to echo what they received. Use before sending a paper/PDF for review, shipping a release or replication package, handing files to a coauthor or collaborator, uploading anything to an external reviewer or model, or publishing. Prevents an entire review/QA cycle from being spent on defects that exist only in the artifact, not in the work.Testing★ 1.7K
- prepare-artifactsShaishavMaisuria/research-paper-lifecycle-skillsPrepares a reproducibility artifact (code/data) for submission and badging. Use when a researcher says "artifact evaluation", "artifact appendix", "reproducibility", "badge", "Artifacts Available/Evaluated/Functional/Reusable", "Results Reproduced/Replicated", "ACM badging", "USENIX/OSDI/SOSP AE", "SIGMOD ARI", "NeurIPS code/checklist", "ACL repro checklist", "Zenodo DOI", "Software Heritage", "anonymize my code/repo", or "package my code". Builds the artifact README + appendix, the dependency/run instructions, an anonymized repo for double-blind, and archival-DOI (Zenodo version vs concept) / Software Heritage SWHID guidance; resolves the ACM badge taxonomy and the Reproduced/Replicated era swap; and lints the artifact directory against the ML Code Completeness checklist with bundled stdlib-only scripts. Outputs an artifact-readiness checklist + packaging plan. Re-verifies the venue current artifact rules live. Advisory only; never submits.Planning★ 60
- artifact_testingwin4r/MuseAI-SkillsVerify an artifact before delivering it - file deliverables (pdf, pptx, docx, xlsx, csv) and web artifacts alike. Use whenever a build is about to return a link, or a build task asks for validation, QA, or a visual check. Covers the per-kind gate scripts, render-and-look verification, and leftover-placeholder scanning.Testing★ 414
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in