# Evals — together-fireworks

`cases.yaml` holds three things: `should_trigger` (prompts that must route into this skill, including the non-obvious "404 model not found" namespace bug and Spanish/Catalan phrasings), `should_not_trigger` (prompts that belong to a named sibling — `runpod`, `ollama`, `fal`, `huggingface`, `prompt-engineering`, `rag` — for the self-host / local / media / hub / prompt-design / pipeline boundaries), and one `capability` scenario with a `must_include` rubric. There is no automated runner here: route each trigger prompt through your skill-selection harness and confirm it lands (or doesn't) as labelled, then have an agent run the capability scenario and hand-score the output — every `must_include` line should be present (correct base_url + namespaced id, batch + 50% discount, the cost formula with dated numbers, the Together-native-Batch-API note). To structurally check any inference snippet the skill produces, run `../scripts/verify.sh <file-or-dir>`; a clean rubric pass plus a clean verify run is the bar.
