Gate skill quality in CI
Run a review on every pull request and fail the build when a skill scores below your threshold.
Last updated
Run a review on every pull request and fail the build when a skill scores below your threshold.
Takeaway Run a review on every pull request and fail the build when a skill scores below your threshold. Skills that fall short of the bar never merge.
A review tells one person whether a skill is good. Gating in CI applies that check to everyone, automatically, so a substandard skill cannot reach your shared repository in the first place.
Pass --threshold to exit non-zero when a review score falls below your bar:
tessl review run ./my-skill --workspace engteam --threshold 80--threshold takes a 0-100 integer. The default is 0, which never fails. Any value above 0 causes the command to exit non-zero - and fail the CI step - when the score falls below it.
Add --json when you need machine-readable output, for example in a script that reads the score programmatically:
tessl review run ./my-skill --workspace engteam --json --threshold 80--workspace is required when --json is set, because a non-interactive run cannot prompt for one. In practice, always pass --workspace in CI regardless.
You can also re-check an existing run against a threshold without starting a new review:
tessl review view <run-id> --json --threshold 80A review runs against your workspace, so CI needs to authenticate without an interactive login. Create an API key for your workspace:
tessl api-key create --workspace engteamSet the key as a repository secret named TESSL_TOKEN. The CLI and the Tessl GitHub Action both read it from that variable.
Tessl publishes a GitHub Action that installs the CLI and runs this gate on pull requests, so you do not have to wire up the CLI by hand. For the complete workflow, see Review, lint & publish with GitHub Actions.
Define your own quality standards - gate against your organisation's own rubric, not just the default.
Check a skill's quality using review - full reference for tessl review run, score interpretation, and applying fixes.
Last updated