gitlab-automation
Automate GitLab Workflows with Rube MCP
GitLab operations require repeated navigation, filtering, and identifier lookup across projects. This skill guides Claude, Codex, and Claude Code through Rube MCP workflows for repositories, pipelines, issues, and users.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "gitlab-automation" from https://skillstore.io/skills/sickn33-gitlab-automation.md and its manifest at https://skillstore.io/api/skills/sickn33-gitlab-automation/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "gitlab-automation". List open issues labeled critical in the payments project.
Expected outcome:
- Project resolved: platform/payments, project ID 184.
- Three open critical issues found across two result pages.
- Issue 42 is unassigned; issues 57 and 61 have active assignees.
Using "gitlab-automation". Show failed main-branch pipelines from the last seven days.
Expected outcome:
- Two failed pipelines matched the branch and date filters.
- The latest failure contains one failed test job and one canceled deployment job.
- No pipeline state was changed.
Using "gitlab-automation". Find project members matching Jordan and report their status.
Expected outcome:
The project has one matching active member with inherited access. The account status is available, and no membership changes were made.
Security Audit
Medium RiskThe 145 external-command detections are false positives caused by Markdown backticks, and both reconnaissance detections describe normal GitLab validation or filtering. The skill intentionally connects to Rube MCP, delegates GitLab OAuth access, and permits remote mutations without an explicit confirmation step.
Confirmed security concerns (2)
Capability review items (1)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
⚙️ External commands (50)
🌐 Network access (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-gitlab-automation/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-gitlab-automation?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-gitlab-automation?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-gitlab-automation/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-gitlab-automation.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). gitlab-automation security audit report (audit version 6) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-gitlab-automation/audits/6BibTeX citation
@techreport{sickn33-sickn33-gitlab-automation-2026,
author = {sickn33},
title = {gitlab-automation security audit report (audit version 6)},
institution = {Skillstore},
year = {2026},
number = {6},
url = {https://skillstore.io/skills/sickn33-gitlab-automation/audits/6},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "gitlab-automation security audit report (audit version 6)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-24"
url: "https://skillstore.io/skills/sickn33-gitlab-automation/audits/6"
identifiers:
- type: other
value: "skillstore:sickn33-gitlab-automation:audit:6"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Triage Project Issues
Find open issues, apply precise filters, resolve assignee identifiers, and prepare controlled updates.
Investigate Pipeline Failures
Filter failed pipelines by branch and date, inspect pipeline details, and summarize affected jobs.
Review Repository Access
List projects, inspect direct and inherited members, and check user status across selected repositories.
Try These Prompts
Connect to GitLab and find project [project]. List its open issues with labels, assignees, and update dates. Do not change anything.
Find project [project]. List all open merge requests targeting [branch]. Include draft status, author, reviewers, labels, and recent update time.
Inspect failed pipelines for project [project] on ref [branch] since [date]. List failed jobs and summarize the latest failure. Keep requests paginated.
Enumerate accessible projects matching [filter]. For each project, paginate through members and open issues. Highlight blocked users, unassigned issues, and incomplete coverage.
Best Practices
- Search Rube tool schemas before each workflow because parameters can change.
- Verify connection status, project identifiers, internal IDs, branches, and permissions before dependent calls.
- Preview remote mutations, request confirmation, paginate complete result sets, and use narrow filters.
Avoid
- Do not assume the first page contains every project, issue, merge request, pipeline, or member.
- Do not confuse project-scoped issue and pipeline identifiers with global identifiers.
- Do not replace labels, change assignees, or create remote resources without reviewing the intended effect.