Model Integration

The consistency skills in this repo decide what to prompt and which reference to condition on. This skill owns everything below that line: finding a way to reach a model, choosing the right one for the job, making the call correctly, and recovering when it fails.

Treat it as a contract with four clauses:

1. Discover before you call. The environment defines what's possible — never assume a provider.
2. Route by capability. Models differ most where consistency cares most: how faithfully they follow a reference image.
3. Invoke reproducibly. Same inputs should give comparable outputs; outputs land as local files, never bare URLs.
4. Fail loudly and cheaply. Diagnose from the error, retry only what retrying can fix, and report exactly what ran.

Clause 1 — Discovery

Work down this list and stop at the first hit:

1. Session tools. An MCP image tool or generation skill already wired into the session (for example a fal-backed generation skill) beats raw SDK calls — auth, upload, and download are solved. Enumerate what the session exposes before writing any provider code.
2. Credentials in the environment. Probe, don't guess: