Inconsistent terminology in skill-creator: assertions vs expectations

[kenwang-coursera]

The skill seems to use the terms "assertions" and "expectations" interchangeably which is mostly fine... except I think it confuses the agent somewhat and results in an evals.json that uses assertions instead of expectations in the json.

Not sure what the consequences of this are but if some (non agentic) script tries to read this file and it doesn't match expectations then it might fail unnecessarily.

[saeedseyfi]

+1
There are a couple of open PRs to fix this (#1443, #1679), going in opposite directions. Would be great to get a call on which name is canonical so one of them can land.