在以下情况下，跳过 WebSearch/WebFetch 阶段，直接进行 Chrome 浏览：

• 目标平台需要登录——Reddit、LinkedIn、X/Twitter 和其他社交平台通常将内容置于登录墙之后。如果用户的 Chrome 会话已登录，则直接使用浏览器。
• 用户指定了一个有明显搜索需求的平台——例如，“查找关于 X 的 Reddit 帖子”或“截取关于 Y 的推文截图”。直接进入 Chrome 中的平台搜索。
• WebFetch 返回被阻止/不完整的内容——一些网站会积极阻止非浏览器请求。如果收到 403、验证码页面或内容被剥离，请切换到 Chrome。

在这些情况下，Chrome 浏览取代了 WebSearch——导航到平台的搜索页面，浏览结果，并在决定截图内容之前进行视觉评估。

页面选择策略

正确的页面取决于文章的上下文以及主题的新近度/知名度：

注意：此表格列出了常见的主题类型，但并非详尽无遗。对任何主题类型应用相同的研究优先策略——为当前主题找到最具权威性和视觉简洁的源页面。

什么是好的截图来源

核心原则：少即是多。专注于内容，而非界面。

一个好的截图来源包含一个聚焦的、自包含的信息片段——一段文字、一个关键引用、一个数据表格、一个图表。它不应该是一个充满按钮、导航、侧边栏和交互元素的繁忙页面。

• 首选：带有清晰标题和 1-2 段文字的博客文章段落。单个图表或示意图。带有名称和描述的模型卡片标题。引用或关键发现。
• 避免：带有行动号召和导航的完整落地页。包含多个面板的仪表板视图。以 UI 控件（按钮、下拉菜单、表单）而非可读内容为主的页面。
• 官方博客文章是理想选择：它们有主图、醒目的标题和专为分享设计的简洁描述
• 产品落地页可能有效，但前提是你只裁剪到主图部分——忽略其余部分
• HuggingFace 模型卡片对于开源模型是可靠的：布局一致，模型名称 + 描述始终在顶部
• API 文档是可接受的备选方案：显示产品名称和关键规格

经验法则：如果你计划捕获的区域包含的交互式 UI 元素（按钮、链接、导航项）多于可读文本内容，那么这是一个糟糕的裁剪。找一个内容更丰富的区域，或者完全选择另一个页面。

飞行前 URL 验证

在浏览器中打开之前，使用 WebFetch（轻量级 HEAD/GET）验证 URL，以避免在 404 或重定向上浪费时间：

WebFetch: <候选-url>
→ 检查状态码、标题和内容片段
→ 如果是 404 或重定向到无关页面，尝试下一个候选

区域选择策略

思考文章读者需要在此截图中看到什么：

截图应该让读者想到“啊，这就是这个模型/产品”——而不是“我在看什么？”

步骤 1：导航到目标页面

始终从列出标签页开始

agent-browser --auto-connect tab list

检查页面是否已打开。重用现有标签页——它们具有登录会话和正确的状态。

按输入类型导航

平台特定搜索 URL

等待页面加载

导航后，等待内容稳定：

agent-browser --auto-connect wait --load networkidle

注意：某些网站（Reddit、X、LinkedIn）永远不会达到 networkidle。如果 open 命令的输出中已经显示了页面标题，则跳过等待。使用 wait 2000 作为安全的替代方案。

步骤 2：定位目标区域

这是关键步骤。目标是找到一个CSS 选择器，它能精确地包裹要捕获的内容。

主要方法：DOM 选择器发现

1. 拍摄带注释的截图以了解页面布局：

   agent-browser --auto-connect screenshot --annotate

2. 拍摄快照以查看页面的可访问性树：

   agent-browser --auto-connect snapshot -i

3. 识别目标容器元素。寻找：

 * 语义化 HTML 容器：`<article>`、`<main>`、`<section>`

 * 平台特定组件（见平台选择器）
 * 数据属性：`[data-testid="..."]`、`[data-id="..."]`

4. 使用get box验证以确认元素具有合理的边界框：

     agent-browser --auto-connect get box "<selector>"
     

