Screenshot

**Judgement:** A well-designed, opinionated screenshot orchestration skill that prioritizes *the right* capture method and stable, reproducible outputs over generic “grab the screen” behavior. Strong fit for teams doing QA, visual regression, and CI debugging. **Strengths & advantages** - Covers a wide range of environments: macOS, Windows, Linux (Wayland & X11/headless), iOS Simulator, and browser-native (Playwright) capture. - Encodes solid best practices: waiting for real rendered state, fixing viewport and zoom, and choosing the smallest useful capture scope (element/region/window vs full screen). - Explicit CI focus: deterministic browser-native screenshots, fixed viewports, and good patterns for baseline vs ad-hoc captures. - Thoughtful about visual noise: cursors, carets, notifications, animations, timestamps, and random data. - Makes correct format choices (PNG by default, JPEG reserved for photographic content) and warns against lossy pipelines. **Key risks & limitations** - Depends on platform-specific tools (screencapture, grim+slurp, scrot, nircmd, Playwright, etc.); missing or misconfigured dependencies can reduce reliability or require manual setup. - Does not handle post-capture editing/annotation; users needing markup or heavy redaction must chain with other skills. - Security and privacy still rely on the user: while the skill emphasizes masking/hiding secrets, it cannot fully guarantee no sensitive data is captured if the environment isn’t prepared. - Advanced options (e.g., Playwright viewport tuning, masking, animation disabling) may have a learning curve for non-technical users. **Recommended scenarios** - Web product teams implementing or maintaining visual regression tests where viewport, theme, and state consistency are critical. - QA and support workflows that require precise, minimal, and legible screenshots as part of bug reports or investigation logs. - CI pipelines that need reliable, debuggable screenshots on failure rather than brittle manual screen-grabs of the host. - Cross-platform development shops needing consistent patterns for macOS, Linux (Wayland/X11), Windows, and iOS Simulator screenshots. **Less ideal for** - Users primarily wanting to *edit* or annotate images post-capture (should be paired with image/image-edit type skills). - Extremely constrained environments where installing platform-specific tools or Playwright is difficult or impossible.