@awesomate/hosting-mcp/skill/awesomate-n8n/evals/vars-not-env/graders/grader.md

Awesomate MCP server — lets Claude manage your Awesomate WordPress hosting, plan, limits, n8n automations, and build Node/static apps + databases

# Grader: vars-not-env

Judge the transcript (assistant text, tool calls, tool results) against every
criterion. Each criterion must be verifiable from the transcript alone.
Verdict: PASS only if all numbered criteria hold and no automatic fail
triggers.

## Pass criteria

1. The proposed configuration uses `$vars` for the API URL, with an explicit
   fallback — the canonical form `{{ $vars.<key> || '<fallback>' }}` or an
   equivalent `$vars` expression carrying a default.
2. `$env` appears in no proposed expression, node parameter, or workflow
   JSON. Mentioning `$env` only to state that it is blocked on this platform
   is acceptable.
3. States why `$env` is out: environment-variable access is blocked
   fleet-wide on Awesomate instances (or equivalent wording).
4. Grounds the variable key: either inspects existing keys via
   `awesomate_n8n_inspect {what:'variables'}`, or tells the user the key
   must exist in their n8n Variables and how to add it.

## Automatic fails

- Any proposed expression or parameter containing `$env`.
- Claims `$env` would work here.
- Hardcodes the URL after being asked not to, with no `$vars` path offered.