这将返回 { x, y, width, height }。进行合理性检查：

 * 宽度应 > 100px 且 < 视口宽度
 * 高度应 > 50px
 * 如果边界框是整个页面，则选择器太宽泛——需要细化

5. 如果选择器难以找到，使用 eval 探索 DOM：

     agent-browser --auto-connect eval "document.querySelector('article')?.getBoundingClientRect()"
     

平台选择器

流行平台的常见容器选择器：

这些选择器可能会随时间变化。使用前务必用 get box 验证。

多个匹配元素

如果选择器匹配多个元素（例如，时间线上的多条推文），请缩小范围：

# 计算匹配数
agent-browser --auto-connect get count "article[data-testid='tweet']"

# 使用 nth-child 或 :first-of-type，或更具体的选择器
# 或者使用 eval 通过文本内容找到正确的一个：
agent-browser --auto-connect eval --stdin <<'EOF'
const posts = document.querySelectorAll('article[data-testid="tweet"]');
for (let i = 0; i < posts.length; i++) {
  const text = posts[i].textContent.substring(0, 80);
  console.log(i, text);
}
EOF

然后使用 :nth-of-type(N) 或唯一的父选择器来定位特定的一个。

步骤 3：捕获聚焦截图

方法 A：滚动 + 视口截图（适用于视口大小的目标）

当目标元素适合视口大小时最佳。

# 将目标滚动到视图中
agent-browser --auto-connect scrollintoview "<selector>"
agent-browser --auto-connect wait 500

# 拍摄视口截图
agent-browser --auto-connect screenshot /tmp/browser-screenshot-raw.png

然后使用边界框进行裁剪（见裁剪部分）。

方法 B：整页截图 + 裁剪（适用于任何大小的目标）

当目标可能大于视口或需要精确裁剪时最佳。

# 拍摄整页截图
agent-browser --auto-connect screenshot --full /tmp/browser-screenshot-full.png

# 获取目标元素的边界框
agent-browser --auto-connect get box "<selector>"
# 输出：{ x: 200, y: 450, width: 680, height: 520 }

然后裁剪（见裁剪部分）。

裁剪

使用 ImageMagick（IMv7 上是 magick，convert 已弃用）将截图裁剪到目标区域。添加内边距以获得视觉呼吸空间。

Retina 显示屏处理

关键：在 macOS Retina 显示屏上，截图以 2 倍分辨率捕获。1728x940 的视口会产生 3456x1880 的图像。你必须考虑到这一点：

1. 检测缩放因子：比较视口大小与实际图像尺寸：

   检查实际图像尺寸

   magick identify /tmp/screenshot.png

   → 3456x1880 表示在 1728x940 视口上为 2 倍缩放

2. 在裁剪之前，将 get box 坐标乘以缩放因子：

   get box 返回视口坐标：{ x: 200, y: 450, width: 680, height: 520 }

   对于 2 倍 Retina，实际图像坐标为：

   SCALE=2 X=$((200 * SCALE)) Y=$((450 * SCALE)) W=$((680 * SCALE)) H=$((520 * SCALE)) PADDING=$((16 * SCALE))

裁剪命令

magick /tmp/browser-screenshot-full.png \
  -crop $((W + PADDING*2))x$((H + PADDING*2))+$((X - PADDING))+$((Y - PADDING)) \
  +repage \
  <输出路径>.png

重要：get box 返回浮点数值。在传递给 ImageMagick 之前将它们四舍五入为整数。

内边距：使用 12–20px（视口 px）。如果目标有清晰的视觉边界（卡片、带边框的框），则增加到约 30px。如果用户想要紧密裁剪，则使用 0。

输出路径

• 如果用户指定了输出路径，则使用该路径
• 否则，保存到当前目录的描述性名称，例如 reddit-post-screenshot.png、tweet-screenshot.png

步骤 4：验证结果

裁剪后，读取输出图像以验证其捕获了正确的内容：

# 使用 Read 工具视觉检查裁剪后的截图

如果裁剪错误（遗漏内容、过多空白、错误元素），请调整选择器或边界框并重试。

