[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CA117R2TRGGG5ADQRPD8YY":3,"skill-same:01M7CA117R2TRGGG5ADQRPD8YY":50},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7CA117R2TRGGG5ADQRPD8YY","gitlab-automation",null,"Automate GitLab project management, issues, merge requests, pipelines, branches, and user operations via Rube MCP (Composio). Always search tools first for current schemas.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills\u002Fskills\u002Fgitlab-automation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: gitlab-automation\ndescription: \"Automate GitLab project management, issues, merge requests, pipelines, branches, and user operations via Rube MCP (Composio). Always search tools first for current schemas.\"\nrisk: critical\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# GitLab Automation via Rube MCP\n\nAutomate GitLab operations including project management, issue tracking, merge request workflows, CI\u002FCD pipeline monitoring, branch management, and user administration through Composio's GitLab toolkit.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active GitLab connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `gitlab`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `gitlab`\n3. If connection is not ACTIVE, follow the returned auth link to complete GitLab OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Manage Issues\n\n**When to use**: User wants to create, update, list, or search issues in a GitLab project\n\n**Tool sequence**:\n1. `GITLAB_GET_PROJECTS` - Find the target project and get its ID [Prerequisite]\n2. `GITLAB_LIST_PROJECT_ISSUES` - List and filter issues for a project [Required]\n3. `GITLAB_CREATE_PROJECT_ISSUE` - Create a new issue [Required for create]\n4. `GITLAB_UPDATE_PROJECT_ISSUE` - Update an existing issue (title, labels, state, assignees) [Required for update]\n5. `GITLAB_LIST_PROJECT_USERS` - Find user IDs for assignment [Optional]\n\n**Key parameters**:\n- `id`: Project ID (integer) or URL-encoded path (e.g., `\"my-group\u002Fmy-project\"`)\n- `title`: Issue title (required for creation)\n- `description`: Issue body text (max 1,048,576 characters)\n- `labels`: Comma-separated label names (e.g., `\"bug,critical\"`)\n- `add_labels` \u002F `remove_labels`: Add or remove labels without replacing all\n- `state`: Filter by `\"all\"`, `\"opened\"`, or `\"closed\"`\n- `state_event`: `\"close\"` or `\"reopen\"` to change issue state\n- `assignee_ids`: Array of user IDs; use `[0]` to unassign all\n- `issue_iid`: Internal issue ID within the project (required for updates)\n- `milestone`: Filter by milestone title\n- `search`: Search in title and description\n- `scope`: `\"created_by_me\"`, `\"assigned_to_me\"`, or `\"all\"`\n- `page` \u002F `per_page`: Pagination (default per_page: 20)\n\n**Pitfalls**:\n- `id` accepts either integer project ID or URL-encoded path; wrong IDs yield 4xx errors\n- `issue_iid` is the project-internal ID (shown as #42), different from the global issue ID\n- Labels in `labels` field replace ALL existing labels; use `add_labels`\u002F`remove_labels` for incremental changes\n- Setting `assignee_ids` to empty array does NOT unassign; use `[0]` instead\n- `updated_at` field requires administrator or project\u002Fgroup owner rights\n\n### 2. Manage Merge Requests\n\n**When to use**: User wants to list, filter, or review merge requests in a project\n\n**Tool sequence**:\n1. `GITLAB_GET_PROJECT` - Get project details and verify access [Prerequisite]\n2. `GITLAB_GET_PROJECT_MERGE_REQUESTS` - List and filter merge requests [Required]\n3. `GITLAB_GET_REPOSITORY_BRANCHES` - Verify source\u002Ftarget branches [Optional]\n4. `GITLAB_LIST_ALL_PROJECT_MEMBERS` - Find reviewers\u002Fassignees [Optional]\n\n**Key parameters**:\n- `id`: Project ID or URL-encoded path\n- `state`: `\"opened\"`, `\"closed\"`, `\"locked\"`, `\"merged\"`, or `\"all\"`\n- `scope`: `\"created_by_me\"` (default), `\"assigned_to_me\"`, or `\"all\"`\n- `source_branch` \u002F `target_branch`: Filter by branch names\n- `author_id` \u002F `author_username`: Filter by MR author\n- `assignee_id`: Filter by assignee (use `None` for unassigned, `Any` for assigned)\n- `reviewer_id` \u002F `reviewer_username`: Filter by reviewer\n- `labels`: Comma-separated label filter\n- `search`: Search in title and description\n- `wip`: `\"yes\"` for draft MRs, `\"no\"` for non-draft\n- `order_by`: `\"created_at\"` (default), `\"title\"`, `\"merged_at\"`, `\"updated_at\"`\n- `view`: `\"simple\"` for minimal fields\n- `iids[]`: Filter by specific MR internal IDs\n\n**Pitfalls**:\n- Default `scope` is `\"created_by_me\"` which limits results; use `\"all\"` for complete listings\n- `author_id` and `author_username` are mutually exclusive\n- `reviewer_id` and `reviewer_username` are mutually exclusive\n- `approved` filter requires the `mr_approved_filter` feature flag (disabled by default)\n- Large MR histories can be noisy; use filters and moderate `per_page` values\n\n### 3. Manage Projects and Repositories\n\n**When to use**: User wants to list projects, create new projects, or manage branches\n\n**Tool sequence**:\n1. `GITLAB_GET_PROJECTS` - List all accessible projects with filters [Required]\n2. `GITLAB_GET_PROJECT` - Get detailed info for a specific project [Optional]\n3. `GITLAB_LIST_USER_PROJECTS` - List projects owned by a specific user [Optional]\n4. `GITLAB_CREATE_PROJECT` - Create a new project [Required for create]\n5. `GITLAB_GET_REPOSITORY_BRANCHES` - List branches in a project [Required for branch ops]\n6. `GITLAB_CREATE_REPOSITORY_BRANCH` - Create a new branch [Optional]\n7. `GITLAB_GET_REPOSITORY_BRANCH` - Get details of a specific branch [Optional]\n8. `GITLAB_LIST_REPOSITORY_COMMITS` - View commit history [Optional]\n9. `GITLAB_GET_PROJECT_LANGUAGES` - Get language breakdown [Optional]\n\n**Key parameters**:\n- `name` \u002F `path`: Project name and URL-friendly path (both required for creation)\n- `visibility`: `\"private\"`, `\"internal\"`, or `\"public\"`\n- `namespace_id`: Group or user ID for project placement\n- `search`: Case-insensitive substring search for projects\n- `membership`: `true` to limit to projects user is a member of\n- `owned`: `true` to limit to user-owned projects\n- `project_id`: Project ID for branch operations\n- `branch_name`: Name for new branch\n- `ref`: Source branch or commit SHA for new branch creation\n- `order_by`: `\"id\"`, `\"name\"`, `\"path\"`, `\"created_at\"`, `\"updated_at\"`, `\"star_count\"`, `\"last_activity_at\"`\n\n**Pitfalls**:\n- `GITLAB_GET_PROJECTS` pagination is required for complete coverage; stopping at first page misses projects\n- Some responses place items under `data.details`; parse the actual returned list structure\n- Most follow-up calls depend on correct `project_id`; verify with `GITLAB_GET_PROJECT` first\n- Invalid `branch_name`\u002F`ref`\u002F`sha` causes client errors; verify branch existence via `GITLAB_GET_REPOSITORY_BRANCHES` first\n- Both `name` and `path` are required for `GITLAB_CREATE_PROJECT`\n\n### 4. Monitor CI\u002FCD Pipelines\n\n**When to use**: User wants to check pipeline status, list jobs, or monitor CI\u002FCD runs\n\n**Tool sequence**:\n1. `GITLAB_GET_PROJECT` - Verify project access [Prerequisite]\n2. `GITLAB_LIST_PROJECT_PIPELINES` - List pipelines with filters [Required]\n3. `GITLAB_GET_SINGLE_PIPELINE` - Get detailed info for a specific pipeline [Optional]\n4. `GITLAB_LIST_PIPELINE_JOBS` - List jobs within a pipeline [Optional]\n\n**Key parameters**:\n- `id`: Project ID or URL-encoded path\n- `status`: Filter by `\"created\"`, `\"waiting_for_resource\"`, `\"preparing\"`, `\"pending\"`, `\"running\"`, `\"success\"`, `\"failed\"`, `\"canceled\"`, `\"skipped\"`, `\"manual\"`, `\"scheduled\"`\n- `scope`: `\"running\"`, `\"pending\"`, `\"finished\"`, `\"branches\"`, `\"tags\"`\n- `ref`: Branch or tag name\n- `sha`: Specific commit SHA\n- `source`: Pipeline source (use `\"parent_pipeline\"` for child pipelines)\n- `order_by`: `\"id\"` (default), `\"status\"`, `\"ref\"`, `\"updated_at\"`, `\"user_id\"`\n- `created_after` \u002F `created_before`: ISO 8601 date filters\n- `pipeline_id`: Specific pipeline ID for job listing\n- `include_retried`: `true` to include retried jobs (default `false`)\n\n**Pitfalls**:\n- Large pipeline histories can be noisy; use `status`, `ref`, and date filters to narrow results\n- Use moderate `per_page` values to keep output manageable\n- Pipeline job `scope` accepts single status string or array of statuses\n- `yaml_errors: true` returns only pipelines with invalid configurations\n\n### 5. Manage Users and Members\n\n**When to use**: User wants to find users, list project members, or check user status\n\n**Tool sequence**:\n1. `GITLAB_GET_USERS` - Search and list GitLab users [Required]\n2. `GITLAB_GET_USER` - Get details for a specific user by ID [Optional]\n3. `GITLAB_GET_USERS_ID_STATUS` - Get user status message and availability [Optional]\n4. `GITLAB_LIST_ALL_PROJECT_MEMBERS` - List all project members (direct + inherited) [Required for member listing]\n5. `GITLAB_LIST_PROJECT_USERS` - List project users with search filter [Optional]\n\n**Key parameters**:\n- `search`: Search by name, username, or public email\n- `username`: Get specific user by username\n- `active` \u002F `blocked`: Filter by user state\n- `id`: Project ID for member listing\n- `query`: Filter members by name, email, or username\n- `state`: Filter members by `\"awaiting\"` or `\"active\"` (Premium\u002FUltimate)\n- `user_ids`: Filter by specific user IDs\n\n**Pitfalls**:\n- Many user filters (admins, auditors, extern_uid, two_factor) are admin-only\n- `GITLAB_LIST_ALL_PROJECT_MEMBERS` includes direct, inherited, and invited members\n- User search is case-insensitive but may not match partial email domains\n- Premium\u002FUltimate features (state filter, seat info) are not available on free plans\n\n## Common Patterns\n\n### ID Resolution\nGitLab uses two identifier formats for projects:\n- **Numeric ID**: Integer project ID (e.g., `123`)\n- **URL-encoded path**: Namespace\u002Fproject format (e.g., `\"my-group%2Fmy-project\"` or `\"my-group\u002Fmy-project\"`)\n- **Issue IID vs ID**: `issue_iid` is the project-internal number (#42); the global `id` is different\n- **User ID**: Numeric; resolve via `GITLAB_GET_USERS` with `search` or `username`\n\n### Pagination\nGitLab uses offset-based pagination:\n- Set `page` (starting at 1) and `per_page` (1-100, default 20)\n- Continue incrementing `page` until response returns fewer items than `per_page` or is empty\n- Total count may be available in response headers (`X-Total`, `X-Total-Pages`)\n- Always paginate to completion for accurate results\n\n### URL-Encoded Paths\nWhen using project paths as identifiers:\n- Forward slashes must be URL-encoded: `my-group\u002Fmy-project` becomes `my-group%2Fmy-project`\n- Some tools accept unencoded paths; check schema for each tool\n- Prefer numeric IDs when available for reliability\n\n## Known Pitfalls\n\n### ID Formats\n- Project `id` field accepts both integer and string (URL-encoded path)\n- Issue `issue_iid` is project-scoped; do not confuse with global issue ID\n- Pipeline IDs are project-scoped integers\n- User IDs are global integers across the GitLab instance\n\n### Rate Limits\n- GitLab has per-user rate limits (typically 300-2000 requests\u002Fminute depending on plan)\n- Large pipeline\u002Fissue histories should use date and status filters to reduce result sets\n- Paginate responsibly with moderate `per_page` values\n\n### Parameter Quirks\n- `labels` field replaces ALL labels; use `add_labels`\u002F`remove_labels` for incremental changes\n- `assignee_ids: [0]` unassigns all; empty array does nothing\n- `scope` defaults vary: `\"created_by_me\"` for MRs, `\"all\"` for issues\n- `author_id` and `author_username` are mutually exclusive in MR filters\n- Date parameters use ISO 8601 format: `\"2024-01-15T10:30:00Z\"`\n\n### Plan Restrictions\n- Some features require Premium\u002FUltimate: `epic_id`, `weight`, `iteration_id`, `approved_by_ids`, member `state` filter\n- Admin-only features: user management filters, `updated_at` override, custom attributes\n- The `mr_approved_filter` feature flag is disabled by default\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List projects | `GITLAB_GET_PROJECTS` | `search`, `membership`, `visibility` |\n| Get project details | `GITLAB_GET_PROJECT` | `id` |\n| User's projects | `GITLAB_LIST_USER_PROJECTS` | `id`, `search`, `owned` |\n| Create project | `GITLAB_CREATE_PROJECT` | `name`, `path`, `visibility` |\n| List issues | `GITLAB_LIST_PROJECT_ISSUES` | `id`, `state`, `labels`, `search` |\n| Create issue | `GITLAB_CREATE_PROJECT_ISSUE` | `id`, `title`, `description`, `labels` |\n| Update issue | `GITLAB_UPDATE_PROJECT_ISSUE` | `id`, `issue_iid`, `state_event` |\n| List merge requests | `GITLAB_GET_PROJECT_MERGE_REQUESTS` | `id`, `state`, `scope`, `labels` |\n| List branches | `GITLAB_GET_REPOSITORY_BRANCHES` | `project_id`, `search` |\n| Get branch | `GITLAB_GET_REPOSITORY_BRANCH` | `project_id`, `branch_name` |\n| Create branch | `GITLAB_CREATE_REPOSITORY_BRANCH` | `project_id`, `branch_name`, `ref` |\n| List commits | `GITLAB_LIST_REPOSITORY_COMMITS` | project ID, branch ref |\n| Project languages | `GITLAB_GET_PROJECT_LANGUAGES` | project ID |\n| List pipelines | `GITLAB_LIST_PROJECT_PIPELINES` | `id`, `status`, `ref` |\n| Get pipeline | `GITLAB_GET_SINGLE_PIPELINE` | `project_id`, `pipeline_id` |\n| List pipeline jobs | `GITLAB_LIST_PIPELINE_JOBS` | `id`, `pipeline_id`, `scope` |\n| Search users | `GITLAB_GET_USERS` | `search`, `username`, `active` |\n| Get user | `GITLAB_GET_USER` | user ID |\n| User status | `GITLAB_GET_USERS_ID_STATUS` | user ID |\n| List project members | `GITLAB_LIST_ALL_PROJECT_MEMBERS` | `id`, `query`, `state` |\n| List project users | `GITLAB_LIST_PROJECT_USERS` | `id`, `search` |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","# GitLab Automation via Rube MCP\n\nAutomate GitLab operations including project management, issue tracking, merge request workflows, CI\u002FCD pipeline monitoring, branch management, and user administration through Composio's GitLab toolkit.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active GitLab connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `gitlab`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `gitlab`\n3. If connection is not ACTIVE, follow the returned auth link to complete GitLab OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Manage Issues\n\n**When to use**: User wants to create, update, list, or search issues in a GitLab project\n\n**Tool sequence**:\n1. `GITLAB_GET_PROJECTS` - Find the target project and get its ID [Prerequisite]\n2. `GITLAB_LIST_PROJECT_ISSUES` - List and filter issues for a project [Required]\n3. `GITLAB_CREATE_PROJECT_ISSUE` - Create a new issue [Required for create]\n4. `GITLAB_UPDATE_PROJECT_ISSUE` - Update an existing issue (title, labels, state, assignees) [Required for update]\n5. `GITLAB_LIST_PROJECT_USERS` - Find user IDs for assignment [Optional]\n\n**Key parameters**:\n- `id`: Project ID (integer) or URL-encoded path (e.g., `\"my-group\u002Fmy-project\"`)\n- `title`: Issue title (required for creation)\n- `description`: Issue body text (max 1,048,576 characters)\n- `labels`: Comma-separated label names (e.g., `\"bug,critical\"`)\n- `add_labels` \u002F `remove_labels`: Add or remove labels without replacing all\n- `state`: Filter by `\"all\"`, `\"opened\"`, or `\"closed\"`\n- `state_event`: `\"close\"` or `\"reopen\"` to change issue state\n- `assignee_ids`: Array of user IDs; use `[0]` to unassign all\n- `issue_iid`: Internal issue ID within the project (required for updates)\n- `milestone`: Filter by milestone title\n- `search`: Search in title and description\n- `scope`: `\"created_by_me\"`, `\"assigned_to_me\"`, or `\"all\"`\n- `page` \u002F `per_page`: Pagination (default per_page: 20)\n\n**Pitfalls**:\n- `id` accepts either integer project ID or URL-encoded path; wrong IDs yield 4xx errors\n- `issue_iid` is the project-internal ID (shown as #42), different from the global issue ID\n- Labels in `labels` field replace ALL existing labels; use `add_labels`\u002F`remove_labels` for incremental changes\n- Setting `assignee_ids` to empty array does NOT unassign; use `[0]` instead\n- `updated_at` field requires administrator or project\u002Fgroup owner rights\n\n### 2. Manage Merge Requests\n\n**When to use**: User wants to list, filter, or review merge requests in a project\n\n**Tool sequence**:\n1. `GITLAB_GET_PROJECT` - Get project details and verify access [Prerequisite]\n2. `GITLAB_GET_PROJECT_MERGE_REQUESTS` - List and filter merge requests [Required]\n3. `GITLAB_GET_REPOSITORY_BRANCHES` - Verify source\u002Ftarget branches [Optional]\n4. `GITLAB_LIST_ALL_PROJECT_MEMBERS` - Find reviewers\u002Fassignees [Optional]\n\n**Key parameters**:\n- `id`: Project ID or URL-encoded path\n- `state`: `\"opened\"`, `\"closed\"`, `\"locked\"`, `\"merged\"`, or `\"all\"`\n- `scope`: `\"created_by_me\"` (default), `\"assigned_to_me\"`, or `\"all\"`\n- `source_branch` \u002F `target_branch`: Filter by branch names\n- `author_id` \u002F `author_username`: Filter by MR author\n- `assignee_id`: Filter by assignee (use `None` for unassigned, `Any` for assigned)\n- `reviewer_id` \u002F `reviewer_username`: Filter by reviewer\n- `labels`: Comma-separated label filter\n- `search`: Search in title and description\n- `wip`: `\"yes\"` for draft MRs, `\"no\"` for non-draft\n- `order_by`: `\"created_at\"` (default), `\"title\"`, `\"merged_at\"`, `\"updated_at\"`\n- `view`: `\"simple\"` for minimal fields\n- `iids[]`: Filter by specific MR internal IDs\n\n**Pitfalls**:\n- Default `scope` is `\"created_by_me\"` which limits results; use `\"all\"` for complete listings\n- `author_id` and `author_username` are mutually exclusive\n- `reviewer_id` and `reviewer_username` are mutually exclusive\n- `approved` filter requires the `mr_approved_filter` feature flag (disabled by default)\n- Large MR histories can be noisy; use filters and moderate `per_page` values\n\n### 3. Manage Projects and Repositories\n\n**When to use**: User wants to list projects, create new projects, or manage branches\n\n**Tool sequence**:\n1. `GITLAB_GET_PROJECTS` - List all accessible projects with filters [Required]\n2. `GITLAB_GET_PROJECT` - Get detailed info for a specific project [Optional]\n3. `GITLAB_LIST_USER_PROJECTS` - List projects owned by a specific user [Optional]\n4. `GITLAB_CREATE_PROJECT` - Create a new project [Required for create]\n5. `GITLAB_GET_REPOSITORY_BRANCHES` - List branches in a project [Required for branch ops]\n6. `GITLAB_CREATE_REPOSITORY_BRANCH` - Create a new branch [Optional]\n7. `GITLAB_GET_REPOSITORY_BRANCH` - Get details of a specific branch [Optional]\n8. `GITLAB_LIST_REPOSITORY_COMMITS` - View commit history [Optional]\n9. `GITLAB_GET_PROJECT_LANGUAGES` - Get language breakdown [Optional]\n\n**Key parameters**:\n- `name` \u002F `path`: Project name and URL-friendly path (both required for creation)\n- `visibility`: `\"private\"`, `\"internal\"`, or `\"public\"`\n- `namespace_id`: Group or user ID for project placement\n- `search`: Case-insensitive substring search for projects\n- `membership`: `true` to limit to projects user is a member of\n- `owned`: `true` to limit to user-owned projects\n- `project_id`: Project ID for branch operations\n- `branch_name`: Name for new branch\n- `ref`: Source branch or commit SHA for new branch creation\n- `order_by`: `\"id\"`, `\"name\"`, `\"path\"`, `\"created_at\"`, `\"updated_at\"`, `\"star_count\"`, `\"last_activity_at\"`\n\n**Pitfalls**:\n- `GITLAB_GET_PROJECTS` pagination is required for complete coverage; stopping at first page misses projects\n- Some responses place items under `data.details`; parse the actual returned list structure\n- Most follow-up calls depend on correct `project_id`; verify with `GITLAB_GET_PROJECT` first\n- Invalid `branch_name`\u002F`ref`\u002F`sha` causes client errors; verify branch existence via `GITLAB_GET_REPOSITORY_BRANCHES` first\n- Both `name` and `path` are required for `GITLAB_CREATE_PROJECT`\n\n### 4. Monitor CI\u002FCD Pipelines\n\n**When to use**: User wants to check pipeline status, list jobs, or monitor CI\u002FCD runs\n\n**Tool sequence**:\n1. `GITLAB_GET_PROJECT` - Verify project access [Prerequisite]\n2. `GITLAB_LIST_PROJECT_PIPELINES` - List pipelines with filters [Required]\n3. `GITLAB_GET_SINGLE_PIPELINE` - Get detailed info for a specific pipeline [Optional]\n4. `GITLAB_LIST_PIPELINE_JOBS` - List jobs within a pipeline [Optional]\n\n**Key parameters**:\n- `id`: Project ID or URL-encoded path\n- `status`: Filter by `\"created\"`, `\"waiting_for_resource\"`, `\"preparing\"`, `\"pending\"`, `\"running\"`, `\"success\"`, `\"failed\"`, `\"canceled\"`, `\"skipped\"`, `\"manual\"`, `\"scheduled\"`\n- `scope`: `\"running\"`, `\"pending\"`, `\"finished\"`, `\"branches\"`, `\"tags\"`\n- `ref`: Branch or tag name\n- `sha`: Specific commit SHA\n- `source`: Pipeline source (use `\"parent_pipeline\"` for child pipelines)\n- `order_by`: `\"id\"` (default), `\"status\"`, `\"ref\"`, `\"updated_at\"`, `\"user_id\"`\n- `created_after` \u002F `created_before`: ISO 8601 date filters\n- `pipeline_id`: Specific pipeline ID for job listing\n- `include_retried`: `true` to include retried jobs (default `false`)\n\n**Pitfalls**:\n- Large pipeline histories can be noisy; use `status`, `ref`, and date filters to narrow results\n- Use moderate `per_page` values to keep output manageable\n- Pipeline job `scope` accepts single status string or array of statuses\n- `yaml_errors: true` returns only pipelines with invalid configurations\n\n### 5. Manage Users and Members\n\n**When to use**: User wants to find users, list project members, or check user status\n\n**Tool sequence**:\n1. `GITLAB_GET_USERS` - Search and list GitLab users [Required]\n2. `GITLAB_GET_USER` - Get details for a specific user by ID [Optional]\n3. `GITLAB_GET_USERS_ID_STATUS` - Get user status message and availability [Optional]\n4. `GITLAB_LIST_ALL_PROJECT_MEMBERS` - List all project members (direct + inherited) [Required for member listing]\n5. `GITLAB_LIST_PROJECT_USERS` - List project users with search filter [Optional]\n\n**Key parameters**:\n- `search`: Search by name, username, or public email\n- `username`: Get specific user by username\n- `active` \u002F `blocked`: Filter by user state\n- `id`: Project ID for member listing\n- `query`: Filter members by name, email, or username\n- `state`: Filter members by `\"awaiting\"` or `\"active\"` (Premium\u002FUltimate)\n- `user_ids`: Filter by specific user IDs\n\n**Pitfalls**:\n- Many user filters (admins, auditors, extern_uid, two_factor) are admin-only\n- `GITLAB_LIST_ALL_PROJECT_MEMBERS` includes direct, inherited, and invited members\n- User search is case-insensitive but may not match partial email domains\n- Premium\u002FUltimate features (state filter, seat info) are not available on free plans\n\n## Common Patterns\n\n### ID Resolution\nGitLab uses two identifier formats for projects:\n- **Numeric ID**: Integer project ID (e.g., `123`)\n- **URL-encoded path**: Namespace\u002Fproject format (e.g., `\"my-group%2Fmy-project\"` or `\"my-group\u002Fmy-project\"`)\n- **Issue IID vs ID**: `issue_iid` is the project-internal number (#42); the global `id` is different\n- **User ID**: Numeric; resolve via `GITLAB_GET_USERS` with `search` or `username`\n\n### Pagination\nGitLab uses offset-based pagination:\n- Set `page` (starting at 1) and `per_page` (1-100, default 20)\n- Continue incrementing `page` until response returns fewer items than `per_page` or is empty\n- Total count may be available in response headers (`X-Total`, `X-Total-Pages`)\n- Always paginate to completion for accurate results\n\n### URL-Encoded Paths\nWhen using project paths as identifiers:\n- Forward slashes must be URL-encoded: `my-group\u002Fmy-project` becomes `my-group%2Fmy-project`\n- Some tools accept unencoded paths; check schema for each tool\n- Prefer numeric IDs when available for reliability\n\n## Known Pitfalls\n\n### ID Formats\n- Project `id` field accepts both integer and string (URL-encoded path)\n- Issue `issue_iid` is project-scoped; do not confuse with global issue ID\n- Pipeline IDs are project-scoped integers\n- User IDs are global integers across the GitLab instance\n\n### Rate Limits\n- GitLab has per-user rate limits (typically 300-2000 requests\u002Fminute depending on plan)\n- Large pipeline\u002Fissue histories should use date and status filters to reduce result sets\n- Paginate responsibly with moderate `per_page` values\n\n### Parameter Quirks\n- `labels` field replaces ALL labels; use `add_labels`\u002F`remove_labels` for incremental changes\n- `assignee_ids: [0]` unassigns all; empty array does nothing\n- `scope` defaults vary: `\"created_by_me\"` for MRs, `\"all\"` for issues\n- `author_id` and `author_username` are mutually exclusive in MR filters\n- Date parameters use ISO 8601 format: `\"2024-01-15T10:30:00Z\"`\n\n### Plan Restrictions\n- Some features require Premium\u002FUltimate: `epic_id`, `weight`, `iteration_id`, `approved_by_ids`, member `state` filter\n- Admin-only features: user management filters, `updated_at` override, custom attributes\n- The `mr_approved_filter` feature flag is disabled by default\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List projects | `GITLAB_GET_PROJECTS` | `search`, `membership`, `visibility` |\n| Get project details | `GITLAB_GET_PROJECT` | `id` |\n| User's projects | `GITLAB_LIST_USER_PROJECTS` | `id`, `search`, `owned` |\n| Create project | `GITLAB_CREATE_PROJECT` | `name`, `path`, `visibility` |\n| List issues | `GITLAB_LIST_PROJECT_ISSUES` | `id`, `state`, `labels`, `search` |\n| Create issue | `GITLAB_CREATE_PROJECT_ISSUE` | `id`, `title`, `description`, `labels` |\n| Update issue | `GITLAB_UPDATE_PROJECT_ISSUE` | `id`, `issue_iid`, `state_event` |\n| List merge requests | `GITLAB_GET_PROJECT_MERGE_REQUESTS` | `id`, `state`, `scope`, `labels` |\n| List branches | `GITLAB_GET_REPOSITORY_BRANCHES` | `project_id`, `search` |\n| Get branch | `GITLAB_GET_REPOSITORY_BRANCH` | `project_id`, `branch_name` |\n| Create branch | `GITLAB_CREATE_REPOSITORY_BRANCH` | `project_id`, `branch_name`, `ref` |\n| List commits | `GITLAB_LIST_REPOSITORY_COMMITS` | project ID, branch ref |\n| Project languages | `GITLAB_GET_PROJECT_LANGUAGES` | project ID |\n| List pipelines | `GITLAB_LIST_PROJECT_PIPELINES` | `id`, `status`, `ref` |\n| Get pipeline | `GITLAB_GET_SINGLE_PIPELINE` | `project_id`, `pipeline_id` |\n| List pipeline jobs | `GITLAB_LIST_PIPELINE_JOBS` | `id`, `pipeline_id`, `scope` |\n| Search users | `GITLAB_GET_USERS` | `search`, `username`, `active` |\n| Get user | `GITLAB_GET_USER` | user ID |\n| User status | `GITLAB_GET_USERS_ID_STATUS` | user ID |\n| List project members | `GITLAB_LIST_ALL_PROJECT_MEMBERS` | `id`, `query`, `state` |\n| List project users | `GITLAB_LIST_PROJECT_USERS` | `id`, `search` |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"critical","community","2026-02-27","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills\u002Fskills\u002Fgitlab-automation",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill gitlab-automation",{"tool":42,"command":43},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill gitlab-automation",{"tool":45,"command":46},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill gitlab-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills\u002Fskills\u002Fgitlab-automation\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]