BROWSER USE - Browser Use Agents: give Browser Use a task and receive completed work. API V4 is current for new integrations. - Browser Infrastructure: connect your agent or automation to managed browsers through SDK, REST, or CDP. Starts at $0.02/browser-hour. - Developer tools: Open Source, Browser Harness, SDK, and MCP support the two products above. [Developer Index](https://browser-use.com/index.md) [Product Map](https://browser-use.com/llms.txt) [Full Product Context](https://browser-use.com/llms-full.txt) [Pricing](https://browser-use.com/pricing.md) [Cloud Docs](https://docs.browser-use.com/cloud/quickstart) [Open Source Docs](https://docs.browser-use.com/open-source/introduction) --- # Automate Gemini with an AI agent Source: https://browser-use.com/skills/gemini. One file from github.com/browser-use/browser-harness, MIT licensed. Written for browser-harness: code calls its helpers (http_get, js, goto_url). Sites change; these notes describe what worked when last updated. --- # Gemini Spark skills ## Editing a skill - Open `https://gemini.google.com/spark/skills`. Locate the card whose title text exactly equals the intended skill name. Read the title separately from the description. A prefix match can select both `Foo` and `Foo Bar`. Stop if the title does not identify one card. - The editor exposes `Skill description` and `Skill instructions` textboxes, `Save skill`, and `Skills, go back` controls. - The instruction editor is a rich contenteditable field. After replacing long text, compare rendered text with repeated blank lines normalized rather than comparing raw `textContent`. - After saving, wait for the `Skill saved` notice to disappear before using `Skills, go back`. Navigating away while the notice is still active can show a misleading `Leave without saving?` dialog even when the save button already says `Saved`. ## Recovering earlier content Open the completed Spark conversation that created or last edited the intended skill. Completed conversations can retain skill confirmation cards. Find `remy-confirmation-card` elements whose `data-test-id="header"` text exactly equals the skill name. Inspect the matching `data-test-id="body"` content. Use conversation order and displayed timestamps to identify the last confirmed version before the unwanted edit. If the history does not establish that version, ask the user which content to restore. Reopen the intended skill. Replace its description and instructions with the recovered content. Save the skill. Wait for the save notice to disappear. Always verify the restored description and instructions by reopening the skill after the final save.