Skip to content
skill-be

Workflows

There are two ways to gate a release on skill-be:

  • Run locally, commit, verify in CI. You run skill-be run on your machine with your own logins and commit skill-be.result.json; CI runs skill-be verify, which calls no model and needs no key, so it is fast and free. The trade-off: CI trusts the committed result. It proves the skill was READY when someone last ran it with this exact SKILL.md, eval file and config, not that it still is with today’s model.
  • CI runs everything. CI runs skill-be run with an API key (Credentials); its exit code is the gate and nothing needs committing. CI is the authority, but every run costs tokens and minutes, so it suits a manual or scheduled job better than every push.

The example shows the steps: Commit the result, then Verify in CI, whose workflow runs verify on every pull request and the benchmark on demand.