Skills 2026-10-05 17:42 UTC
skills
Committed by sjkim-expo. Update Category: Routine Updates & Maintenance. Commit details: [eas-simulator] State session costs as facts instead of asking before using the simulator (#211). This update performs routine maintenance and minor adjustments.
CommitRaw commit message
[eas-simulator] State session costs as facts instead of asking before using the simulator (#211) # Why In Szymon's benchmark of EAS Simulator against lim.run and revyl (#ai-infra, 2026-09-29), Opus stopped to ask how many iterations to run on EAS Simulator, and did not do that for the other two services ([ENG-27701](https://linear.app/expo/issue/ENG-27701)). That was after #186 had already removed the repeated billing warnings. The line that still reads as a reason to pause is "Ask before exceeding a stated budget or expanding beyond the requested work". # How In `eas-simulator` only: - The authorization paragraph now says to start the session and do the requested work without asking again, stop the session when the work is done, and only check in when the user set a limit the work would pass, or the work grows beyond what they asked for. - The cost callout keeps the required `**EAS service - costs apply.**` heading and the pricing link, and states facts instead of a caution: sessions count toward the account's pricing and limits, stop at their maximum duration, and can be stopped with `eas simulator:stop`. Like #186, it doesn't name a billing unit or a free tier. This doesn't touch the `EAS service (paid).` description prefix, which #202 removes, or the callouts in the other EAS skills. The plugin version goes to 1.13.9 in all four manifests. # Test Plan `check-skill-limits.ts`, `check-plugin-version-bump.ts origin/main`, and `check-overview-routing.ts` pass. I haven't rerun the benchmark prompt yet; the eval work David is building is the better check once it's ready.