generating-assetslisted

# Generating assets This skill answers one question first — *can you make anything at all?* — and only then how. Get the order wrong and you will design a beat around a photograph that never arrives. ## 1. Find out what you have, in a way that can answer Run one plain command per call: ``` command -v higgsfield ``` No `cd`, no `&&`, no `for` loop, no pipe. Compound commands are refused clause by clause, and a refused probe tells you nothing. A real run wrote a single `cd … && for b in comfy sd sdxl …` across eighteen binaries, had it denied outright, and recorded "found nothing" while an installed, authenticated generator sat on `PATH` with its commands already granted. Three outcomes, three different pages: | what happened | what to record | |---|---| | probed, nothing installed | no generator; design for stills you can draw | | probe refused, or binary found but not runnable | **blocked check** — name the command in `assumptions` | | found and runnable | name it, and what you used it for | Do not wait for a generator to appear in your tool list. Deferred MCP tools load through `ToolSearch`, and `ToolSearch` cannot be given to an agent — declared on an allowlist it is silently dropped, the same as an `mcp__*` wildcard. **The route open to you is a binary on `PATH`, driven over Bash.** ## 2. Do not inherit a provider Before choosing, check what you are about to copy. A run once grepped its own project scratch directory, found the provider a previous run had used, se