glab(1)

💅 glab(1) — the glab skills install glow-up

okay bestie so this is a page from glab(1), the manual for glab — and today's main character is glab skills install. pull up a chair, hydrate, and let's get into it ✨

---

✨ NAME ✨

glab-skills-install — installs glab's bundled agent skills 🎀

heads up: this one is labeled (EXPERIMENTAL). we'll get to what that means, and you're gonna want to read it, fr fr.

---

🌸 SYNOPSIS 🌸

glab skills install [name] [flags]

---

🦋 DESCRIPTION 🦋

So what does it actually do? It installs those bundled SKILL.md files into .agents/skills/ — which is the cross-agent standard defined by the Agent Skills specification 🔥. And it's not picky, it plays nice with GitLab Duo Agent Platform, Claude Code, Codex, Gemini CLI, and literally any other agent that's compliant with the spec. inclusive queen behavior 💜

By default? Only the core glab skill gets installed. If you want a specific bundled skill instead, just pass a positional name argument. Not sure what's even available? Run glab skills list and go window shopping 👀

🎀 Install scope (the part where you choose ur destiny)

• Default — skills land in the current project, inside .agents/skills/ at the root of the current Git repository. that's the "no thoughts, just vibes" path 🌈
• --global — install for the current user instead, into ~/.agents/skills/. global icon energy 👑
• --path — install to a custom directory. important detail: the path is resolved relative to the current working directory, not the repository root. don't get caught out by that one bestie 🫶

Wanna overwrite a skill file that's already there? That's what --force is for. no cap.

⚠️ Real talk, and I mean it: this feature is an experiment and is not ready for production use. It might be unstable or removed at any time. For more information, see https://docs.gitlab.com/policy/development_stages_support/ .

---

⭐ OPTIONS ⭐

• -f, --force[=false] — overwrite skill files that already exist. respectfully, it does not ask twice 💅
• -g, --global[=false] — install skills at user scope, i.e. into ~/.agents/skills/.
• --path="" — install skills to the directory at . — and yes, that's literally what it says 😭 the placeholder got eaten somewhere in manpage-land, so it's giving "trust the flag, not the text" 🙈

---

🧚 OPTIONS INHERITED FROM PARENT COMMANDS 🧚

• -h, --help[=false] — show help for this command. when in doubt, ask the parent 🎀

---

💖 EXAMPLE 💖

here's the whole lil mood board of how you'd actually use it:

# Install the core glab skill in the current project (default)
glab skills install

# Install a specific bundled skill by name
glab skills install glab-stack

# Install the core skill globally (user scope)
glab skills install --global

# Install a skill to a custom directory
glab skills install glab-stack --path /path/to/skills

# Overwrite an existing skill file
glab skills install --force

look at that. five examples. ate and left no crumbs 🍓

---

🌈 SEE ALSO 🌈

• glab-skills(1) — the parent page, the origin story, the mothership 🫶

---

✨ and that's the whole page bestie ✨ this beauty was auto generated by spf13/cobra, dated Nov 2026, and it lives in glab(1). go install some skills, stay experimental, and remember: overwriting without --force is not the move 💀💜