Explain Interface is a user-invoked agent skill that answers how something on the web was built. Ask how the gradient on a site was made and it finds the layers behind it in paint order and says what each contributes. Ask how a whole site was built and it reports the frontend stack, tokens, type, spacing, color, motion and breakpoints.
It explains and issues no verdict. Every claim carries a tier, measured, derived or inferred, and a screenshot answer is labeled a reconstruction.
What You Get
- The layer stack behind an effect in paint order, including pseudo-elements, blur, blend and backdrop layers, with the declaration doing the work on each
- A site-level read of framework, styling approach, component primitives, tokens, type scale, spacing rhythm, radii, shadows, motion and breakpoints
- A tier on every value: measured from the page, derived by computation or inferred as intent
- For screenshots, a reconstruction with exact colors and contrast, ratios in place of pixel sizes and a list of what the image hid
- A closing recipe in words, plus what is not transferable, such as a licensed typeface or a pre-rendered shadow
Common Use Cases
- Finding out how a landing-page hero gradient or glow was layered
- Learning how a site’s reveal animation staggers its text
- Identifying a site’s framework, Tailwind version and token structure
- Reconstructing a look from a screenshot when no URL is available
What Makes It Unique
It explains the mechanism and does not dump a readout. It treats compiled output as such: three animations on one element is what a stagger helper compiles to. It also refuses to end in a code block, because anything assembled from compiled output is a lookalike tuned to a viewport and typeface you do not have.
Under The Hood
The skill is a SKILL.md with four reference files for finding effects, reading a whole system, screenshots and working without a browser. It has no scripts, but it gives the agent JavaScript snippets to run in a page through a scriptable browser, such as the chrome-devtools MCP, and shell commands for the no-browser route. That route downloads the page’s HTML and linked stylesheets with curl into a temporary directory and searches them with grep. It reads only the sites you name, treats page text as evidence and never as instructions, never submits forms or signs in, and does not edit your project.