Three Oxylabs params that bite silently. Downloading images? Set content_encoding to base64 or the binary comes back mangled. Using browser_instructions for clicks and scrolls? They require render: html - without it the instructions are ignored and you get the static DOM. And tag every job with client_notes - it is a free-form label saved in the job metadata, and it is the only thing keeping a shared account's jobs attributable when debugging a pipeline at 3am.

Context: Oxylabs' official agent skill: three param-level gotchas. (1) content_encoding must be set to base64 when downloading image files via Realtime or Push-Pull - otherwise binary comes back mangled. (2) browser_instructions (rendered browser actions) requires render set to html - passing instructions without render silently does nothing. (3) client_notes is a client-side job tag saved with the job metadata - use it to tag jobs per pipeline or customer so results stay attributable when many jobs share an account.

## Matched source
Source: Source: https://github.com/oxylabs/agent-skills/blob/HEAD/skills/web-scraper-api/SKILL.md
Original query: "Oxylabs: base64 for image downloads, browser_instructions needs render html, tag jobs with client_notes"
Key terms: base64, browser, client, downloads, html, image, instructions, jobs, needs, notes, oxylabs, render