Browser evidence
Use when claiming a visible, responsive, interactive, scroll-led, canvas, WebGL, or animated browser result is complete and fresh evidence is needed.From its SKILL.md
npx -y skills add twk0672005/sentence-to-site --skill browser-evidenceAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 5 stars5 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.
SKILL.md
0.9 KB, 158 tokens by cl100k_base, as published. Nobody here has run it
Browser Evidence
Match proof to the claim. A build, HTTP 200, or one hero screenshot does not prove mobile behavior, interaction, motion, or visual quality.
For ordinary visible work, inspect the running page and a key desktop state. Add mobile, primary flow, and serious console/page errors for responsive or interactive work. Add representative states, a short clip or multi-state frames, and fallback review for motion-led work.
Use the bundled scripts when executable browser proof is appropriate. Report pass, partial, or blocked exactly; a missing runtime or unsupported capability is not a successful result.
Read ../../references/evidence-and-handoff.md and ../../references/tooling.md. Use ../../templates/evidence-report.md for a reviewable result.
What ships with it: 1 file
363 B alongside SKILL.md
evals/
- evals.json363 B