BrowserOS screenshot-walkthrough
Capture step-by-step screenshots of a workflow or process for documentation, bug reports, or tutorials. Use when the user asks to document steps, create a walkthrough, or capture a process.
install
source · Clone the upstream repo
git clone https://github.com/browseros-ai/BrowserOS
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/browseros-ai/BrowserOS "$T" && mkdir -p ~/.claude/skills && cp -r "$T/packages/browseros-agent/apps/server/src/skills/defaults/screenshot-walkthrough" ~/.claude/skills/browseros-ai-browseros-screenshot-walkthrough && rm -rf "$T"
manifest:
packages/browseros-agent/apps/server/src/skills/defaults/screenshot-walkthrough/SKILL.mdsource content
Screenshot Walkthrough
When to Use
Activate when the user asks to document a workflow, create a step-by-step guide, capture a process for a bug report, or build visual documentation of a web-based procedure.
Steps
-
Clarify the workflow. Confirm with the user:
- What process to document
- Starting URL or page
- Where to save the screenshots
-
Navigate to the starting point using
.navigate_page -
For each step in the workflow: a. Take a screenshot using
with a descriptive filename:save_screenshot- Pattern:
step-{number}-{description}.png - Example:
,step-01-login-page.png
b. Note what action to take next c. Perform the action (click, fill, navigate, etc.) d. Wait for the page to settle (new content to load) e. Repeatstep-02-enter-credentials.png
- Pattern:
-
Compile the walkthrough as a markdown document:
Output Format
# Walkthrough: [Process Name] **Date:** [current date] **URL:** [starting URL] ## Step 1: [Action Description]  Navigate to [URL]. You will see [what's on screen]. ## Step 2: [Action Description]  Click on [element]. [What happens next].
- Save the walkthrough using
alongside the screenshots.filesystem_write
Tips
- Number steps with zero-padded digits (01, 02, ...) for correct file sorting.
- Include the browser URL bar in screenshots when the URL is relevant to the step.
- For error documentation, capture the error state and any console errors.
- If the process involves sensitive data, warn the user before capturing screenshots.