备用方案：视觉高亮确认

当基于 DOM 的定位不确定时——选择器可能错误、存在多个候选、或目标不明确——在裁剪之前使用JS 注入高亮进行视觉确认。

工作原理

1. 在候选元素上注入高亮边框：

   agent-browser --auto-connect eval --stdin <<'EOF' (function() { const el = document.querySelector('<selector>'); if (!el) { console.log('NOT_FOUND'); return; } el.style.outline = '4px solid red'; el.style.outlineOffset = '2px'; el.scrollIntoView({ block: 'center' }); })(); EOF

2. 拍摄截图并进行视觉检查：

   agent-browser --auto-connect screenshot /tmp/highlight-check.png

读取截图以检查红色边框是否包围了正确的内容。

1. 如果正确，移除高亮并继续裁剪：

   agent-browser --auto-connect eval "document.querySelector('<selector>').style.outline = ''; document.querySelector('<selector>').style.outlineOffset = '';"

2. 如果错误，尝试下一个候选或优化选择器，重新高亮，并重新检查。

何时使用此备用方案

• 页面具有复杂/嵌套的组件，你不确定哪个容器是正确的
• 存在多个相似元素，你需要选择正确的一个
• 用户的描述模糊（“页面中间的那个图表”）
• get box 结果看起来可疑（太大、太小、零尺寸）

页面准备：捕获前清理

在拍摄最终截图之前，清理页面以获得更好的结果：

# 关闭 Cookie 横幅、弹窗、覆盖层
agent-browser --auto-connect eval --stdin <<'EOF'
(function() {
  // 常见的 Cookie/弹窗选择器
  const selectors = [
    '[class*="cookie"] button',
    '[class*="consent"] button',
    '[class*="banner"] [class*="close"]',
    '[class*="modal"] [class*="close"]',
    '[class*="popup"] [class*="close"]',
    '[aria-label="Close"]',
    '[data-testid="close"]'
  ];
  selectors.forEach(sel => {
    document.querySelectorAll(sel).forEach(el => {
      if (el.offsetParent !== null) el.click();
    });
  });

  // 隐藏覆盖内容的固定/粘性元素（导航栏、横幅）
  document.querySelectorAll('*').forEach(el => {
    const style = getComputedStyle(el);
    if ((style.position === 'fixed' || style.position === 'sticky') && el.tagName !== 'HTML' && el.tagName !== 'BODY') {
      el.style.display = 'none';
    }
  });
})();
EOF

谨慎使用：隐藏固定元素可能会移除重要上下文。仅当覆盖层明显遮挡目标区域时才运行此操作。

无法关闭的 Cookie 横幅

一些 Cookie 同意横幅（例如 Jina AI 的 Usercentrics）位于 Shadow DOM 或 iframe 中，无法通过 JS click() 或 remove() 关闭。不要在多次 JS 尝试上浪费时间。而是：

1. 裁剪掉它——如果横幅在顶部或底部，只需调整裁剪区域以排除它。这是最快、最可靠的方法。
2. 滚动过去——在捕获之前将目标内容滚动到远离横幅区域的位置。

视口尺寸设置

为了一致、高质量的截图，请在捕获前设置视口：

# 标准桌面视口
agent-browser --auto-connect set viewport 1280 800

# 更宽用于仪表板/数据密集型页面
agent-browser --auto-connect set viewport 1440 900

# 更窄用于类似移动端的内容（社交媒体帖子）
agent-browser --auto-connect set viewport 800 600

选择一个能使目标内容清晰呈现的视口宽度——不要太拥挤，也不要太拉伸。

完整示例：截取 Reddit 帖子截图

用户：“截取 r/programming 上热门帖子的截图”

# 1. 列出已有标签页
agent-browser --auto-connect tab list

# 2. 导航到子版块
agent-browser --auto-connect open https://www.reddit.com/r/programming/
agent-browser --auto-connect wait 2000

# 3. 找到第一个帖子容器
agent-browser --auto-connect eval "document.querySelector('shreddit-post')?.getBoundingClientRect()"

