gen-ai-local-files

# Local Files → Hosted URL Picsart's MCP tools take **URLs**, not local paths. This skill is the bridge: it turns a file the user named on their own machine into a hosted URL you can hand to any Picsart MCP tool. It is not a Drive browser and not a directory scanner — it moves exactly the file the user pointed at. ## When to Use _See the description above._ Concretely, reach for this when **both** hold: - The user named a specific local file (`~/photos/hero.jpg`, `./renders/clip.mp4`, a path they pasted). - The Picsart tool you want to call next needs a URL (`image_url`, `video_url`, `startFrame`, `image`, …). Do **not** use this skill to discover what files the user has — see Pitfalls. And skip it entirely before a `gen-ai` CLI generation: pass the local path to `-i` and the CLI uploads it for you (see Procedure, step 1). ## Prerequisites - **A Picsart MCP server connected**, for the small-file route — `picsart_drive` lives on the `picsart-gen-ai` server. Check what's connected before promising a next step. - **For a large file, the `gen-ai` CLI, authenticated.** Run `gen-ai whoami` (auth + install + Node 22+ check) before uploading. If `gen-ai` is not found: `curl -fsSL https://picsart.com/gen-ai-cli/install.sh | bash` (or `npm install -g @picsart/gen-ai`, needs Node 22+). If `gen-ai whoami` fails, tell the user to either run `gen-ai login` **themselves, interactively** — it's a browser OAuth flow, so you cannot drive it from a non-TTY shell — or export `PICSART_ACC...