Check a slide manifest and plan tiling before a pathology run
Paste your whole-slide image manifest and your tiling and model numbers. Your browser runs the pathml skill's own tools on them - manifest validator, PathML 3.0.5 tile planner and inference batch planner - with the same output as the Python, free. Nothing is uploaded. A paid run reads only the counts and plans and reviews the plan or drafts the methods and provenance.
Both examples have saved model runs for both lanes - the whole page, free.
Your recent runs
What this does, and what it does not
The pathml agent skill ships standard-library Python tools that check a computational-pathology
plan without opening a slide or importing PathML. slide_manifest.py validate checks a
manifest: pseudonymous slide and patient ids, unique slides and paths, no URLs, allowed split names,
and that no patient has slides in two splits. plan_pipeline.py reproduces PathML 3.0.5's
tile-count arithmetic and estimates the uncompressed payload for a tile size, stride, level and
pipeline. plan_inference.py estimates batch memory from numbers or a JSON model card,
without loading a checkpoint.
This page runs JavaScript ports of all three with the same JSON output and error messages, checked against the Python on thousands of fuzzed inputs (see the notice for the counts). One difference is stated plainly: a browser cannot see your files, so each slide path is checked as text and assumed to exist; the commands on the page run the real check on your machine. The page's flags, its pass over every row and the per-slide plans are its own, labelled as such. The paid lanes read only counts, plans and flags - never a slide, a file name or an identifier. PathML is research software, not a medical device: nothing here supports a diagnosis. Derived from the agent skill @k-dense-ai/pathml (k-dense-ai/scientific-agent-skills, MIT; see the notice).