mcpField
G
gitlab-wiki

gitlab-wiki

github.com/grandcamelProductivity498 installsUpdated 40w ago
Repository

About gitlab-wiki

gitlab-wiki is a skill for managing GitLab project wikis through `glab api`, intended for teams maintaining project documentation. It handles page retrieval and editing, deletion, and attachment uploads.

Key features

  1. 01List and retrieve wiki pages
  2. 02Create, update, and delete pages
  3. 03Upload attachments such as images
  4. 04Support multiple page formats
  5. 05List pages with pagination

Use cases

  1. 01Create project documentation pages
  2. 02Update or back up wiki content
  3. 03Upload diagrams for wiki pages
  4. 04Move wiki pages between projects

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/grandcamel/gitlab-assistant-skills --skill gitlab-wiki

After installing, type/gitlab-wikiin Claude Code to confirm it loaded.

Details

From the project README

Wiki Skill

Wiki page management for GitLab using glab api raw endpoint calls.

Quick Reference

OperationCommand PatternRisk
List pagesglab api projects/:id/wikis-
Get pageglab api projects/:id/wikis/:slug-
Create pageglab api projects/:id/wikis -X POST -f ...⚠️
Update pageglab api projects/:id/wikis/:slug -X PUT -f ...⚠️
Delete pageglab api projects/:id/wikis/:slug -X DELETE⚠️⚠️
Upload attachmentglab api projects/:id/wikis/attachments -X POST ...⚠️

Risk Legend: - Safe | ⚠️ Caution | ⚠️⚠️ Warning | ⚠️⚠️⚠️ Danger

When to Use This Skill

ALWAYS use when:

  • User mentions "wiki", "wiki page", "documentation page"
  • User wants to create/edit project documentation in GitLab
  • User mentions wiki slugs or wiki content
  • User wants to upload images to wiki

NEVER use when:

  • User wants README files (use gitlab-file)
  • User wants to search wiki content (use gitlab-search with wiki_blobs scope)
  • User wants external documentation (not GitLab wiki)

API Prerequisites

Required Token Scopes: api

Permissions:

  • Read wiki: Reporter+ (for private repos)
  • Write wiki: Developer+ (or based on project settings)

Note: Wiki must be enabled for the project.

Available Commands

List Wiki Pages
# List all wiki pages
glab api projects/123/wikis --method GET

# With pagination
glab api projects/123/wikis --paginate

# Using project path
glab api "projects/$(echo 'mygroup/myproject' | jq -Rr @uri)/wikis"
Get Wiki Page
# Get page by slug
glab api projects/123/wikis/home --method GET

# Get page with spaces in slug (URL-encode)
glab api "projects/123/wikis/$(echo 'Getting Started' | jq -Rr @uri)" --method GET

# Get nested page
glab api "projects/123/wikis/$(echo 'docs/installation' | jq -Rr @uri)" --method GET

# Get page with specific version
glab api "projects/123/wikis/home?version=abc123" --method GET

# Render HTML
glab api "projects/123/wikis/home?render_html=true" --method GET
Create Wiki Page
# Create simple page
glab api projects/123/wikis --method POST \
  -f title="Getting Started" \
  -f content="# Getting Started\n\nWelcome to the project!"

# Create with Markdown format
glab api projects/123/wikis --method POST \
  -f title="Installation Guide" \
  -f content="# Installation\n\n## Prerequisites\n\n- Node.js 18+\n- npm" \
  -f format="markdown"

# Create with custom slug
glab api projects/123/wikis --method POST \
  -f title="API Reference" \
  -f slug="api-docs" \
  -f content="# API Documentation\n\nEndpoints..."

# Create nested page (using directory in slug)
glab api projects/123/wikis --method POST \
  -f title="Database Setup" \
  -f slug="guides/database-setup" \
  -f content="# Database Setup\n\nConfiguration steps..."
Update Wiki Page
# Update content
glab api "projects/123/wikis/$(echo 'Getting Started' | jq -Rr @uri)" --method PUT \
  -f content="# Getting Started\n\n## Updated content\n\nNew information..."

# Update title and content
glab api projects/123/wikis/home --method PUT \
  -f title="Home Page" \
  -f content="# Welcome\n\nUpdated home page content."

