Browser UseBrowser Skills
← Back to skills

Domain skill

gemini

Markdown synced from browser-harness domain skills.

Host
gemini
Files
1

Agent prompt

Use this skill

Copy this prompt into your coding agent to make it enable browser-harness domain skills and read this exact domain folder before automating.

Set up https://github.com/browser-use/browser-harness for me if it is not already installed. If setup is needed, read `install.md` first to install and connect it to my real browser. Then read `SKILL.md` for normal usage and always read `helpers.py` because that is where the browser-harness functions are.

Enable domain skills if they are not already enabled by setting `BH_DOMAIN_SKILLS=1` for browser-harness. Use the `gemini` domain skill from `agent-workspace/domain-skills/gemini/`. Read every markdown file for this domain before inventing an approach:
- agent-workspace/domain-skills/gemini/spark-skills.md

Use those domain-skill notes to complete my task for `gemini` in my real browser. When you open a setup, verification, or task tab, activate it so I can see the active browser tab.

Skill contents

What the agent will read

Gemini Spark skills

spark-skills.md

Source
  • 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...
  • 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...
Show full markdown

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.