scenario-quality-gate
Scenario Quality Gate
Overview
One tool, asset_quality_gate_run, scores a finished image asset and returns a pass/warn/fail verdict with 0 to 100 scores and per-dimension lists of reasons and suggestions: an AI-quality check always, plus brand-brief compliance when the team or project has a brief configured. Image assets only. Quality Gate is an Enterprise add-on: when it is not enabled for the team the call fails cleanly, so detect that, fall back to an asset_analyze review (see scenario-asset-analysis), and say so. Retrying never clears it.
The tool is catalog-only and write-class: get the schema with scenario_tools_search, then run it through scenario_tool_execute_write with {name: "asset_quality_gate_run", parameters: {...}}, scope ids inside parameters (the read executor rejects it by lane and names the right one). Or reconnect with ?toolsets=full. Connection and scope: see the scenario skill. If a sibling skill named here is missing from your available skills, ask the user to install it (npx skills add scenario-labs/skills --skill <name>); unattended, proceed from tool schemas and flag the gap.
Quick reference: what a call costs
| Call | What happens | Cost |
|---|---|---|
| Plain call, usable verdict stored | Returns the stored verdict, source: "stored" |
Free (the response carries no creativeUnitsCost) |
| Plain call, no usable verdict | Runs a new analysis and stores the verdict, source: "new_analysis" |
Billed; the response carries creativeUnitsCost (1 CU as of this writing) |
rerun: true |
New analysis that replaces the stored verdict | Billed |
dry_run: true |
Nothing runs; returns the price of a new analysis as creativeUnitsCost |
Free |
A plain call is a read only when a usable verdict already exists; otherwise the same call silently escalates to the billed analysis. "No usable verdict" covers both never-scored and a stored error result. When spend needs approval first, probe free: dry_run: true, or asset_get, whose qualityGate field carries the verdict and scores when one is stored (summary only; the stored reasons and suggestions come back through the tool, still free). sensitivity (low, medium, high; default is the team or project setting) shapes new analyses only and is ignored on stored reads. rerun: true is for after the brief or the sensitivity changed, nothing else: it re-bills and overwrites.