web-analysisSKILL.md · 2.9 KB
Paste a link. Get the whole site in one summary.
Hand it a URL and it reads the site back to you: what the thing is and who it is for, how the page is put together, which colours the CSS declares against which ones actually land, and where the contrast gives out.
Two passes, kept apart on purpose. One reads the visual system, the other reads the site as a business — run them together and you get a vague impression of both.
cp -r web-analysis ~/.claude/skills/What it does
The useful part is what it refuses to guess.
It fetches; it does not browse. So the report opens by saying so — a table of everything the method could not reach: hover and focus states, anything the page renders after load, whatever sits behind a click. Naming the gap is the point. A report that quietly leaves it out reads as complete when it is not.
Colour and contrast are calculated from the declared source rather than sampled from a screenshot, and the report says which it did. The palette table keeps the two apart — what the CSS asks for in one column, what survives opacity and blending in the next. On example.com that gap is the entire finding: an opacity: 0.8 on the container is what costs the only link on the page its AAA.
The rest is structure. A skeleton of the page as a tree, the recurring wrappers named by the class that carries them, palette and type as tables, and a short list of the small things — an empty data: favicon that exists only to stop the browser asking for one, a viewport meta that is present, a lang that is declared. It comes back as Markdown, so it goes wherever the rest of your notes go.
Example reports
Three real runs, unedited. They are long — a skill this short is mostly a decision about what has to be in the answer.