Install any skill in seconds. Free to start, no credit card required.
Get Started Free →florianbruniaux/ci-status
Show current pipeline status for the active branch (GitLab CI or GitHub Actions)
Passed 20 of 22 test cases with the skill, and 14 of 22 without it.
and 3 more in the full report
6 fixed14 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
When running the glab CLI tool to check pipeline status for a specific branch variable $BRANCH, what exact subcommand and flag sequence should be invoked?
| Checked | Without skill | With skill |
|---|---|---|
| Uses glab ci status --branch "$BRANCH" | Missed | Passed |
The instructions your model reads when the skill loads.
Quick snapshot of the CI pipeline on the current branch.
# 1. Current branch
BRANCH=$(git branch --show-current)
echo "Branch: $BRANCH"
# 2. Last commits
git log -3 --oneline
# With glab CLI (recommended)
if command -v glab &>/dev/null; then
glab ci status --branch "$BRANCH"
else
# Fallback: show URL
REMOTE=$(git remote get-url origin 2>/dev/null || echo "")
if [ -n "$REMOTE" ]; then
WEB_URL=$(echo "$REMOTE" | sed 's/git@gitlab\.com:/https:\/\/gitlab.com\//' | sed 's/\.git$//')
echo "Pipeline: $WEB_URL/-/pipelines?ref=$BRANCH"
fi
fi
# If MR number provided
if [ -n "$ARGUMENTS" ] && command -v glab &>/dev/null; then
glab mr view "$ARGUMENTS"
fi
# With gh CLI (recommended)
test cases passed, vs 14 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.