# Evals: no-code-app

This is a process/judgment skill — there is no compiled artifact, so there is no `verify.sh` and no automated runner. Evaluate by hand: read `cases.yaml` against `SKILL.md`. For each `should_trigger` prompt, confirm the description's "Use when…/Triggers:" line would plausibly route an agent here; for each `should_not_trigger`, confirm the named `route_to` sibling is the better home and that this skill's boundary (`NOT a coded web app (that is nextjs)`) sends it away. The `capability` case is a rubric check: an agent following the skill on the yoga-studio brief should produce all five `must_include` items — Step 0 gate, a platform pick justified by app shape + billing model, a normalized data model with a named backend, a metered cost/limit estimate with a load-test note, and an exit/export plan. If any are missing, the SKILL.md body needs tightening.
