Skip to content
Skills Library
Marketing & content · Tool integration

setup

/setup

Friendly first-time setup for the Google Flow plugin — checks the Claude in Chrome connection, Flow sign-in, the browser's download folder and save-dialog setting, then does a free test generation to prove everything works. Use when the user runs /google-flow:setup, just installed the plugin, asks how to set up / fix the Flow plugin, or when /google-flow:generate reports that setup is needed.

Licence
MIT
Last repository change
28.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
5
Deprecation

No signals detected. Repository changed on 28.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Friendly first-time setup for the Google Flow plugin — checks the Claude in Chrome connection, Flow sign-in, the browser's download folder and save-dialog setting, then does a free test generation to prove everything works. Use when the user runs /google-flow:setup, just installed the plugin, asks how to set up / fix the Flow plugin, or when /google-flow:generate reports that setup is needed.

Original author description

Friendly first-time setup for the Google Flow plugin — checks the Claude in Chrome connection, Flow sign-in, the browser's download folder and save-dialog setting, then does a free test generation to prove everything works. Use when the user runs /google-flow:setup, just installed the plugin, asks how to set up / fix the Flow plugin, or when /google-flow:generate reports that setup is needed.

How it works

  1. Voice
  2. Steps
Original SKILL.md headings · 59 lines, 738 words
SKILL.md preview
---
name: setup
description: Friendly first-time setup for the Google Flow plugin — checks the Claude in Chrome connection, Flow sign-in, the browser's download folder and save-dialog setting, then does a free test generation to prove everything works. Use when the user runs /google-flow:setup, just installed the plugin, asks how to set up / fix the Flow plugin, or when /google-flow:generate reports that setup is needed.
allowed-tools: Bash(${CLAUDE_PLUGIN_ROOT}/skills/generate/scripts/collect.sh *)
---

# Google Flow — first-time setup 🎬

Walk the user through getting the plugin ready, one check at a time. This is their first impression of the plugin, so make it feel easy and a little fun.

`collect.sh` below means `${CLAUDE_PLUGIN_ROOT}/skills/generate/scripts/collect.sh`. Setup state lives in `${CLAUDE_PLUGIN_DATA}`. The Flow UI map is `${CLAUDE_PLUGIN_ROOT}/skills/generate/reference/ui-map.md` and the page script is `${CLAUDE_PLUGIN_ROOT}/skills/generate/reference/page-hooks.js`.

## Voice

- Warm, upbeat, brief. Talk like a friendly studio assistant getting the set ready ("lights… camera… let's check your browser").
- One check per message. Mark progress like `✅ 1/4 Browser connected`. A few emoji at milestones are welcome; don't decorate every line.
- When something needs the user, give them **exactly** what to click or type, then wait for them to say they're done. Never make them feel they did something wrong.
- Stay plain and precise about anything involving their account, settings, or credits.
- You do the checking; the user only does the steps you can't (installing an extension, signing in, changing a browser setting). Never change browser settings yourself.

## Steps

**0. Hello.** One short message: what's about to happen (4 quick checks + a free test image, ~2 minutes) and that they'll only need to click a couple of things.