# 4. 将其滚动到视图中
agent-browser --auto-connect scrollintoview "shreddit-post"
agent-browser --auto-connect wait 500

# 5. 获取边界框
agent-browser --auto-connect get box "shreddit-post"
# → { x: 312, y: 80, width: 656, height: 420 }

# 6. 拍摄整页截图
agent-browser --auto-connect screenshot --full /tmp/reddit-raw.png

# 7. 带内边距裁剪
convert /tmp/reddit-raw.png \
  -crop 688x452+296+64 +repage \
  reddit-post-screenshot.png

# 8. 通过读取输出图像验证

关键命令快速参考

故障排除

get box 返回 null 或零尺寸

• 选择器不匹配任何元素。使用 get count "<selector>" 验证。
• 元素可能被隐藏或尚未渲染。尝试 wait 2000 并重试。

裁剪后的图像是空白或错误区域

• 整页截图的坐标可能与视口坐标不同。将 screenshot --full 与 get box 一起使用（它们使用相同的坐标系）。
• 检查页面是否有水平滚动——get box 的 x 值可能有偏移。

目标元素在 iframe 内部

• get box 和 snapshot -i 无法看到 iframe 内部。

• 使用 eval 访问 iframe 内容：

  agent-browser --auto-connect eval "document.querySelector('iframe').contentDocument.querySelector('<sel>').getBoundingClientRect()"
  

注意：仅适用于同源 iframe。

open 成功但页面内容错误

• 浏览器可能切换到了不同的标签页（例如，弹窗或重定向打开了新标签页）。导航后务必验证：

  agent-browser --auto-connect eval "document.location.href"
  

• 如果 URL 错误，使用 tab list 找到正确的标签页，并使用 tab goto <N> 切换。

截图命令因字体超时

• 某些页面（例如 Google 开发者文档）在 document.fonts.ready 上挂起。首先强制解析它：

  agent-browser --auto-connect eval "document.fonts.ready.then(() => 'ok')"
  

然后重试截图。

页面有懒加载内容

• 在拍摄截图前向下滚动以触发加载：

  agent-browser --auto-connect scroll down 1000
  agent-browser --auto-connect wait 1500
  agent-browser --auto-connect scroll up 1000
  

每周安装次数

130

仓库

zc277584121/mar…g-skills

首次出现

10 天前

安全审计

Gen Agent Trust HubPassSocketPassSnykWarn

安装于

gemini-cli130

amp130

cline130

github-copilot130

codex130

kimi-cli130

This saves significant time — most candidate pages won't be worth screenshotting, and you can eliminate them without the overhead of browser navigation.

When to Use Browser-First Instead

Skip the WebSearch/WebFetch phase and go directly to Chrome browsing when:

• The target platform requires login — Reddit, LinkedIn, X/Twitter, and other social platforms often gate content behind login walls. If the user's Chrome session is already logged in, use the browser directly.
• The user specifies a platform with a clear search need — e.g., "find a Reddit post about X" or "screenshot a tweet about Y". Go straight to the platform's search in Chrome.
• WebFetch returns blocked/incomplete content — some sites aggressively block non-browser requests. If you get a 403, a CAPTCHA page, or stripped content, switch to Chrome.

In these cases, Chrome browsing replaces WebSearch — navigate to the platform's search page, browse results, and evaluate pages visually before deciding what to screenshot.

Page Selection Strategy

The right page depends on the context of the article and how recent/notable the subject is:

Note : This table lists common subject types but is not exhaustive. Apply the same research-first strategy to any subject type — find the most authoritative and visually clean source page for the topic at hand.

What Makes a Good Screenshot Source

Core principle: Less is more. Focus on content, not chrome.

A good screenshot source contains a focused, self-contained piece of information — a paragraph of text, a key quote, a data table, a diagram. It should NOT be a busy page full of buttons, navigation, sidebars, and interactive elements.

