Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashgraph-online/gitlab-ops
Use this skill when performing VCS operations on GitLab or GitHub repositories — creating, updating, or closing issues and MRs, applying label taxonomy, running `glab`/`gh` CLI commands, or resolving project IDs dynamically. Acts as the single source of truth for CLI command syntax and label conventions; consuming skills reference this rather than duplicating logic. Triggers: "create a GitLab issue", "list open MRs", "apply priority label", "how do I resolve the project ID", "what's the carryove
Passed 16 of 20 test cases with the skill, and 8 of 20 without it.
and 10 more in the full report
9 fixed9 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
At session close Phase 2.6, a knowingly-broken shipment with a hard due date needs a specific tracking issue filed. Which label identifies this specific knowingly-broken shipment carryover?
| Checked | Without skill | With skill |
|---|---|---|
| Includes the label broken-window | Missed | Passed |
The instructions your model reads when the skill loads.
Detect which VCS platform the current repo uses and select the right CLI:
# Check git remote
REMOTE_URL=$(git remote get-url origin 2>/dev/null)
if echo "$REMOTE_URL" | grep -q "github.com"; then
VCS=github # use `gh`
else
VCS=gitlab # use `glab`
fi
Session Config overrides:
vcs: github|gitlab — force a specific platformgitlab-host: <host> — override auto-detected GitLab host (glab reads host from git remote by default)Directive: Consuming skills MUST NOT duplicate VCS auto-detection logic or CLI command syntax inline. This skill is the single source of truth for all VCS operations.
When a skill needs VCS operations, include this reference block in its instructions:
VCS Reference: Detect the VCS platform per the "VCS Auto-Detection" section of the gitlab-ops skill. Use CLI commands per the "Common CLI Commands" section. For cross-project queries, see "Dynamic Project Resolution."
Canonical commands: All glab and gh command syntax — flags, output formats,
pagination options — is defined in the "Common CLI Commands" section below. Consuming
skills must reference that section rather than redefining commands. If a skill needs a
command variant not listed there, add it to this file first, then reference it.
What consuming skills should include:
glab/gh invocations or detection snippetstest cases passed, vs 8 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.