Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →release
Cut a new release by triggering the Release workflow via GitHub Actions workflow dispatch.
Passed 14 of 19 test cases with the skill, and 6 of 19 without it.
and 8 more in the full report
10 fixed6 passed either way5 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
When running release.yml for production deployment in vellum-assistant, which git reference must be passed as the --ref parameter?
| Checked | Without skill | With skill |
|---|---|---|
| Passes the release branch name release/v<X.Y.Z> as the ref parameter | Missed | Passed |
The instructions your model reads when the skill loads.
Cut a new release. Releases are a two-step process:
create-release-branch.yml computes the version from the bump type, deletes any stale release/v<X.Y.Z> branch, cuts a fresh one from main HEAD with the version-bump commit, and pushes it. That push triggers a Release run on the branch which is a staging deploy (push-triggered and main-dispatched Release runs are always staging).release.yml on the release/v<X.Y.Z> branch runs the full production release — tag, GitHub Release, DMG sign/notarize/publish, npm packages, Docker Hub images, iOS TestFlight, platform dependency bump, and the merge-back of the release branch to main.The scheduled Tue/Fri 8:52am ET cut performs step 1 automatically; a human performs step 2 after the staging bake is green. A release/v<X.Y.Z> branch with no corresponding GitHub Release means a cut was never promoted — re-running step 1 refreshes it from current main.
The user may pass $ARGUMENTS as the bump type for step 1: patch, minor, major, or hotfix (patch cut from the latest release tag's commit instead of main, pushed [skip ci] for manual cherry-picks). Default to patch.
git checkout main && git pull
git describe --tags --abbrev=0
git log --oneline "$(git describe --tags --abbrev=0)"..origin/main | head -20
Confirm with the user before proceeding unless they already asked for the release explicitly.
gh workflow run create-release-branch.yml \
--repo vellum-ai/vellum-assistant \
--ref main \
--field bump=<patch|minor|major|hotfix>
Then wait for the branch cut and find the staging Release run its push triggered:
gh run list --workflow="Create Release Branch" --limit 1
gh run list --workflow=Release --branch "release/v<X.Y.Z>" --limit 1
The version appears in the branch name; the staging run takes ~15-20 minutes. Wait for it to succeed — it is the CI bake for the exact release payload. If it fails, fix main and re-run this step (it recuts the branch from main HEAD).
test cases passed, vs 6 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.