GitLab Connector for Muse
GitLab user, projects, open merge requests and issue creation
- What
- GitLab user, projects, open merge requests and issue creation
- Cost
- Free
- Needs
- A GitLab personal access token (gitlab.com → Preferences → Access Tokens; read_api scope for reads, api scope to create issues), kept in your Muse's secure vault (never paste secrets here).
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
A Muse agent skill that reads and writes GitLab: who the token belongs to, project list, open merge requests for a project, and issue creation (needs the `api` token scope). Issue creation needs confirmation first. No secrets in the repo — credentials stay in Muse's secure vault.
Curated by Skill Harbor — free, open-source build (MIT) by @bluman1.
Version:
Install
Prerequisites: A GitLab personal access token (gitlab.com → Preferences → Access Tokens; read_api scope for reads, api scope to create issues), kept in your Muse's secure vault (never paste secrets here). No GitHub account needed unless listed here. Install "GitLab Connector for Muse" for me. A Muse agent skill that reads and writes GitLab: your user, projects, open merge requests, and issue creation. Repository: https://github.com/bluman1/muse-connectors/tree/main/connectors/gitlab 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "gitlab". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. save my GitLab personal access token in the vault with the right scopes). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.