Browser evidence
One sentence in, a verified website out. Agent skills that close the gap between vibe coding and software engineering - so people with no coding background can build a website that holds up.
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.
2 things to look at
- 19 days oldThe repository was created 19 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 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.
What its author says it does
Copied from the file, not written here
Use when claiming a visible, responsive, interactive, scroll-led, canvas, WebGL, or animated browser result is complete and fresh evidence is needed.
SKILL.md
0.9 KB, 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.