# Send Screenshot to your agent
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
## Fast path
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
## Suggested prompts
### New install

```text
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
```
### Upgrade existing

```text
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
```
## Machine-readable fields
```json
{
  "schemaVersion": "1.0",
  "item": {
    "slug": "screenshot",
    "name": "Screenshot",
    "source": "tencent",
    "type": "skill",
    "category": "通讯协作",
    "sourceUrl": "https://clawhub.ai/ivangdavila/screenshot",
    "canonicalUrl": "https://clawhub.ai/ivangdavila/screenshot",
    "targetPlatform": "OpenClaw"
  },
  "install": {
    "downloadUrl": "/downloads/screenshot",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=screenshot",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "packageFormat": "ZIP package",
    "primaryDoc": "SKILL.md",
    "includedAssets": [
      "SKILL.md"
    ],
    "downloadMode": "redirect",
    "sourceHealth": {
      "source": "tencent",
      "slug": "screenshot",
      "status": "healthy",
      "reason": "direct_download_ok",
      "recommendedAction": "download",
      "checkedAt": "2026-05-01T05:39:26.647Z",
      "expiresAt": "2026-05-08T05:39:26.647Z",
      "httpStatus": 200,
      "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=screenshot",
      "contentType": "application/zip",
      "probeMethod": "head",
      "details": {
        "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=screenshot",
        "contentDisposition": "attachment; filename=\"screenshot-1.0.1.zip\"",
        "redirectLocation": null,
        "bodySnippet": null,
        "slug": "screenshot"
      },
      "scope": "item",
      "summary": "Item download looks usable.",
      "detail": "Yavira can redirect you to the upstream package for this item.",
      "primaryActionLabel": "Download for OpenClaw",
      "primaryActionHref": "/downloads/screenshot"
    },
    "validation": {
      "installChecklist": [
        "Use the Yavira download entry.",
        "Review SKILL.md after the package is downloaded.",
        "Confirm the extracted package contains the expected setup assets."
      ],
      "postInstallChecks": [
        "Confirm the extracted package includes the expected docs or setup files.",
        "Validate the skill or prompts are available in your target agent workspace.",
        "Capture any manual follow-up steps the agent could not complete."
      ]
    }
  },
  "links": {
    "detailUrl": "https://openagent3.xyz/skills/screenshot",
    "downloadUrl": "https://openagent3.xyz/downloads/screenshot",
    "agentUrl": "https://openagent3.xyz/skills/screenshot/agent",
    "manifestUrl": "https://openagent3.xyz/skills/screenshot/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/screenshot/agent.md"
  }
}
```
## Documentation

### When to Use

Use when the task needs a screenshot of a desktop app, browser page, simulator, region, window, or full screen, especially for debugging, QA, documentation, release notes, bug reports, visual review, or before/after comparison.

This skill is about taking the right screenshot reliably, not about editing images after the fact.

### Tool Choice

ContextBest defaultWhymacOS desktop or windowscreencaptureBuilt-in, reliable, supports silent, interactive, region, and window captureiOS Simulatorxcrun simctl io booted screenshotMore reliable than generic desktop capture for simulator outputLinux Waylandgrim + slurpX11 tools often fail or behave oddly on WaylandLinux X11 / headless CIscrot or browser-native captureWorks in minimal or virtual-display environmentsWindows desktop capturenircmd savescreenshot or Pillow ImageGrabEasier than verbose PowerShell screen APIsWeb page or web appPlaywrightBest for stable viewport, element, full-page, masked, and regression screenshotsVisual diff / screenshot testsPlaywright with fixed viewportBetter control over animations, caret, masks, and reproducibility

Default to the most native capture path first. Move to browser-native tooling when determinism, masking, element capture, or visual regression matters more than convenience.

### 1. Pick the capture path by artifact, not by habit

Desktop UI screenshots usually want OS-native tools.
Web pages and web apps usually want browser-native capture, not a desktop screenshot of the browser window.
Simulator screenshots should come from the simulator tooling when possible.
Use region, window, or element capture when the point is local; use full screen or full page only when the full context matters.

### 2. Stabilize the target before capturing

Dynamic pages should settle before capture: wait for network idle or the specific element that matters, then give fonts and transitions a brief moment to finish.
Do not take the screenshot before the real rendered state exists.
For browser capture, prefer explicit readiness over blind sleeps when possible.
If the page never truly goes idle, wait for the exact UI state you need instead of chasing perfect stillness.

### 3. Freeze viewport, scale, zoom, and theme for reproducibility