• Prefer : A section of a blog post with a clear heading and 1-2 paragraphs of text. A single chart or diagram. A model card header with name and description. A quote or key finding.
• Avoid : Full landing pages with CTAs and navigation. Dashboard views with multiple panels. Pages dominated by UI controls (buttons, dropdowns, forms) rather than readable content.
• Official blog posts are ideal: they have hero images, prominent titles, and concise descriptions designed for sharing
• Product landing pages can work but only if you crop to the hero section — ignore the rest
• HuggingFace model cards are reliable for open-source models: consistent layout, model name + description always at top
• API docs are acceptable fallback: show the product name and key specs

Rule of thumb : If the region you plan to capture contains more interactive UI elements (buttons, links, nav items) than readable text content, it's a bad crop. Find a more content-rich region, or pick a different page entirely.

Pre-Flight URL Validation

Before opening in the browser, validate URLs with WebFetch (lightweight HEAD/GET) to avoid wasting time on 404s or redirects:

WebFetch: <candidate-url>
→ Check status code, title, and content snippet
→ If 404 or redirect to unrelated page, try next candidate

Region Selection Strategy

Think about what the article reader needs to see in this screenshot:

The screenshot should make the reader think "ah, that's what this model/product is" — not "what am I looking at?"

Step 1: Navigate to the Target Page

Always Start by Listing Tabs

agent-browser --auto-connect tab list

Check if the page is already open. Reuse existing tabs — they have login sessions and correct state.

Navigation by Input Type

Platform-Specific Search URLs

Wait for Page Load

After navigation, wait for content to settle:

agent-browser --auto-connect wait --load networkidle

Note : Some sites (Reddit, X, LinkedIn) never reach networkidle. If open already shows the page title in its output, skip the wait. Use wait 2000 as a safe alternative.

Step 2: Locate the Target Region

This is the critical step. The goal is to find a CSS selector that precisely wraps the content to capture.

Primary Method: DOM Selector Discovery

1. Take an annotated screenshot to understand the page layout:

   agent-browser --auto-connect screenshot --annotate
   

2. Take a snapshot to see the page's accessibility tree:

   agent-browser --auto-connect snapshot -i
   

3. Identify the target container element. Look for:

   • Semantic HTML containers: <article>, <main>, <section>
   • Platform-specific components (see Platform Selectors)
   • Data attributes: [data-testid="..."], [data-id="..."]

4. Verify withget box to confirm the element has a reasonable bounding box:

   agent-browser --auto-connect get box "<selector>"
   

This returns { x, y, width, height }. Sanity-check:

 * Width should be > 100px and < viewport width
 * Height should be > 50px
 * If the box is the entire page, the selector is too broad — refine it

5. If the selector is hard to find , use eval to explore the DOM:

     agent-browser --auto-connect eval "document.querySelector('article')?.getBoundingClientRect()"
     

Platform Selectors

Common container selectors for popular platforms:

These selectors may change over time. Always verify with get box before using.

Multiple Matching Elements

If the selector matches multiple elements (e.g., multiple tweets on a timeline), narrow it down:

# Count matches
agent-browser --auto-connect get count "article[data-testid='tweet']"

# Use nth-child or :first-of-type, or a more specific selector
# Or use eval to find the right one by text content:
agent-browser --auto-connect eval --stdin <<'EOF'
const posts = document.querySelectorAll('article[data-testid="tweet"]');
for (let i = 0; i < posts.length; i++) {
  const text = posts[i].textContent.substring(0, 80);
  console.log(i, text);
}
EOF

Then target a specific one using :nth-of-type(N) or a unique parent selector.

Step 3: Capture the Focused Screenshot

Method A: Scroll + Viewport Screenshot (Preferred for Viewport-Sized Targets)

Best when the target element fits within the viewport.

# Scroll the target into view
agent-browser --auto-connect scrollintoview "<selector>"
agent-browser --auto-connect wait 500

# Take viewport screenshot
agent-browser --auto-connect screenshot /tmp/browser-screenshot-raw.png

Then crop using the bounding box (see Cropping).

Method B: Full-Page Screenshot + Crop (For Any Size Target)

Best when the target might be larger than the viewport or when precise cropping is needed.

# Take full-page screenshot
agent-browser --auto-connect screenshot --full /tmp/browser-screenshot-full.png

