screenshotslisted

# Screenshots Skill (advanced mode) > **Version**: 2.0 (Single-file mode) | **Backend**: Resolution-agnostic, uses pure pixel coordinates (pixels) | **Focus**: Advanced reasoning and problem solving ## CRITICAL: Microscope model (not primary analysis) This skill is a **microscope, not a primary analysis tool**. It is Powerful for deep analysis, but Expensive (slow, high token usage). It Supports UI Mapper (the primary inspection tool). **Key Principles:** - **Less is More.** Use it SPARINGLY, NOT by default. - **Flat Architecture.** Analyze in a single pass; NO recursive decomposition. - **UI has no recursive structure.** Do not invent hierarchy where none exists. - **Element Count Match.** MUST match the pixel/reference image as closely as possible. - **Fail Fast.** If inspection fails after 1 retry, STOP and show the error. - **No Features.** Do not document features/behaviors; ONLY report what you can SEE. - **Debug-First.** Focus on malformed inputs, pollution, and state mismatches. - **Advanced Analysis.** Here for complex analysis, not your FIRST analysis attempt. - **Evidence Based.** Do not guess/hallucinate; base everything on observable evidence. - **Pixel-Perfect ROI.** Validate element sizes through actual screenshot regions, NOT via uamappings alone (accuracy gate). --- ## CRITICAL: Data freshness (non-negotiable) - Inventory Data MUST be < 30 seconds old. If `since_capture` > 30s, RE-CAPTURE. - Screenshots MUST be from the CURRENT session (after the last