Screenshot comparisons are meaningless if viewport, zoom level, theme, or device scale changed.
For browser captures, fix the viewport before taking baselines or before/after images.
Retina and HiDPI displays can produce more pixels than expected; decide whether you want physical pixels or CSS-scale output and keep that choice consistent.
If dark/light mode matters, capture both intentionally instead of mixing them accidentally.

### 4. Capture the smallest useful scope

Element, region, or window screenshots are usually better than noisy full-screen captures.
Full-page screenshots are useful for audits and archives, but long pages become hard to read and compare.
For browser work, element screenshots or clipped regions usually produce cleaner diffs than full-page output.
If the screenshot is evidence, keep enough surrounding context that the user can understand what they are looking at.

### 5. Remove noise before you capture

Hide or avoid unstable UI when it is not the subject: cursors, carets, toasts, chat widgets, notifications, loading spinners, timestamps, and randomized content.
Mask or avoid secrets, personal data, tokens, and internal URLs before capture.
For Playwright-style browser capture, features like disabled animations, hidden carets, and masking are worth using when visual stability matters.
If the noise is the bug, keep it; otherwise remove it.

### 6. Use the right output format

PNG is the default for screenshots, UI, code, terminals, and text-heavy captures.
JPEG is for photographic content, not normal screenshots.
WebP is fine for sharing or storage when compatibility is acceptable, but do not default to it if the consumer expects plain PNG files.
Avoid recompressing screenshots through JPEG pipelines unless the user explicitly wants smaller lossy output.

### 7. Make automation and CI captures debuggable

On failures, save a screenshot immediately before retrying or moving on.
Use stable filenames for baselines and timestamps for ad hoc or batch captures.
In CI, identical viewport and deterministic state matter more than raw screenshot volume.
Headless runs should prefer browser-native screenshots over trying to screen-grab the host display.

### 8. Validate that the screenshot is actually useful

Check that the important detail is visible, legible, and not cropped away.
Verify that secrets are not still visible in tabs, sidebars, URLs, notifications, or test data.
Before/after comparisons should use the same viewport, zoom, theme, and state.
A screenshot is bad if it is technically correct but useless for the human who needs it.

### High-Value Patterns

macOS: screencapture -x out.png for silent capture, -i for interactive selection, -R x,y,w,h for a fixed region.
iOS Simulator: xcrun simctl io booted screenshot out.png
Linux Wayland: grim -g "$(slurp)" out.png
Playwright page capture: wait for the target state, then use page, element, clipped, or full-page screenshots deliberately.
Playwright stability features worth remembering: fixed viewport, disabled animations, hidden caret, masks for sensitive regions, and stable theme/media settings.

### Common Traps

Taking a browser-window screenshot when an element or page screenshot was the real need.
Capturing before fonts, data, or layout transitions finish.
Comparing screenshots with different viewport sizes or zoom levels and treating the diff as meaningful.
Using JPEG for screenshots and blurring text, edges, and code.
Letting timestamps, cursor blinks, notifications, or random data ruin visual diffs.
Forgetting that Wayland breaks familiar X11 screenshot tools.
Sharing screenshots with secrets still visible in tabs, sidebars, URLs, or test accounts.
Taking full-page captures of huge pages and ending up with unreadable evidence.

### Related Skills

Install with clawhub install <slug> if user confirms:

playwright — Browser automation, DOM interaction, and web screenshots
image — Post-capture format, cropping, compression, and export decisions
image-edit — Annotation, cleanup, masking, and targeted edits after capture
documentation — Turning screenshots into docs, guides, and release assets
video — When a flow should be recorded instead of reduced to still images

### Feedback

If useful: clawhub star screenshot
Stay updated: clawhub sync
## Trust
- Source: tencent
- Verification: Indexed source record
- Publisher: ivangdavila
- Version: 1.0.1
## Source health
- Status: healthy
- Item download looks usable.
- Yavira can redirect you to the upstream package for this item.
- Health scope: item
- Reason: direct_download_ok
- Checked at: 2026-05-01T05:39:26.647Z
- Expires at: 2026-05-08T05:39:26.647Z
- Recommended action: Download for OpenClaw
## Links
- [Detail page](https://openagent3.xyz/skills/screenshot)
- [Send to Agent page](https://openagent3.xyz/skills/screenshot/agent)
- [JSON manifest](https://openagent3.xyz/skills/screenshot/agent.json)
- [Markdown brief](https://openagent3.xyz/skills/screenshot/agent.md)
- [Download page](https://openagent3.xyz/downloads/screenshot)