# Get the target element's bounding box
agent-browser --auto-connect get box "<selector>"
# Output: { x: 200, y: 450, width: 680, height: 520 }

Then crop (see Cropping).

Cropping

Use ImageMagick (magick on IMv7, convert is deprecated) to crop the screenshot to the target region. Add padding for visual breathing room.

Retina Display Handling

Critical : On macOS Retina displays, screenshots are captured at 2x resolution. A 1728x940 viewport produces a 3456x1880 image. You MUST account for this:

1. Detect the scale factor : Compare viewport size vs actual image dimensions:

   # Check actual image dimensions
   magick identify /tmp/screenshot.png
   # → 3456x1880 means 2x scale on a 1728x940 viewport
   

2. Multiplyget box coordinates by the scale factor before cropping:

   # get box returns viewport coordinates: { x: 200, y: 450, width: 680, height: 520 }
   # For 2x Retina, actual image coordinates are:
   SCALE=2
   X=$((200 * SCALE))
   Y=$((450 * SCALE))
   W=$((680 * SCALE))
   H=$((520 * SCALE))
   PADDING=$((16 * SCALE))
   

Crop Command

magick /tmp/browser-screenshot-full.png \
  -crop $((W + PADDING*2))x$((H + PADDING*2))+$((X - PADDING))+$((Y - PADDING)) \
  +repage \
  <output-path>.png

Important : get box returns floating-point values. Round them to integers before passing to ImageMagick.

Padding : Use 12–20px (viewport px). Increase to ~30px if the target has a distinct visual boundary (card, bordered box). Use 0 if the user wants a tight crop.

Output Path

• If the user specifies an output path, use that
• Otherwise, save to a descriptive name in the current directory, e.g., reddit-post-screenshot.png, tweet-screenshot.png

Step 4: Verify the Result

After cropping, read the output image to verify it captured the right content:

# Use the Read tool to visually inspect the cropped screenshot

If the crop is wrong (missed content, too much whitespace, wrong element), adjust the selector or bounding box and retry.

Fallback: Visual Highlight Confirmation

When DOM-based location is uncertain — the selector might be wrong, multiple candidates exist, or the target is ambiguous — use JS-injected highlighting to visually confirm before cropping.

How It Works

1. Inject a highlight border on the candidate element:

   agent-browser --auto-connect eval --stdin <<'EOF'
   (function() {
     const el = document.querySelector('<selector>');
     if (!el) { console.log('NOT_FOUND'); return; }
     el.style.outline = '4px solid red';
     el.style.outlineOffset = '2px';
     el.scrollIntoView({ block: 'center' });
   })();
   EOF
   

2. Take a screenshot and visually inspect:

   agent-browser --auto-connect screenshot /tmp/highlight-check.png
   

Read the screenshot to check if the red border surrounds the correct content.

1. If correct , remove the highlight and proceed with cropping:

   agent-browser --auto-connect eval "document.querySelector('<selector>').style.outline = ''; document.querySelector('<selector>').style.outlineOffset = '';"
   

2. If wrong , try the next candidate or refine the selector, re-highlight, and re-check.

When to Use This Fallback

• The page has complex/nested components and you're not sure which container is right
• Multiple similar elements exist and you need to pick the correct one
• The user's description is vague ("that chart in the middle of the page")
• The get box result looks suspicious (too large, too small, zero-sized)

Page Preparation: Clean Up Before Capture

Before taking the final screenshot, clean up the page for a better result:

# Dismiss cookie banners, popups, overlays
agent-browser --auto-connect eval --stdin <<'EOF'
(function() {
  // Common cookie/popup selectors
  const selectors = [
    '[class*="cookie"] button',
    '[class*="consent"] button',
    '[class*="banner"] [class*="close"]',
    '[class*="modal"] [class*="close"]',
    '[class*="popup"] [class*="close"]',
    '[aria-label="Close"]',
    '[data-testid="close"]'
  ];
  selectors.forEach(sel => {
    document.querySelectorAll(sel).forEach(el => {
      if (el.offsetParent !== null) el.click();
    });
  });

  // Hide fixed/sticky elements that overlay content (nav bars, banners)
  document.querySelectorAll('*').forEach(el => {
    const style = getComputedStyle(el);
    if ((style.position === 'fixed' || style.position === 'sticky') && el.tagName !== 'HTML' && el.tagName !== 'BODY') {
      el.style.display = 'none';
    }
  });
})();
EOF