# Change format (markdown, rdoc, asciidoc)
glab api projects/123/wikis/readme --method PUT \
  -f format="asciidoc" \
  -f content="= README\n\nAsciidoc content here."
Delete Wiki Page
# Delete page
glab api projects/123/wikis/old-page --method DELETE

# Delete nested page (URL-encode)
glab api "projects/123/wikis/$(echo 'drafts/temp-page' | jq -Rr @uri)" --method DELETE
Upload Attachment
# Upload image
glab api projects/123/wikis/attachments --method POST \
  -F "[email protected]"

# The response contains the markdown link to use
# {"file_name":"screenshot.png","file_path":"uploads/...","branch":"master","link":{"url":"...","markdown":"![screenshot](uploads/...)"}}

Wiki Page Options

OptionTypeDescription
titlestringPage title (required for create)
slugstringPage URL slug (auto-generated from title if not provided)
contentstringPage content
formatstringContent format: markdown (default), rdoc, asciidoc

Format Support

FormatExtensionDescription
markdown.mdGitHub-flavored Markdown
rdoc.rdocRuby documentation format
asciidoc.asciidocAsciiDoc format
org.orgOrg mode format

Common Workflows

Workflow 1: Create Documentation Structure
project_id=123

# Create home page
glab api projects/$project_id/wikis --method POST \
  -f title="Home" \
  -f content="# Project Wiki\n\n- [Getting Started](Getting-Started)\n- [API Reference](API-Reference)\n- [FAQ](FAQ)"

# Create getting started guide
glab api projects/$project_id/wikis --method POST \
  -f title="Getting Started" \
  -f content="# Getting Started\n\n## Installation\n\n\`\`\`bash\nnpm install\n\`\`\`"

# Create API reference
glab api projects/$project_id/wikis --method POST \
  -f title="API Reference" \
  -f content="# API Reference\n\n## Endpoints\n\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /users | List users |"
Workflow 2: Backup Wiki Content
# List all pages and save content
mkdir -p wiki_backup
glab api projects/123/wikis --paginate | jq -r '.[].slug' | while read slug; do
  echo "Backing up: $slug"
  glab api "projects/123/wikis/$(echo "$slug" | jq -Rr @uri)" | \
    jq -r '.content' > "wiki_backup/${slug//\//_}.md"
done
Workflow 3: Migrate Wiki Content
# Get page from source project
content=$(glab api projects/123/wikis/home | jq -r '.content')
title=$(glab api projects/123/wikis/home | jq -r '.title')

# Create in target project
glab api projects/456/wikis --method POST \
  -f title="$title" \
  -f content="$content"
Workflow 4: Add Image to Wiki Page
# 1. Upload image
response=$(glab api projects/123/wikis/attachments --method POST -F "[email protected]")

# 2. Get markdown link
markdown_link=$(echo "$response" | jq -r '.link.markdown')

# 3. Update page to include image
current_content=$(glab api projects/123/wikis/architecture | jq -r '.content')
new_content="$current_content

## Diagram

$markdown_link"

glab api projects/123/wikis/architecture --method PUT \
  -f content="$new_content"
Workflow 5: List All Wiki Pages with Titles
glab api projects/123/wikis --paginate | \
  jq -r '.[] | "[\(.title)](\(.slug))"'

Wiki Slugs

Slugs are URL-safe versions of titles:

  • Spaces become hyphens: Getting Started → Getting-Started
  • Special characters are removed
  • Case is preserved

For nested pages, use directory structure in slug:

  • guides/installation creates a page under guides/

Troubleshooting

IssueCauseSolution
404 Not FoundWiki disabled or page doesn't existEnable wiki in project settings, check slug
403 ForbiddenNo write accessNeed Developer+ role or check wiki permissions
Empty contentEncoding issueCheck content string escaping
Slug mismatchAuto-generated slug differsExplicitly set slug parameter
Upload failsWrong content typeUse -F flag for file uploads

Best Practices

  1. Use meaningful slugs: Keep URLs readable and consistent
  2. Create a home page: Start with a home/index page
  3. Use relative links: Link between wiki pages using slugs
  4. Organize with structure: Use slug directories for organization
  5. Include images: Upload screenshots and diagrams for clarity

Related Documentation

Comments

Markdown supported