Vibe CI Supply Chain
mistralai/mistral-vibe
Git workflow, CI/GitHub Actions, and supply-chain pinning rules for Mistral Vibe.
Explore GitLab repositories using glab CLI and git commands.
Install GitLab Explorer
$ npx skills add Wide-Moat/open-computer-use --skill gitlab-explorer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Wide-Moat/open-computer-use gitlab-explorer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Wide-Moat/open-computer-use.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/public/gitlab-explorer .claude/skills/gitlab-explorer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "gitlab-explorer" agent skill from https://github.com/Wide-Moat/open-computer-use/tree/main/skills/public/gitlab-explorer into .claude/skills/gitlab-explorer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gitlab-explorer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Wide-Moat/open-computer-use/tree/main/skills/public/gitlab-explorerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Wide-Moat/open-computer-use --skill gitlab-explorer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Wide-Moat/open-computer-use gitlab-explorer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Wide-Moat/open-computer-use.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/public/gitlab-explorer .agents/skills/gitlab-explorer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "gitlab-explorer" agent skill from https://github.com/Wide-Moat/open-computer-use/tree/main/skills/public/gitlab-explorer into .agents/skills/gitlab-explorer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gitlab-explorer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Wide-Moat/open-computer-use --skill gitlab-explorer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Wide-Moat/open-computer-use gitlab-explorer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Wide-Moat/open-computer-use.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/public/gitlab-explorer .cursor/skills/gitlab-explorer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "gitlab-explorer" agent skill from https://github.com/Wide-Moat/open-computer-use/tree/main/skills/public/gitlab-explorer into .cursor/skills/gitlab-explorer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gitlab-explorer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Wide-Moat/open-computer-use.git --path skills/public/gitlab-explorer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Wide-Moat/open-computer-use --skill gitlab-explorer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Wide-Moat/open-computer-use gitlab-explorer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Wide-Moat/open-computer-use.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/public/gitlab-explorer .gemini/skills/gitlab-explorer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "gitlab-explorer" agent skill from https://github.com/Wide-Moat/open-computer-use/tree/main/skills/public/gitlab-explorer into .gemini/skills/gitlab-explorer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gitlab-explorer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Wide-Moat/open-computer-use gitlab-explorerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Wide-Moat/open-computer-use --skill gitlab-explorer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Wide-Moat/open-computer-use.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/public/gitlab-explorer .github/skills/gitlab-explorer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "gitlab-explorer" agent skill from https://github.com/Wide-Moat/open-computer-use/tree/main/skills/public/gitlab-explorer into .github/skills/gitlab-explorer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gitlab-explorer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Wide-Moat/open-computer-use --skill gitlab-explorer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Wide-Moat/open-computer-use gitlab-explorer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Wide-Moat/open-computer-use.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/public/gitlab-explorer .opencode/skills/gitlab-explorer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "gitlab-explorer" agent skill from https://github.com/Wide-Moat/open-computer-use/tree/main/skills/public/gitlab-explorer into .opencode/skills/gitlab-explorer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gitlab-explorer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
gitlab-explorer- GitHub stars
- 126
- Token cost
- ~891 tokens
- SKILL.md length
- 230 words
- Files
- 4 (incl. scripts, references)
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Explore GitLab repositories using glab CLI and git commands.
- Works in 6 steps: Clone the repo → Check README and documentation → Explore directory structure with tree → …
- User asks to: clone repositories
- SKILL.md covers Before Any GitLab Operation, Quick Start, Exploring Code and Working with Merge Requests, plus 4 more sections
- Runs Shell scripts from its folder; calls glab, git and jq; reaches gitlab.com; needs GITLAB_TOKEN
What it does
GitLab Explorer is an agent skill from Wide-Moat/open-computer-use. Explore GitLab repositories using glab CLI and git commands. Use when user asks to: clone repositories, search projects or code in GitLab, view merge requests, explore project structure, check CI/CD pipelines, work with issues, or analyze git history. IMPORTANT: Always run authentication check script first before any GitLab operation.
Its SKILL.md is about 890 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts and reference files (for example `references/git-commands.md`, `references/glab-commands.md` and `scripts/check_gitlab_auth.sh`).
It sits in DevOps & Cloud, covering Git workflow and CI/CD. It works with GitLab and Git. The repository describes itself as: ARCHIVED — superseded by Wide Moat.
When your agent uses it
- User asks to: clone repositories
- Search projects
- View merge requests
- Explore project structure
Example prompts
- “/gitlab-explorer”
Requirements
- A Bash shell
- A credential in GITLAB_TOKEN
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Clone the repo
- Check README and documentation
- Explore directory structure with tree
- Find main entry points
- Use git log to understand recent changes
- Use git blame to find who wrote specific code
What it can do on your machine
Read from SKILL.md and the folder at commit 1ddf832. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
glabgitjqbash
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
gitlab.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
GITLAB_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
GitLab Explorer loads about 891 tokens when it runs, and up to ~3.3k if it reads all its reference files. Until then it costs about 88 tokens; SKILL.md has 230 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 230 words (~891 tokens).
“This skill enables exploring GitLab repositories, searching code, viewing merge requests, and working with git history.”
- name
- gitlab-explorer
Files
SKILL.md and 3 other files (scripts, references) in skills/public/gitlab-explorer of Wide-Moat/open-computer-use.
- SKILL.md
- references/git-commands.md
- references/glab-commands.md
- scripts/check_gitlab_auth.sh
Open the folder on GitHubat commit 1ddf832
Compare with similar skills
GitLab Explorer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| GitLab Explorer this skillWide-Moat/open-computer-use | 126 | — | ~891 | Automated safety check: Pass | Custom licence | |
| Vibe CI Supply Chainmistralai/mistral-vibe | 5.1k | — | ~1k | Automated safety check: Pass | Apache-2.0 | |
| Git Workflow for Chinese PlatformsjnMetaCode/superpowers-zh | 8.3k | — | ~2.4k | Automated safety check: Warn | MIT | |
| Automating Devopstelagod/code-abyss | 243 | — | ~422 | Automated safety check: Pass | MIT | |
| ccLoad Release Publishercaidaoli/ccLoad | 418 | — | ~887 | Automated safety check: Pass | MIT | |
| GlabNikiforovAll/claude-code-rules | 141 | 1 repos | ~2.2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Git Workflow for Chinese Platforms
jnMetaCode/superpowers-zh
Reference for setting up Git on Gitee, Coding.net, JiHu GitLab and CNB, with branching models, branch naming and CI differences for teams in China.
Automating Devops
telagod/code-abyss
DevOps knowledge reference covering Git workflows, testing strategies, DevSecOps, release pipeline orchestration (release.yml, multi-arch images, cosign integration), CI/CD pipelines, database…
ccLoad Release Publisher
caidaoli/ccLoad
Publishes a ccLoad Beta or explicit stable release through a version-tag workflow, including commit, push, CI wait, GitHub Release and container image checks.
Glab
NikiforovAll/claude-code-rules
Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line.
- Official
Authoring GitHub Workflows
dotnet/skills
Author and review GitHub Actions workflow YAML safely so syntactically-valid YAML can't ship a workflow that GitHub Actions refuses to run.
More from Wide-Moat/open-computer-use
Sub Agent
Wide-Moat/open-computer-use
COSTLY: Spawns a separate sub-agent CLI session. An agent skill from Wide-Moat/open-computer-use.
File Reading
Wide-Moat/open-computer-use
A skill your agent uses when a file has been uploaded but its content is NOT in your context — only its path at /mnt/user-data/uploads/ is listed in an uploadedfiles block.
PDF Reading
Wide-Moat/open-computer-use
A skill your agent uses when you need to read, inspect, or extract content from PDF files — especially when file content is NOT in your context and you need to read it from disk.
Describe Image
Wide-Moat/open-computer-use
Describe images (charts, diagrams, tables, screenshots) using Vision AI.
Related
Categories
Questions about GitLab Explorer
What does GitLab Explorer do?
Explore GitLab repositories using glab CLI and git commands. GitLab Explorer is an agent skill from Wide-Moat/open-computer-use. Explore GitLab repositories using glab CLI and git commands.
When should I use GitLab Explorer?
GitLab Explorer fits situations like: user asks to: clone repositories; search projects; view merge requests; explore project structure.
How do I install GitLab Explorer in Claude Code?
Run `npx skills add Wide-Moat/open-computer-use --skill gitlab-explorer -a claude-code`. Or copy the skill folder (skills/public/gitlab-explorer in Wide-Moat/open-computer-use) into .claude/skills/gitlab-explorer in your project. Claude Code loads it when a task matches its description.
How do I install GitLab Explorer in Codex?
Run `npx skills add Wide-Moat/open-computer-use --skill gitlab-explorer -a codex`. Or copy the skill folder (skills/public/gitlab-explorer in Wide-Moat/open-computer-use) into .agents/skills/gitlab-explorer in your project. Codex loads it when a task matches its description.
Can I use GitLab Explorer in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Wide-Moat/open-computer-use --skill gitlab-explorer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gitlab-explorer, .gemini/skills/gitlab-explorer, .github/skills/gitlab-explorer and .opencode/skills/gitlab-explorer in your project.
What does GitLab Explorer need to run?
Going by SKILL.md and its folder, GitLab Explorer needs a shell for the scripts in its folder, the command-line tools its instructions call (glab, git, jq and bash) and credentials named GITLAB_TOKEN. Our summary lists: A Bash shell; A credential in GITLAB_TOKEN.
Does GitLab Explorer access the network?
SKILL.md names 1 domain. In commands or code: gitlab.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is GitLab Explorer safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does GitLab Explorer use?
GitLab Explorer has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does GitLab Explorer use?
About 891 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.4k tokens, read only when the agent opens those files.
What are the alternatives to GitLab Explorer?
Skills that share tags, products or a category with GitLab Explorer: Vibe CI Supply Chain (mistralai/mistral-vibe, 5.1k stars), Git Workflow for Chinese Platforms (jnMetaCode/superpowers-zh, 8.3k stars), Automating Devops (telagod/code-abyss, 243 stars) and ccLoad Release Publisher (caidaoli/ccLoad, 418 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains GitLab Explorer?
Wide-Moat (a GitHub organization) maintains it in Wide-Moat/open-computer-use, which has 126 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 5, 2026.
Source: Wide-Moat/open-computer-use on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.