What it proves
A public repo should expose the README, a runnable example, sample files, and a verification path early enough that a newcomer does not need to infer the basics.
Workflow checks
repo-onramp-check turns repo quality into visible proof instead of a vague README promise.
This is the anchor repo for the workflow-check track because it makes a normally fuzzy standard inspectable: can a stranger reach first useful success without guessing what to run or what to trust.
Why this repo carries the track
A short site-side guide before the proof layer on GitHub.
Why it is the anchor
It carries the standard for the whole track quickly: a small utility that turns repeated repo review advice into a rerunnable check.
What survives the first run
The audit output is the useful artifact. It gives you a compact report you can use before publishing a repo or reviewing someone else's first-run experience.
What the first useful success looks like
repo-onramp-check as a first useful success, not only a demo.
The first run is intentionally small: point the checker at a repo, inspect the score, and then decide whether the README, example, or verification path still needs work. That makes the next move obvious before the repo is shared more widely.
Use this before publishing a small tool, before recommending a starter repo internally, or before linking someone to a public repo as the anchor example for a broader pattern.
python3 repo_onramp_check.py .Score: 5/5
README present: yes
Quick-start guidance: yes
Runnable example: yes
Sample data or examples: yes
Tests or verification path: yesWhere it routes next
Audits whether a public repo makes first proof, visible examples, and the rerun path obvious to a newcomer.