Individual skill

vis-reproducibility

Use when strengthening IEEE VIS reproducibility and open-practices evidence, covering the open-materials statement, anonymized-but-runnable code and stimuli, preregistration of perceptual and user studies, provenance for datasets and rendering pipelines, claim-to-figure mapping, honest degrees of reproducibility, and consistency between what the TVCG paper says and what the supplemental archive contains.

VIS-Skills/skills/vis-reproducibility/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,405
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# VIS Reproducibility

Use this before submission and again before camera-ready. IEEE VIS's Open Practices posture and the
**Graphics Replicability Stamp** make reproducibility a visible dimension, not a courtesy: reviewers
routinely open the supplemental code, data, and video, and the TVCG camera-ready collects
open-practices disclosures. The goal is that a competent reader could rebuild your figures, rerun
your study analysis, and reach your conclusions.

## Evidence map

- Map each **figure, quantitative result, and study finding** to a **verifiable location** — a
  section, a figure generated from logged data, or a script in the supplemental archive.
- For **techniques and rendering**, give enough of the algorithm, parameters, and environment
  (including GPU/driver assumptions and tolerances) that a reader could re-implement or re-run.
Back to top