Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jeremylongshore/juicebox-ci-integration
Configure Juicebox CI/CD. Trigger: "juicebox ci", "juicebox pipeline".
Passed 21 of 24 test cases with the skill, and 5 of 24 without it.
and 14 more in the full report
16 fixed5 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 16 test cases the skill fixed. Same model, same prompt, with and without the skill.
Where in the repository directory structure should the Juicebox CI workflow definition file be placed, and what should it be named?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies the location .github/workflows/juicebox-ci.yml. | Missed | Passed |
The instructions your model reads when the skill loads.
Set up CI/CD for Juicebox AI data analysis integrations: run unit tests with mocked dataset and analysis responses on every PR, validate live API connectivity for data queries on merge to main. Juicebox provides AI-powered data exploration and visualization, so CI pipelines verify dataset upload logic, analysis execution, and result parsing workflows.
# .github/workflows/juicebox-ci.yml
name: Juicebox CI
on:
pull_request:
paths: ['src/juicebox/**', 'tests/**']
push:
branches: [main]
jobs:
unit-tests:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with: { node-version: '20' }
- run: npm ci
- run: npm test -- --reporter=verbose
integration-tests:
if: github.ref == 'refs/heads/main'
needs: unit-tests
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with: { node-version: '20' }
- run: npm ci
- run: npm run test:integration
env:
JUICEBOX_API_KEY: ${{ secrets.JUICEBOX_API_KEY }}
test cases passed, vs 5 / 24 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.