**1. Browser connection.** Load the Claude in Chrome tools in ONE ToolSearch call:
`select:mcp__claude-in-chrome__tabs_context_mcp,mcp__claude-in-chrome__tabs_create_mcp,mcp__claude-in-chrome__navigate,mcp__claude-in-chrome__computer,mcp__claude-in-chrome__find,mcp__claude-in-chrome__read_page,mcp__claude-in-chrome__javascript_tool,mcp__claude-in-chrome__browser_batch,mcp__claude-in-chrome__tabs_close_mcp`
Call `tabs_context_mcp` with `createIfEmpty: true`.
- Not connected (or the tools don't exist) → explain: install **Claude in Chrome** from https://claude.ai/chrome in a Chrome-based browser (Chrome, Brave, Edge, Arc…), sign in to the **same Claude account** as Claude Code, then fully restart the browser. Wait, then retry.

**2. Flow sign-in.** `tabs_create_mcp`, navigate to `https://flow.google.com/`, wait 3 s, screenshot.
- Project grid / **New project** button → signed in ✅.
- Google sign-in page or a welcome/terms screen → ask them to finish it in that tab (you don't type credentials or accept terms for them), then re-check.
- "Not available in your country" or similar → explain Flow isn't available for that account/region and stop kindly.

**3. Download folder.** Run `collect.sh mark`.
- Exit 3 → their browser saves to a folder that no longer exists. Get the scheme from `collect.sh browser` and send them to `<scheme>settings/downloads` to pick a real folder (e.g. Downloads). Re-run.
- Output warns the browser "asks where to save" → same page: turn off **Ask where to save each file**. Re-run.
- Otherwise ✅, and mention the folder.

**4. The save-dialog trick.** Flow normally pops a "flow.google.com wants to save" system window that you can't click, so you'd be stuck waiting on them every download. Get the scheme from `collect.sh browser` and ask them to:
1. open `<scheme>settings/content/fileSystemWrite` (Edge: search settings for **File editing** if the link doesn't open)
2. next to **Not allowed to edit files**, click **Add**, enter `https://flow.google.com`, click **Add**
3. tell you when done.
Then reload the Flow tab (navigate to `https://flow.google.com/` again) — the setting only applies after a reload.

**5. Test drive ✨** Follow the generate skill's workflow (`${CLAUDE_PLUGIN_ROOT}/skills/generate/SKILL.md`, steps 3–9) with:
- New project, Image, the default model, 1:1, x1, prompt: `a tiny cheerful robot waving hello, soft pastel studio backdrop, product photo`, out dir `./flow-output`.
- Read the credits line. If it isn't 0, tell them the cost and ask before generating (they can also skip the test).
- After clicking **Original size**, run `collect.sh collect ./flow-output "hello robot"`.
  - File arrives → 🎉 show the path.
  - Exit 4 → ask whether a save window popped up. If yes: have them click **Cancel**, double-check step 4 (exact address `https://flow.google.com`, then reload), and try the download once more. If no window and still nothing: report the script output and stop.

**6. Done.** Run `collect.sh setup-done "${CLAUDE_PLUGIN_DATA}"`. Celebrate briefly and show 2–3 starter commands:
```
/google-flow:generate image "a cozy reading nook, rainy window, warm lamp light" --count 2
/google-flow:generate video "slow push-in on a steaming cup of coffee" --aspect 9:16
/google-flow:generate video "the robot starts dancing" --start ./flow-output/<their test image>
```
Then show their credit menu: follow the `google-flow:credits` skill's steps 2–4 (reusing the open tab — do this before closing it) so they know exactly how many images and videos they can make. Remind them: Claude always asks before spending credits, and `/google-flow:credits` shows the menu again anytime.

Close the tab when you're finished.

If they want to stop partway, that's fine — don't mark setup done; tell them `/google-flow:setup` picks up from the top anytime.

Versions

RepositoryScoreLicence
This page · Jayith/claude-google-flow100MIT
HwangSlater/harness-fit100MIT
nesquikm/dev-process-toolkit100MIT
userKael/rastro100MIT
als-apg/osprey100BSD-3-Clause
dedujeong/gemba100Apache-2.0
eigenwise/eigenwise-toolshed100MIT
awrshift/agent-memory-kit100MIT
lifecycle-innovations-limited/claude-ops100MIT

Database snapshot: 13.11.2026 · package version 60debddfff8e (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90generate
    Generate images or videos in Google Flow (flow.google.com) by driving the user's signed-in Chrome-based browser through Claude in Chrome — picks image/video, model, aspect ratio and output count, attaches reference images or start/end frames, enters the prompt, waits for results…
  • 98takomi-flow
    Use when Codex needs to operate Google Flow as a reusable agent tool through safe browser automation: bootstrap/login a persistent Flow profile, smoke-check access without spending credits, prepare image or video generation request files, run guarded Flow generations, download…
  • 100chrome-health-check
    Quickly checks whether the Claude in Chrome MCP connection is working and reports the status. Use when the user says "is chrome connected?", "check chrome", "chrome status", "test chrome connection", "is the chrome extension working?", or any variation of wanting to know if…
  • 100google-ads
    Router / orchestrator for the claude-google-ads suite. Use when the user wants to do anything with Google Ads but hasn't named a specific step — "help me with Google Ads", "launch Google Ads for my store", "run google ads", or just /google-ads. Reads account-context.yaml, runs…
  • 100fix-chrome-connection
    Use when: tabs_context_mcp fails, Chrome MCP is broken, user says "fix Chrome", "reconnect Chrome", "Chrome extension not responding", or after switching Claude Desktop accounts. Diagnoses and repairs broken Claude-in-Chrome MCP connections step by step, then commits any new learnings to GitHub.
  • 90seedance2-setup
    First run for Seedance 2: check the connection, explain what it can make and what it costs, and help make a first video. Use right after installing, when the user asks how to start, or when the Seedance 2 tools are not connected.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.