Gemini Spark skills

Notes an AI agent reads before it works on gemini.google.com: what to open, what to call, what breaks. Written by browser-harness contributors after real runs, and kept on GitHub under the MIT license.

Run it in Browser Use Cloud Source on GitHub

Give it to your agent

Any coding agent

Start the task with this line. The Markdown version is the same notes without the page around them.

Read https://browser-use.com/skills/gemini.md, then <your task>

Browser Harness

Save the files into your workspace and turn domain skills on. The code below calls its helpers, such as http_get and js. What Browser Harness is.

d="${BH_AGENT_WORKSPACE:-$HOME/.config/browser-harness/agent-workspace}/domain-skills/gemini"
mkdir -p "$d" && cd "$d"
curl -sLO https://raw.githubusercontent.com/browser-use/browser-harness/main/agent-workspace/domain-skills/gemini/spark-skills.md
export BH_DOMAIN_SKILLS=1

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.

spark-skills.md · updated Oct 9, 2026 · 241 words

Sites change. These notes describe what worked when they were last updated, not a guarantee they still do. If something broke, the fix is a pull request to browser-harness.