Install any skill in seconds. Free to start, no credit card required.
Get Started Free →agentworkforce/deploying-to-staging-environment
Use when deploying changes to staging across relay, relay-dashboard, and relay-cloud repos - coordinates multi-repo branch syncing using git worktrees, automatically triggers staging deployments via GitHub Actions
Passed 22 of 22 test cases with the skill, and 5 of 22 without it.
and 22 more in the full report
17 fixed5 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 17 test cases the skill fixed. Same model, same prompt, with and without the skill.
Where does the deployment workflow send HTTP requests to verify that the Fly.io staging application is up and running successfully, and what response status code is required?
| Checked | Without skill | With skill |
|---|---|---|
| Names https://agent-relay-staging.fly.dev/health as the health check endpoint URL. | Missed | Passed |
| States that an HTTP 200 response status code is required for the health check to pass. | Passed | Passed |
The instructions your model reads when the skill loads.
The staging environment deployment is a coordinated multi-repo process that synchronizes code across three repositories (relay, relay-dashboard, relay-cloud) and automatically triggers deployment via GitHub Actions. Staging deployments ensure feature verification before production while keeping main branch clean during development.
When NOT to use:
The staging deployment system consists of:
Three Repos (relay, relay-dashboard, relay-cloud)
↓
Staging Branches (synced via git push)
↓
relay-cloud staging push triggers GitHub Actions
↓
Deploy-Staging Workflow (deploy-staging.yml)
↓
Fly.io Staging Environment (agent-relay-staging)
↓
Automatic health check verification
Key details:
test cases passed, vs 5 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.