{"id":93248,"plugin_id":"plugin_asdk_app_6acf97ef6e488191938fbff985dd5d41","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-12T19:35:08.690Z","digest":"69edb955c9a4f36f01e63261e8ae1fb535b700947e63de6912f4bc3c7384592a","against":null,"payload":{"description":"Summarise how a webpage came through against its Figma design, from a Uiprobe probe. Use when the user asks what's different between a design and a page, wants a design QA summary, or wants to share a probe's findings with a designer, developer or PM. Reads existing probes only and never starts a run.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":108}],"name":"design-qa-summary","skill_md_contents":"---\nname: design-qa-summary\ndescription: Summarise how a webpage came through against its Figma design, from a Uiprobe probe. Use when the user asks what's different between a design and a page, wants a design QA summary, or wants to share a probe's findings with a designer, developer or PM. Reads existing probes only and never starts a run.\n---\n\n# Summarise a probe's findings\n\nThe Uiprobe MCP server's instructions explain each tool and how to read a finding's evidence. Follow them. This skill turns a probe's findings into a summary a person can read and share.\n\nIt only reads. Don't call `run_probe` or `rerun_probe` unless the user asks for a new run.\n\n## Steps\n\n1. **Find the probe.** If the user gave a probe or viewer URL, use it. Otherwise call `list_probes`, with `nameFilter` when the user named the page or design. If more than one probe fits, ask which one.\n2. **Get all findings.** Call `get_probe` and page through with `nextOffset` until you have them all. If the latest run is still `PENDING` or `RUNNING`, say so and offer to wait.\n3. **Sort them into sections:**\n   - **Properties**, grouped by what differs: text and content, typography, colour and style, size\n   - **Spacing**, including layout shifts\n   - **Unverified**, kept apart from the rest\n4. **Pick a few to show.** Choose up to five findings that are easy to see on the page: grouped findings that cover many elements, and large differences in size, colour or typography. Call `get_finding_images` for them.\n5. **Write the summary** in the format below.\n\n## Format\n\n- One line on top: the probe's title (from `list_probes`) and the viewer URL.\n- One short paragraph on what came through as designed.\n- Per section, one bullet per finding or group: what differs, the design value and the page value, and the `findingUrl`. Put a group on one line and say how many elements it covers.\n- The images from step 4, each under its bullet.\n- Unverified findings last, as elements Uiprobe couldn't map yet. Don't present them as differences.\n- If `get_probe` reports findings hidden by the probe's filters or dismissed, say how many and offer to include them.\n\nKeep it short enough to paste into a chat. Offer a longer version if the user wants every finding.\n\n## Don't\n\n- Rank findings by importance or severity. Uiprobe reports differences; the user decides what matters.\n- Explain why a difference exists. You can't see the code or the design process behind it.\n- Compare the number of findings with an earlier run.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}