framework_eng/skills/tool-usage/browser-ui/screenshot/SKILL.md
Use when the user explicitly asks for a desktop or system screenshot (full screen, specific app or window, or a pixel region), or when tool-specific capture capabilities are unavailable and an OS-level capture is needed.
npx skillsauth add steelmorgan/1c-agent-based-dev-framework screenshotInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Save-location rules:
Prefer tool-specific captures (Figma MCP, Playwright, agent-browser) when available. Use this skill for explicit requests, whole-system desktop captures, or when tool-specific capture cannot get what you need.
Run once before window/app capture. Combine preflight + capture to reduce sandbox prompts:
bash <path-to-skill>/scripts/ensure_macos_permissions.sh && \
python3 <path-to-skill>/scripts/take_screenshot.py --app "<App>" --mode temp
python3 <path-to-skill>/scripts/take_screenshot.py [OPTIONS]
| Option | Example | Note |
|--------|---------|------|
| (none) | | OS default location |
| --mode temp | | Codex visual check |
| --path <path> | --path output/screen.png | Explicit location |
| --app "<Name>" | --app "Codex" | macOS only, substring match |
| --app "<Name>" --window-name "<Title>" | | macOS only |
| --list-windows --app "<Name>" | | macOS only, discover window ids |
| --region x,y,w,h | --region 100,200,800,600 | |
| --active-window | | Frontmost window |
| --window-id <id> | --window-id 12345 | |
The script prints one path per capture. Multiple windows/displays produce multiple paths with -w<id> or -d<display> suffixes.
Priority: scrot → gnome-screenshot → ImageMagick import → ffmpeg (x11grab). For X11 virtual displays, ffmpeg is often the most practical option in containers:
ffmpeg -y -f x11grab -video_size 1920x1080 -i :99 -frames:v 1 /tmp/screen.png
Display dimensions: DISPLAY=:99 xdpyinfo | grep dimensions
--app, --window-name, --list-windows are macOS-only. On Linux use --active-window or --window-id.
powershell -ExecutionPolicy Bypass -File <path-to-skill>/scripts/take_screenshot.ps1 [OPTIONS]
| Option | Example |
|--------|---------|
| (none) | Default location |
| -Mode temp | Codex visual check |
| -Path "<path>" | Explicit |
| -Region x,y,w,h | Pixel region |
| -ActiveWindow | Ask user to focus first |
| -WindowHandle <id> | Specific window |
screencapture -x output/screen.png # full screen
screencapture -x -R100,200,800,600 output/region.png # region
screencapture -x -l12345 output/window.png # window id
scrot output/screen.png # full
scrot -a 100,200,800,600 output/region.png # region
scrot -u output/window.png # active window
import -window root output/screen.png # ImageMagick full
ffmpeg -y -f x11grab -video_size 800x600 -i :99+100,200 -frames:v 1 output/region.png
ModuleCache) → rerun with escalated permissions--list-windows --app "Name" → retry with --window-idcommand -v scrot, command -v importtools
Diagnostics for Vanessa Automation runs. Use when a feature scenario failed, artifacts were not created, or you need to classify a failure after launch.
tools
Creating and refining Vanessa Automation feature scenarios based on real project requirements. Use when you need to write or update a scenario test, not just run it.
tools
--- name: v8-session-manager description: Use when working with the 1С session manager (v8-session-manager) - launch, configuration, connecting 1С clients, reading session_list, calling proxied MCP-tools from 1С extensions, diagnostics. Triggers: mention of `v8-session-manager`, `session_list`, 1С extension MCP showcase, error “no active sessions” / “session_id required”, connecting a client to the manager via `mcpMode=ws`. provides_capabilities: # Built-in manager tools — always available whi
tools
Use when Codex needs to manage v8-runner on local 1C projects through the CLI: configure v8project.yaml, initialize infobases or EDT workspaces, build sources from Designer or EDT, run syntax checks and tests, dump infobase changes, convert source formats, load or export artifacts, launch 1C clients, or choose safe 1C automation command sequences.