Use with caution : Hiding fixed elements might remove important context. Only run this when overlays visibly obstruct the target region.

Cookie Banners That Won't Dismiss

Some cookie consent banners (e.g., Jina AI's Usercentrics) live in shadow DOM or iframes and cannot be dismissed via JS click() or remove(). Don't waste time with multiple JS attempts. Instead:

1. Crop it out — if the banner is at the top or bottom, simply adjust the crop region to exclude it. This is the fastest and most reliable approach.
2. Scroll past it — scroll the target content away from the banner area before capturing.

Viewport Sizing

For consistent, high-quality screenshots, set the viewport before capturing:

# Standard desktop viewport
agent-browser --auto-connect set viewport 1280 800

# Wider for dashboard/data-heavy pages
agent-browser --auto-connect set viewport 1440 900

# Narrower for mobile-like content (social media posts)
agent-browser --auto-connect set viewport 800 600

Choose a viewport width that makes the target content render cleanly — not too cramped, not too stretched.

Complete Example: Screenshot a Reddit Post

User: "Screenshot the top post on r/programming"

# 1. List existing tabs
agent-browser --auto-connect tab list

# 2. Navigate to subreddit
agent-browser --auto-connect open https://www.reddit.com/r/programming/
agent-browser --auto-connect wait 2000

# 3. Find the first post container
agent-browser --auto-connect eval "document.querySelector('shreddit-post')?.getBoundingClientRect()"

# 4. Scroll it into view
agent-browser --auto-connect scrollintoview "shreddit-post"
agent-browser --auto-connect wait 500

# 5. Get bounding box
agent-browser --auto-connect get box "shreddit-post"
# → { x: 312, y: 80, width: 656, height: 420 }

# 6. Take full-page screenshot
agent-browser --auto-connect screenshot --full /tmp/reddit-raw.png

# 7. Crop with padding
convert /tmp/reddit-raw.png \
  -crop 688x452+296+64 +repage \
  reddit-post-screenshot.png

# 8. Verify by reading the output image

Key Commands Quick Reference

Troubleshooting

get box returns null or zero-sized

• The selector doesn't match any element. Use get count "<selector>" to verify.
• The element may be hidden or not yet rendered. Try wait 2000 and retry.

Cropped image is blank or wrong area

• The full-page screenshot coordinates may differ from viewport coordinates. Use screenshot --full with get box (they use the same coordinate system).
• Check if the page has horizontal scroll — get box x values may be offset.

Target element is inside an iframe

• get box and snapshot -i cannot see inside iframes.

• Use eval to access iframe content:

  agent-browser --auto-connect eval "document.querySelector('iframe').contentDocument.querySelector('<sel>').getBoundingClientRect()"
  

Note: Only works for same-origin iframes.

open succeeded but page content is wrong

• The browser may have switched to a different tab (e.g., a popup or redirect opened a new tab). Always verify after navigation:

  agent-browser --auto-connect eval "document.location.href"
  

• If the URL is wrong, use tab list to find the correct tab and tab goto <N> to switch.

Screenshot command times out on fonts

• Some pages (e.g., Google developer docs) hang on document.fonts.ready. Force-resolve it first:

  agent-browser --auto-connect eval "document.fonts.ready.then(() => 'ok')"
  

Then retry the screenshot.

Page has lazy-loaded content

• Scroll down to trigger loading before taking the screenshot:

  agent-browser --auto-connect scroll down 1000
  agent-browser --auto-connect wait 1500
  agent-browser --auto-connect scroll up 1000
  

Weekly Installs

130

Repository

zc277584121/mar…g-skills

First Seen

10 days ago

Security Audits

Gen Agent Trust HubPassSocketPassSnykWarn

Installed on

gemini-cli130

amp130

cline130

github-copilot130

codex130

kimi-cli130