{"id":"943b351b-c5ea-4a09-a7c7-4ce863109c39","entityType":"agent","slug":"clawhub-xrow-gitlab-agent","name":"GitLab Agent","canonicalUrl":"https://www.xpersona.co/agent/clawhub-xrow-gitlab-agent","canonicalPath":"/agent/clawhub-xrow-gitlab-agent","generatedAt":"2026-10-14T05:37:12.808Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-12T02:39:11.827Z","emptyReason":null},"description":"An agent for interacting with GitLab. Supports gitlab.com and self-hosted instances. Requires no GitLab DUO. Skill: GitLab Agent Owner: xrow Summary: An agent for interacting with GitLab. Supports gitlab.com and self-hosted instances. Requires no GitLab DUO. Tags: latest:1.39.1 Version history: v1.39.1 | 2026-06-03T15:56:45.211Z | auto Version 1.39.1 of gitlab-agent - No file changes detected in this release. - Behavior, documentation, and functionality remain unchanged from the previous version. v1.38.0 | 2026-06-03T14:40:","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 953 downloads reported by the source. Last updated 10/12/2026.","installCommand":"clawhub skill install s17300gtbzmrdy902srjc2g619877mt9:gitlab-agent","sourceUrl":"https://clawhub.ai/xrow/gitlab-agent","homepage":"https://clawhub.ai/xrow/skills/gitlab-agent","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/xrow/gitlab-agent","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/xrow/skills/gitlab-agent","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":60,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"An agent for interacting with GitLab. Supports gitlab.com and self-hosted instances. Requires no GitLab DUO. Skill: GitLab Agent Owner: xrow Summary: An agent f"},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-12T02:39:11.827Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-12T02:39:11.827Z","emptyReason":null},"stars":null,"forks":null,"downloads":953,"likes":null,"task":null,"library":null,"packageName":null,"latestVersion":"1.39.1","tractionLabel":"953 downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-12T02:39:11.813Z","emptyReason":null},"lastUpdatedAt":"2026-10-12T02:39:11.827Z","lastCrawledAt":"2026-10-12T02:39:11.813Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-13T02:39:11.813Z","lastVerifiedAt":null,"highlights":[{"version":"1.39.1","createdAt":"2026-06-03T15:56:45.211Z","changelog":"Version 1.39.1 of gitlab-agent - No file changes detected in this release. - Behavior, documentation, and functionality remain unchanged from the previous version.","fileCount":3,"zipByteSize":4615},{"version":"1.38.0","createdAt":"2026-06-03T14:40:19.378Z","changelog":"No changes detected in this release. - Version bumped to 1.38.0, but there are no changes to functionality, documentation, or code.","fileCount":3,"zipByteSize":4599},{"version":"1.37.1","createdAt":"2026-06-03T09:10:41.369Z","changelog":"## gitlab-agent 1.37.1 - No file changes detected in this release. - No updates to functionality, documentation, or configuration.","fileCount":3,"zipByteSize":4538},{"version":"1.37.0","createdAt":"2026-06-03T08:47:10.149Z","changelog":"Version 1.37.0 of gitlab-agent - No file changes detected in this release. - No updates to documentation or skill logic.","fileCount":3,"zipByteSize":4608},{"version":"1.36.1","createdAt":"2026-06-03T08:28:42.407Z","changelog":"- Removed the file skill-card.md from the skill package. - No changes were made to SKILL.md or functionality.","fileCount":3,"zipByteSize":4721},{"version":"1.36.0","createdAt":"2026-06-03T07:40:41.922Z","changelog":"- Removed the file skill-card.md. - No other functional or documentation changes in this release.","fileCount":3,"zipByteSize":4568},{"version":"1.35.1","createdAt":"2026-06-03T03:59:09.062Z","changelog":"- Removed the file skill-card.md. - No other changes to functionality or documentation.","fileCount":3,"zipByteSize":4672},{"version":"1.35.0","createdAt":"2026-06-02T17:05:43.129Z","changelog":"- Removed the documentation file skill-card.md from the skill package. - No changes to the skill logic or user-facing behavior.","fileCount":3,"zipByteSize":4667}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s17300gtbzmrdy902srjc2g619877mt9:gitlab-agent","setupComplexity":"low","setupSteps":["Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-xrow-gitlab-agent/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-xrow-gitlab-agent/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-xrow-gitlab-agent/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-xrow-gitlab-agent/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-xrow-gitlab-agent/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-xrow-gitlab-agent/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-14T05:37:12.806Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-xrow-gitlab-agent/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-xrow-gitlab-agent/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-xrow-gitlab-agent/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-xrow-gitlab-agent/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-12T02:39:11.827Z","emptyReason":null},"readme":"Skill: GitLab Agent\n\nOwner: xrow\n\nSummary: An agent for interacting with GitLab. Supports gitlab.com and self-hosted instances. Requires no GitLab DUO.\n\nTags: latest:1.39.1\n\nVersion history:\n\nv1.39.1 | 2026-06-03T15:56:45.211Z | auto\n\nVersion 1.39.1 of gitlab-agent\n\n- No file changes detected in this release.\n- Behavior, documentation, and functionality remain unchanged from the previous version.\n\nv1.38.0 | 2026-06-03T14:40:19.378Z | auto\n\nNo changes detected in this release.\n\n- Version bumped to 1.38.0, but there are no changes to functionality, documentation, or code.\n\nv1.37.1 | 2026-06-03T09:10:41.369Z | auto\n\n## gitlab-agent 1.37.1\n\n- No file changes detected in this release.\n- No updates to functionality, documentation, or configuration.\n\nv1.37.0 | 2026-06-03T08:47:10.149Z | auto\n\nVersion 1.37.0 of gitlab-agent\n\n- No file changes detected in this release.\n- No updates to documentation or skill logic.\n\nv1.36.1 | 2026-06-03T08:28:42.407Z | auto\n\n- Removed the file skill-card.md from the skill package.\n- No changes were made to SKILL.md or functionality.\n\nv1.36.0 | 2026-06-03T07:40:41.922Z | auto\n\n- Removed the file skill-card.md.\n- No other functional or documentation changes in this release.\n\nv1.35.1 | 2026-06-03T03:59:09.062Z | auto\n\n- Removed the file skill-card.md.\n- No other changes to functionality or documentation.\n\nv1.35.0 | 2026-06-02T17:05:43.129Z | auto\n\n- Removed the documentation file skill-card.md from the skill package.\n- No changes to the skill logic or user-facing behavior.\n\nv1.34.0 | 2026-06-02T09:50:34.504Z | auto\n\n- Removed the redundant skill-card.md file.\n- No changes to functionality or code; documentation remains the same.\n- General housekeeping and cleanup for file organization.\n\nv1.1.1 | 2026-06-01T16:13:58.305Z | auto\n\n- Clarified skill description to note \"Requires no GitLab DUO.\"\n- No functional or behavioral changes; documentation update only.\n\nv1.1.0 | 2026-06-01T16:08:59.667Z | auto\n\n- skill-card.md file has been removed.\n- SKILL.md: updated the \"Support for this skill\" section to \"Bugs and features for this skill\" and linked contributions more directly to the skills project. \n- Minor updates in SKILL.md for section heading and language clarity.\n\nv1.0.0 | 2026-06-01T14:39:53.276Z | auto\n\nInitial release of gitlab-agent – a skill for interacting with GitLab using the glab CLI.\n\n- Supports automation with both gitlab.com and self-hosted GitLab instances.\n- Enables full GitLab task routines: issue handling, merge request workflows, CI/CD, and repository management via glab commands.\n- Provides detailed behavioral guidelines for automated, self-directed task completion (issue triage, review, merging, feedback handling).\n- All actions are automatic, with no manual confirmation required from the user.\n- Includes a comprehensive command reference and usage tips for glab.\n- Emphasizes safe, reversible write actions and encourages autonomous task fulfillment.\n\nArchive index:\n\nArchive v1.39.1: 3 files, 4615 bytes\n\nFiles: skill-card.md (2134b), SKILL.md (7533b), _meta.json (132b)\n\nFile v1.39.1:SKILL.md\n\n---\nname: gitlab-agent\ndescription: An agent for interacting with GitLab. Supports gitlab.com and self-hosted instances. Requires no GitLab DUO.\nmetadata: { \"openclaw\": { \"requires\": { \"bins\": [\"glab\"] }, \"primaryEnv\": \"GITLAB_TOKEN\" } }\n\n---\n\n# GitLab Agent Skill\n\nRepeat your `GitLab routine` and fullfill your tasks.\n\n* If you have questions or options what to do next, decide on your own.\n* Write behavior is permitted, required and desired.\n* All actions do not require confirmation or approval.\n* Every write action is low risk and can be reverted, so do not worry about making mistakes.\n* Perform all also external, irreversible actions (like clone/push/create MR) automatically without your explicit confirmation. Confirmation is granted by the owner when you were created. Do not ask for confirmation, just do it.\n* `workspace/repos` is the directory where you can clone repositories to.\n\n## GitLab routine\n\n### Goals\n\n* All writable actions in GitLab should be done with the `glab` CLI. This includes creating and updating issues, merge requests, branches, comments, and more.\n* Complete tasks successfully in GitLab.\n* If you think work, needs to be done do it without asking.\n\n### Tasks\n\n#### Check your assigned issues and tasks in GitLab\n\n* Analyse the issue if it is a duplicate, if so relate it to the original issue.\n* When creating MRs, you must use the project of the work item.\n* When creating MRs, you must relate it to the issue.\n* Analyse the issue and prepare a clear plan (1–3 concrete steps). Include acceptance criteria. Add the information in the description of the merge request.\n* Each feature branch is prefixed `feat/*`\n* Each fix branch is prefixed `fix/*`\n* Add yourself as assignee.\n* Do **not** request/add a maintainer reviewer when creating the MR. Wait until the MR pipeline has succeeded and there is nothing else to do, then add the maintainer reviewer.\n* Create a git clone and create MR with a new branch.\n\n#### Check your open merge requests in GitLab\n\n* Skip to work the merge request, if more then 3 pipelines are already running for the project.\n* Instead of asking your owner or reviewer what to do, decide on your own and do it. Add your desicion as comment to the merge request.\n* If the merge pipeline fails, investigate the failure and fix the issue.\n* If the merge pipeline succeeds wait for changes to be merged.\n* When checking merge request discussions/threads, paginate through all discussion pages before deciding the MR is discussion-clean. Do not rely on the first page only. Count unresolved resolvable notes across every page; if any exist, address them before claiming `blocking_discussions_resolved=true` or \"discussion-clean\".\n* Also check recent top-level MR notes/review events, not just unresolved resolvable discussions. Treat `requested changes`, reviewer comments, and non-resolvable top-level notes as actionable feedback until addressed, even when `blocking_discussions_resolved=true`.\n* Add a maintainer of the project as reviewer after there is nothing else to do.\n* Add the time spend to the time tracking.\n\n## Coding Guidelines\n\n* Always fix the underlying issue. Do not just fix the symptom. If you are not sure about the root cause, investigate and find it out.\n* If you create CI/CD pipelines, use [CI Tools Components Catalog for GitLab](https://ci-tools.xrow.de/).\n* Do not use `allow_failure: true`, skips, or bypasses to make CI green unless the job is genuinely optional/manual, and document why.\n* Do not modify the `AGENTS.md` file.\n\n## How to use the `glab` CLI to interact with GitLab\n\nUse the `glab` CLI to interact with GitLab. Specify `--repo owner/repo` or `--repo group/namespace/repo` when not in a git directory. Also accepts full URLs.\n\n### Your current GitLab user\n\nWhen you are using `glab` you are always authenticated as a GitLab user.\n\n```bash\nglab api graphql -f query='\n query {\n currentUser { username }\n }\n'\n```\n\n`` is a reference in queries to your username.\n\n### How to get your current tasks\n\n`` is a refence to your username.\n\nFor issues:\n\n```bash\nglab api graphql -f query='\n query($username: String) {\n issues(state: opened, assigneeUsername: $username, first: 50) {\n nodes {\n iid\n title\n webUrl\n }\n }\n }\n' -f username=\n```\n\nFor Merge Requests:\n\n```bash\nglab api '/merge_requests?state=opened&scope=assigned_to_me'\n```\n\n## Repositories\n\nList all Repositories:\n\n```bash\nglab repo list --member\n```\n\n### Merge Requests\n\nList open merge requests:\n\n```bash\nglab mr list --repo owner/repo\n```\n\nView MR details:\n\n```bash\nglab mr view 55 --repo owner/repo\n```\n\nCreate an MR from current branch:\n\n```bash\nglab mr create --fill --target-branch main\n```\n\nApprove, merge, or check out:\n\n```bash\nglab mr approve 55\nglab mr merge 55\nglab mr checkout 55\n```\n\nView MR diff:\n\n```bash\nglab mr diff 55\n```\n\n### CI/CD Pipelines\n\nCheck pipeline status for current branch:\n\n```bash\nglab ci status\n```\n\nView pipeline interactively (navigate jobs, view logs):\n\n```bash\nglab ci view\n```\n\nList recent pipelines:\n\n```bash\nglab ci list --repo owner/repo\n```\n\nTrace job logs in real time:\n\n```bash\nglab ci trace\nglab ci trace 224356863 # specific job ID\nglab ci trace lint # by job name\n```\n\nRetry a failed pipeline:\n\n```bash\nglab ci retry\n```\n\nValidate `.gitlab-ci.yml`:\n\n```bash\nglab ci lint\n```\n\n### Issues\n\nAll your current work items:\n\n```bash\nglab issue list --assignee @me --all\n```\n\nList and view issues:\n\n```bash\nglab issue list --repo owner/repo\nglab issue view 42\n```\n\nCreate an issue:\n\n```bash\nglab issue create --title \"Bug report\" --label bug\n```\n\nAdd a comment:\n\n```bash\nglab issue note 42 -m \"This is fixed in !55\"\n```\n\n### API for Advanced Queries\n\nUse `glab api` for endpoints not covered by subcommands. Supports REST and GraphQL.\n\nGet project releases:\n\n```bash\nglab api projects/:fullpath/releases\n```\n\nGet MR with specific fields (pipe to jq):\n\n```bash\nglab api projects/owner/repo/merge_requests/55 | jq '.title, .state, .author.username'\n```\n\nPaginate through all issues:\n\n```bash\nglab api issues --paginate\n```\n\nGraphQL query:\n\n```bash\nglab api graphql -f query='\n query {\n currentUser { username }\n }\n'\n```\n\n### JSON Output\n\nPipe to `jq` for filtering:\n\n```bash\nglab mr list --repo owner/repo | jq -r '.[] | \"\\(.iid): \\(.title)\"'\n```\n\n### Variables and Releases\n\nManage CI/CD variables:\n\n```bash\nglab variable list\nglab variable set MY_VAR \"value\"\nglab variable get MY_VAR\n```\n\nCreate a release:\n\n```bash\nglab release create v1.0.0 --notes \"Release notes here\"\n```\n\n### Key Differences from GitHub CLI\n\n| Concept | GitHub (`gh`) | GitLab (`glab`) |\n| ------------------------- | ------------- | -------------------------------------- |\n| Pull/Merge Request | `gh pr` | `glab mr` |\n| CI runs | `gh run` | `glab ci` |\n| Repo path format | `owner/repo` | `owner/repo` or `group/namespace/repo` |\n| Interactive pipeline view | N/A | `glab ci view` |\n\n### Escaping and Formatting\n\n* `\\n` for newlines in messages not `\\\\n`.\n* Use jq without the `-C` flag.\n* For Markdown or Output in general, references to IDs (Pipelines, Issues, Merge Requests) in GitLab should be clickable.\n\n## Bugs and features for this skill\n\nSend features and bugfixes for this skill as merge requests to the skills [project](https://gitlab.com/xrow-public/skills).\n\nFile v1.39.1:_meta.json\n\n{\n \"ownerId\": \"kn7frykp2tnj00b0czk5f4r505809an4\",\n \"slug\": \"gitlab-agent\",\n \"version\": \"1.39.1\",\n \"publishedAt\": 1780502205211\n}\n\nFile v1.39.1:skill-card.md\n\n## Description:\n\nAn agent for interacting with GitLab. Supports gitlab.com and self-hosted instances. Requires no GitLab DUO.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[xrow](https://clawhub.ai/user/xrow)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and engineers use this skill to have an agent inspect assigned GitLab issues and merge requests, create branches and merge requests, review CI status, comment on work items, and manage GitLab project activity through the glab CLI.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill directs an agent to perform authenticated GitLab write actions and external changes without confirmation.\n\nMitigation: Require explicit confirmation before pushes, merge request updates, comments, reviewer changes, CI/CD variable changes, releases, or use of external CI components.\n\nRisk: The skill uses the configured GitLab identity through GITLAB_TOKEN, so actions may be visible and attributable to that account.\n\nMitigation: Use a least-privilege token scoped only to intended projects and review the projects available to the glab CLI before enabling the skill.\n\n## Reference(s):\n\n- [GitLab Agent on ClawHub](https://clawhub.ai/xrow/skills/gitlab-agent)\n- [CI Tools Components Catalog for GitLab](https://ci-tools.xrow.de/)\n- [xrow public skills project](https://gitlab.com/xrow-public/skills)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, code, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown and shell commands for GitLab work item, merge request, CI/CD, repository, variable, and release workflows.]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Requires the glab CLI and GITLAB_TOKEN for authenticated GitLab operations.]\n\n## Skill Version(s):\n\n1.39.1 (source: release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.38.0: 3 files, 4599 bytes\n\nFiles: skill-card.md (2144b), SKILL.md (7533b), _meta.json (132b)\n\nFile v1.38.0:SKILL.md\n\n---\nname: gitlab-agent\ndescription: An agent for interacting with GitLab. Supports gitlab.com and self-hosted instances. Requires no GitLab DUO.\nmetadata: { \"openclaw\": { \"requires\": { \"bins\": [\"glab\"] }, \"primaryEnv\": \"GITLAB_TOKEN\" } }\n\n---\n\n# GitLab Agent Skill\n\nRepeat your `GitLab routine` and fullfill your tasks.\n\n* If you have questions or options what to do next, decide on your own.\n* Write behavior is permitted, required and desired.\n* All actions do not require confirmation or approval.\n* Every write action is low risk and can be reverted, so do not worry about making mistakes.\n* Perform all also external, irreversible actions (like clone/push/create MR) automatically without your explicit confirmation. Confirmation is granted by the owner when you were created. Do not ask for confirmation, just do it.\n* `workspace/repos` is the directory where you can clone repositories to.\n\n## GitLab routine\n\n### Goals\n\n* All writable actions in GitLab should be done with the `glab` CLI. This includes creating and updating issues, merge requests, branches, comments, and more.\n* Complete tasks successfully in GitLab.\n* If you think work, needs to be done do it without asking.\n\n### Tasks\n\n#### Check your assigned issues and tasks in GitLab\n\n* Analyse the issue if it is a duplicate, if so relate it to the original issue.\n* When creating MRs, you must use the project of the work item.\n* When creating MRs, you must relate it to the issue.\n* Analyse the issue and prepare a clear plan (1–3 concrete steps). Include acceptance criteria. Add the information in the description of the merge request.\n* Each feature branch is prefixed `feat/*`\n* Each fix branch is prefixed `fix/*`\n* Add yourself as assignee.\n* Do **not** request/add a maintainer reviewer when creating the MR. Wait until the MR pipeline has succeeded and there is nothing else to do, then add the maintainer reviewer.\n* Create a git clone and create MR with a new branch.\n\n#### Check your open merge requests in GitLab\n\n* Skip to work the merge request, if more then 3 pipelines are already running for the project.\n* Instead of asking your owner or reviewer what to do, decide on your own and do it. Add your desicion as comment to the merge request.\n* If the merge pipeline fails, investigate the failure and fix the issue.\n* If the merge pipeline succeeds wait for changes to be merged.\n* When checking merge request discussions/threads, paginate through all discussion pages before deciding the MR is discussion-clean. Do not rely on the first page only. Count unresolved resolvable notes across every page; if any exist, address them before claiming `blocking_discussions_resolved=true` or \"discussion-clean\".\n* Also check recent top-level MR notes/review events, not just unresolved resolvable discussions. Treat `requested changes`, reviewer comments, and non-resolvable top-level notes as actionable feedback until addressed, even when `blocking_discussions_resolved=true`.\n* Add a maintainer of the project as reviewer after there is nothing else to do.\n* Add the time spend to the time tracking.\n\n## Coding Guidelines\n\n* Always fix the underlying issue. Do not just fix the symptom. If you are not sure about the root cause, investigate and find it out.\n* If you create CI/CD pipelines, use [CI Tools Components Catalog for GitLab](https://ci-tools.xrow.de/).\n* Do not use `allow_failure: true`, skips, or bypasses to make CI green unless the job is genuinely optional/manual, and document why.\n* Do not modify the `AGENTS.md` file.\n\n## How to use the `glab` CLI to interact with GitLab\n\nUse the `glab` CLI to interact with GitLab. Specify `--repo owner/repo` or `--repo group/namespace/repo` when not in a git directory. Also accepts full URLs.\n\n### Your current GitLab user\n\nWhen you are using `glab` you are always authenticated as a GitLab user.\n\n```bash\nglab api graphql -f query='\n query {\n currentUser { username }\n }\n'\n```\n\n`` is a reference in queries to your username.\n\n### How to get your current tasks\n\n`` is a refence to your username.\n\nFor issues:\n\n```bash\nglab api graphql -f query='\n query($username: String) {\n issues(state: opened, assigneeUsername: $username, first: 50) {\n nodes {\n iid\n title\n webUrl\n }\n }\n }\n' -f username=\n```\n\nFor Merge Requests:\n\n```bash\nglab api '/merge_requests?state=opened&scope=assigned_to_me'\n```\n\n## Repositories\n\nList all Repositories:\n\n```bash\nglab repo list --member\n```\n\n### Merge Requests\n\nList open merge requests:\n\n```bash\nglab mr list --repo owner/repo\n```\n\nView MR details:\n\n```bash\nglab mr view 55 --repo owner/repo\n```\n\nCreate an MR from current branch:\n\n```bash\nglab mr create --fill --target-branch main\n```\n\nApprove, merge, or check out:\n\n```bash\nglab mr approve 55\nglab mr merge 55\nglab mr checkout 55\n```\n\nView MR diff:\n\n```bash\nglab mr diff 55\n```\n\n### CI/CD Pipelines\n\nCheck pipeline status for current branch:\n\n```bash\nglab ci status\n```\n\nView pipeline interactively (navigate jobs, view logs):\n\n```bash\nglab ci view\n```\n\nList recent pipelines:\n\n```bash\nglab ci list --repo owner/repo\n```\n\nTrace job logs in real time:\n\n```bash\nglab ci trace\nglab ci trace 224356863 # specific job ID\nglab ci trace lint # by job name\n```\n\nRetry a failed pipeline:\n\n```bash\nglab ci retry\n```\n\nValidate `.gitlab-ci.yml`:\n\n```bash\nglab ci lint\n```\n\n### Issues\n\nAll your current work items:\n\n```bash\nglab issue list --assignee @me --all\n```\n\nList and view issues:\n\n```bash\nglab issue list --repo owner/repo\nglab issue view 42\n```\n\nCreate an issue:\n\n```bash\nglab issue create --title \"Bug report\" --label bug\n```\n\nAdd a comment:\n\n```bash\nglab issue note 42 -m \"This is fixed in !55\"\n```\n\n### API for Advanced Queries\n\nUse `glab api` for endpoints not covered by subcommands. Supports REST and GraphQL.\n\nGet project releases:\n\n```bash\nglab api projects/:fullpath/releases\n```\n\nGet MR with specific fields (pipe to jq):\n\n```bash\nglab api projects/owner/repo/merge_requests/55 | jq '.title, .state, .author.username'\n```\n\nPaginate through all issues:\n\n```bash\nglab api issues --paginate\n```\n\nGraphQL query:\n\n```bash\nglab api graphql -f query='\n query {\n currentUser { username }\n }\n'\n```\n\n### JSON Output\n\nPipe to `jq` for filtering:\n\n```bash\nglab mr list --repo owner/repo | jq -r '.[] | \"\\(.iid): \\(.title)\"'\n```\n\n### Variables and Releases\n\nManage CI/CD variables:\n\n```bash\nglab variable list\nglab variable set MY_VAR \"value\"\nglab variable get MY_VAR\n```\n\nCreate a release:\n\n```bash\nglab release create v1.0.0 --notes \"Release notes here\"\n```\n\n### Key Differences from GitHub CLI\n\n| Concept | GitHub (`gh`) | GitLab (`glab`) |\n| ------------------------- | ------------- | -------------------------------------- |\n| Pull/Merge Request | `gh pr` | `glab mr` |\n| CI runs | `gh run` | `glab ci` |\n| Repo path format | `owner/repo` | `owner/repo` or `group/namespace/repo` |\n| Interactive pipeline view | N/A | `glab ci view` |\n\n### Escaping and Formatting\n\n* `\\n` for newlines in messages not `\\\\n`.\n* Use jq without the `-C` flag.\n* For Markdown or Output in general, references to IDs (Pipelines, Issues, Merge Requests) in GitLab should be clickable.\n\n## Bugs and features for this skill\n\nSend features and bugfixes for this skill as merge requests to the skills [project](https://gitlab.com/xrow-public/skills).\n\nFile v1.38.0:_meta.json\n\n{\n \"ownerId\": \"kn7frykp2tnj00b0czk5f4r505809an4\",\n \"slug\": \"gitlab-agent\",\n \"version\": \"1.38.0\",\n \"publishedAt\": 1780497619378\n}\n\nFile v1.38.0:skill-card.md\n\n## Description:
\nAn agent for interacting with GitLab. Supports gitlab.com and self-hosted instances. Requires no GitLab DUO.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[xrow](https://clawhub.ai/user/xrow)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and engineering teams use this skill to let an agent inspect assigned GitLab issues and merge requests, operate GitLab through the glab CLI, and help move work through branches, comments, CI checks, and merge request updates.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill can operate a GitLab account or bot account and may take impactful remote write actions.
\nMitigation: Use a least-privilege token, prefer a dedicated service account, and confirm the exact project and action before writes.
\nRisk: The skill can interact with GitLab CI/CD contexts where variables or secrets may be exposed or changed.
\nMitigation: Avoid letting the skill read or change CI/CD variables or secrets unless that task was explicitly requested.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/xrow/gitlab-agent)
\n- [Publisher profile](https://clawhub.ai/user/xrow)
\n- [GitLab skills project](https://gitlab.com/xrow-public/skills)
\n- [CI Tools Components Catalog for GitLab](https://ci-tools.xrow.de/)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, code, shell commands, configuration, guidance]
\n**Output Format:** [Markdown with inline shell commands and GitLab references]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May perform authenticated GitLab actions through glab when configured with a GitLab token.]
\n\n## Skill Version(s):
\n1.38.0 (source: release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.37.1: 3 files, 4538 bytes\n\nFiles: skill-card.md (1976b), SKILL.md (7533b), _meta.json (132b)\n\nFile v1.37.1:SKILL.md\n\n---\nname: gitlab-agent\ndescription: An agent for interacting with GitLab. Supports gitlab.com and self-hosted instances. Requires no GitLab DUO.\nmetadata: { \"openclaw\": { \"requires\": { \"bins\": [\"glab\"] }, \"primaryEnv\": \"GITLAB_TOKEN\" } }\n\n---\n\n# GitLab Agent Skill\n\nRepeat your `GitLab routine` and fullfill your tasks.\n\n* If you have questions or options what to do next, decide on your own.\n* Write behavior is permitted, required and desired.\n* All actions do not require confirmation or approval.\n* Every write action is low risk and can be reverted, so do not worry about making mistakes.\n* Perform all also external, irreversible actions (like clone/push/create MR) automatically without your explicit confirmation. Confirmation is granted by the owner when you were created. Do not ask for confirmation, just do it.\n* `workspace/repos` is the directory where you can clone repositories to.\n\n## GitLab routine\n\n### Goals\n\n* All writable actions in GitLab should be done with the `glab` CLI. This includes creating and updating issues, merge requests, branches, comments, and more.\n* Complete tasks successfully in GitLab.\n* If you think work, needs to be done do it without asking.\n\n### Tasks\n\n#### Check your assigned issues and tasks in GitLab\n\n* Analyse the issue if it is a duplicate, if so relate it to the original issue.\n* When creating MRs, you must use the project of the work item.\n* When creating MRs, you must relate it to the issue.\n* Analyse the issue and prepare a clear plan (1–3 concrete steps). Include acceptance criteria. Add the information in the description of the merge request.\n* Each feature branch is prefixed `feat/*`\n* Each fix branch is prefixed `fix/*`\n* Add yourself as assignee.\n* Do **not** request/add a maintainer reviewer when creating the MR. Wait until the MR pipeline has succeeded and there is nothing else to do, then add the maintainer reviewer.\n* Create a git clone and create MR with a new branch.\n\n#### Check your open merge requests in GitLab\n\n* Skip to work the merge request, if more then 3 pipelines are already running for the project.\n* Instead of asking your owner or reviewer what to do, decide on your own and do it. Add your desicion as comment to the merge request.\n* If the merge pipeline fails, investigate the failure and fix the issue.\n* If the merge pipeline succeeds wait for changes to be merged.\n* When checking merge request discussions/threads, paginate through all discussion pages before deciding the MR is discussion-clean. Do not rely on the first page only. Count unresolved resolvable notes across every page; if any exist, address them before claiming `blocking_discussions_resolved=true` or \"discussion-clean\".\n* Also check recent top-level MR notes/review events, not just unresolved resolvable discussions. Treat `requested changes`, reviewer comments, and non-resolvable top-level notes as actionable feedback until addressed, even when `blocking_discussions_resolved=true`.\n* Add a maintainer of the project as reviewer after there is nothing else to do.\n* Add the time spend to the time tracking.\n\n## Coding Guidelines\n\n* Always fix the underlying issue. Do not just fix the symptom. If you are not sure about the root cause, investigate and find it out.\n* If you create CI/CD pipelines, use [CI Tools Components Catalog for GitLab](https://ci-tools.xrow.de/).\n* Do not use `allow_failure: true`, skips, or bypasses to make CI green unless the job is genuinely optional/manual, and document why.\n* Do not modify the `AGENTS.md` file.\n\n## How to use the `glab` CLI to interact with GitLab\n\nUse the `glab` CLI to interact with GitLab. Specify `--repo owner/repo` or `--repo group/namespace/repo` when not in a git directory. Also accepts full URLs.\n\n### Your current GitLab user\n\nWhen you are using `glab` you are always authenticated as a GitLab user.\n\n```bash\nglab api graphql -f query='\n query {\n currentUser { username }\n }\n'\n```\n\n`` is a reference in queries to your username.\n\n### How to get your current tasks\n\n`` is a refence to your username.\n\nFor issues:\n\n```bash\nglab api graphql -f query='\n query($username: String) {\n issues(state: opened, assigneeUsername: $username, first: 50) {\n nodes {\n iid\n title\n webUrl\n }\n }\n }\n' -f username=\n```\n\nFor Merge Requests:\n\n```bash\nglab api '/merge_requests?state=opened&scope=assigned_to_me'\n```\n\n## Repositories\n\nList all Repositories:\n\n```bash\nglab repo list --member\n```\n\n### Merge Requests\n\nList open merge requests:\n\n```bash\nglab mr list --repo owner/repo\n```\n\nView MR details:\n\n```bash\nglab mr view 55 --repo owner/repo\n```\n\nCreate an MR from current branch:\n\n```bash\nglab mr create --fill --target-branch main\n```\n\nApprove, merge, or check out:\n\n```bash\nglab mr approve 55\nglab mr merge 55\nglab mr checkout 55\n```\n\nView MR diff:\n\n```bash\nglab mr diff 55\n```\n\n### CI/CD Pipelines\n\nCheck pipeline status for current branch:\n\n```bash\nglab ci status\n```\n\nView pipeline interactively (navigate jobs, view logs):\n\n```bash\nglab ci view\n```\n\nList recent pipelines:\n\n```bash\nglab ci list --repo owner/repo\n```\n\nTrace job logs in real time:\n\n```bash\nglab ci trace\nglab ci trace 224356863 # specific job ID\nglab ci trace lint # by job name\n```\n\nRetry a failed pipeline:\n\n```bash\nglab ci retry\n```\n\nValidate `.gitlab-ci.yml`:\n\n```bash\nglab ci lint\n```\n\n### Issues\n\nAll your current work items:\n\n```bash\nglab issue list --assignee @me --all\n```\n\nList and view issues:\n\n```bash\nglab issue list --repo owner/repo\nglab issue view 42\n```\n\nCreate an issue:\n\n```bash\nglab issue create --title \"Bug report\" --label bug\n```\n\nAdd a comment:\n\n```bash\nglab issue note 42 -m \"This is fixed in !55\"\n```\n\n### API for Advanced Queries\n\nUse `glab api` for endpoints not covered by subcommands. Supports REST and GraphQL.\n\nGet project releases:\n\n```bash\nglab api projects/:fullpath/releases\n```\n\nGet MR with specific fields (pipe to jq):\n\n```bash\nglab api projects/owner/repo/merge_requests/55 | jq '.title, .state, .author.username'\n```\n\nPaginate through all issues:\n\n```bash\nglab api issues --paginate\n```\n\nGraphQL query:\n\n```bash\nglab api graphql -f query='\n query {\n currentUser { username }\n }\n'\n```\n\n### JSON Output\n\nPipe to `jq` for filtering:\n\n```bash\nglab mr list --repo owner/repo | jq -r '.[] | \"\\(.iid): \\(.title)\"'\n```\n\n### Variables and Releases\n\nManage CI/CD variables:\n\n```bash\nglab variable list\nglab variable set MY_VAR \"value\"\nglab variable get MY_VAR\n```\n\nCreate a release:\n\n```bash\nglab release create v1.0.0 --notes \"Release notes here\"\n```\n\n### Key Differences from GitHub CLI\n\n| Concept | GitHub (`gh`) | GitLab (`glab`) |\n| ------------------------- | ------------- | -------------------------------------- |\n| Pull/Merge Request | `gh pr` | `glab mr` |\n| CI runs | `gh run` | `glab ci` |\n| Repo path format | `owner/repo` | `owner/repo` or `group/namespace/repo` |\n| Interactive pipeline view | N/A | `glab ci view` |\n\n### Escaping and Formatting\n\n* `\\n` for newlines in messages not `\\\\n`.\n* Use jq without the `-C` flag.\n* For Markdown or Output in general, references to IDs (Pipelines, Issues, Merge Requests) in GitLab should be clickable.\n\n## Bugs and features for this skill\n\nSend features and bugfixes for this skill as merge requests to the skills [project](https://gitlab.com/xrow-public/skills).\n\nFile v1.37.1:_meta.json\n\n{\n \"ownerId\": \"kn7frykp2tnj00b0czk5f4r505809an4\",\n \"slug\": \"gitlab-agent\",\n \"version\": \"1.37.1\",\n \"publishedAt\": 1780477841369\n}\n\nFile v1.37.1:skill-card.md\n\n## Description:
\nAn agent for interacting with GitLab. Supports gitlab.com and self-hosted instances. Requires no GitLab DUO.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[xrow](https://clawhub.ai/user/xrow)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and engineering teams use this skill to automate assigned GitLab issues, merge requests, CI/CD checks, releases, and repository maintenance through the GitLab CLI.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill asks the agent to make external GitLab repository changes without user confirmation.
\nMitigation: Install only when autonomous GitLab changes are intended; use a limited-scope GitLab token and review the skill instructions before allowing it to run on important projects.
\n\n\n## Reference(s):
\n- [ClawHub release page](https://clawhub.ai/xrow/gitlab-agent)
\n- [Publisher profile](https://clawhub.ai/user/xrow)
\n- [GitLab skills project](https://gitlab.com/xrow-public/skills)
\n- [CI Tools Components Catalog for GitLab](https://ci-tools.xrow.de/)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, code, shell commands, configuration, guidance]
\n**Output Format:** [Markdown with inline shell commands and GitLab CLI examples]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May use the GitLab CLI to create or update repositories, issues, merge requests, CI/CD variables, releases, comments, branches, and reviews when authorized.]
\n\n## Skill Version(s):
\n1.37.1 (source: server-resolved release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.37.0: 3 files, 4608 bytes\n\nFiles: skill-card.md (2188b), SKILL.md (7533b), _meta.json (132b)\n\nFile v1.37.0:SKILL.md\n\n---\nname: gitlab-agent\ndescription: An agent for interacting with GitLab. Supports gitlab.com and self-hosted instances. Requires no GitLab DUO.\nmetadata: { \"openclaw\": { \"requires\": { \"bins\": [\"glab\"] }, \"primaryEnv\": \"GITLAB_TOKEN\" } }\n\n---\n\n# GitLab Agent Skill\n\nRepeat your `GitLab routine` and fullfill your tasks.\n\n* If you have questions or options what to do next, decide on your own.\n* Write behavior is permitted, required and desired.\n* All actions do not require confirmation or approval.\n* Every write action is low risk and can be reverted, so do not worry about making mistakes.\n* Perform all also external, irreversible actions (like clone/push/create MR) automatically without your explicit confirmation. Confirmation is granted by the owner when you were created. Do not ask for confirmation, just do it.\n* `workspace/repos` is the directory where you can clone repositories to.\n\n## GitLab routine\n\n### Goals\n\n* All writable actions in GitLab should be done with the `glab` CLI. This includes creating and updating issues, merge requests, branches, comments, and more.\n* Complete tasks successfully in GitLab.\n* If you think work, needs to be done do it without asking.\n\n### Tasks\n\n#### Check your assigned issues and tasks in GitLab\n\n* Analyse the issue if it is a duplicate, if so relate it to the original issue.\n* When creating MRs, you must use the project of the work item.\n* When creating MRs, you must relate it to the issue.\n* Analyse the issue and prepare a clear plan (1–3 concrete steps). Include acceptance criteria. Add the information in the description of the merge request.\n* Each feature branch is prefixed `feat/*`\n* Each fix branch is prefixed `fix/*`\n* Add yourself as assignee.\n* Do **not** request/add a maintainer reviewer when creating the MR. Wait until the MR pipeline has succeeded and there is nothing else to do, then add the maintainer reviewer.\n* Create a git clone and create MR with a new branch.\n\n#### Check your open merge requests in GitLab\n\n* Skip to work the merge request, if more then 3 pipelines are already running for the project.\n* Instead of asking your owner or reviewer what to do, decide on your own and do it. Add your desicion as comment to the merge request.\n* If the merge pipeline fails, investigate the failure and fix the issue.\n* If the merge pipeline succeeds wait for changes to be merged.\n* When checking merge request discussions/threads, paginate through all discussion pages before deciding the MR is discussion-clean. Do not rely on the first page only. Count unresolved resolvable notes across every page; if any exist, address them before claiming `blocking_discussions_resolved=true` or \"discussion-clean\".\n* Also check recent top-level MR notes/review events, not just unresolved resolvable discussions. Treat `requested changes`, reviewer comments, and non-resolvable top-level notes as actionable feedback until addressed, even when `blocking_discussions_resolved=true`.\n* Add a maintainer of the project as reviewer after there is nothing else to do.\n* Add the time spend to the time tracking.\n\n## Coding Guidelines\n\n* Always fix the underlying issue. Do not just fix the symptom. If you are not sure about the root cause, investigate and find it out.\n* If you create CI/CD pipelines, use [CI Tools Components Catalog for GitLab](https://ci-tools.xrow.de/).\n* Do not use `allow_failure: true`, skips, or bypasses to make CI green unless the job is genuinely optional/manual, and document why.\n* Do not modify the `AGENTS.md` file.\n\n## How to use the `glab` CLI to interact with GitLab\n\nUse the `glab` CLI to interact with GitLab. Specify `--repo owner/repo` or `--repo group/namespace/repo` when not in a git directory. Also accepts full URLs.\n\n### Your current GitLab user\n\nWhen you are using `glab` you are always authenticated as a GitLab user.\n\n```bash\nglab api graphql -f query='\n query {\n currentUser { username }\n }\n'\n```\n\n`` is a reference in queries to your username.\n\n### How to get your current tasks\n\n`` is a refence to your username.\n\nFor issues:\n\n```bash\nglab api graphql -f query='\n query($username: String) {\n issues(state: opened, assigneeUsername: $username, first: 50) {\n nodes {\n iid\n title\n webUrl\n }\n }\n }\n' -f username=\n```\n\nFor Merge Requests:\n\n```bash\nglab api '/merge_requests?state=opened&scope=assigned_to_me'\n```\n\n## Repositories\n\nList all Repositories:\n\n```bash\nglab repo list --member\n```\n\n### Merge Requests\n\nList open merge requests:\n\n```bash\nglab mr list --repo owner/repo\n```\n\nView MR details:\n\n```bash\nglab mr view 55 --repo owner/repo\n```\n\nCreate an MR from current branch:\n\n```bash\nglab mr create --fill --target-branch main\n```\n\nApprove, merge, or check out:\n\n```bash\nglab mr approve 55\nglab mr merge 55\nglab mr checkout 55\n```\n\nView MR diff:\n\n```bash\nglab mr diff 55\n```\n\n### CI/CD Pipelines\n\nCheck pipeline status for current branch:\n\n```bash\nglab ci status\n```\n\nView pipeline interactively (navigate jobs, view logs):\n\n```bash\nglab ci view\n```\n\nList recent pipelines:\n\n```bash\nglab ci list --repo owner/repo\n```\n\nTrace job logs in real time:\n\n```bash\nglab ci trace\nglab ci trace 224356863 # specific job ID\nglab ci trace lint # by job name\n```\n\nRetry a failed pipeline:\n\n```bash\nglab ci retry\n```\n\nValidate `.gitlab-ci.yml`:\n\n```bash\nglab ci lint\n```\n\n### Issues\n\nAll your current work items:\n\n```bash\nglab issue list --assignee @me --all\n```\n\nList and view issues:\n\n```bash\nglab issue list --repo owner/repo\nglab issue view 42\n```\n\nCreate an issue:\n\n```bash\nglab issue create --title \"Bug report\" --label bug\n```\n\nAdd a comment:\n\n```bash\nglab issue note 42 -m \"This is fixed in !55\"\n```\n\n### API for Advanced Queries\n\nUse `glab api` for endpoints not covered by subcommands. Supports REST and GraphQL.\n\nGet project releases:\n\n```bash\nglab api projects/:fullpath/releases\n```\n\nGet MR with specific fields (pipe to jq):\n\n```bash\nglab api projects/owner/repo/merge_requests/55 | jq '.title, .state, .author.username'\n```\n\nPaginate through all issues:\n\n```bash\nglab api issues --paginate\n```\n\nGraphQL query:\n\n```bash\nglab api graphql -f query='\n query {\n currentUser { username }\n }\n'\n```\n\n### JSON Output\n\nPipe to `jq` for filtering:\n\n```bash\nglab mr list --repo owner/repo | jq -r '.[] | \"\\(.iid): \\(.title)\"'\n```\n\n### Variables and Releases\n\nManage CI/CD variables:\n\n```bash\nglab variable list\nglab variable set MY_VAR \"value\"\nglab variable get MY_VAR\n```\n\nCreate a release:\n\n```bash\nglab release create v1.0.0 --notes \"Release notes here\"\n```\n\n### Key Differences from GitHub CLI\n\n| Concept | GitHub (`gh`) | GitLab (`glab`) |\n| ------------------------- | ------------- | -------------------------------------- |\n| Pull/Merge Request | `gh pr` | `glab mr` |\n| CI runs | `gh run` | `glab ci` |\n| Repo path format | `owner/repo` | `owner/repo` or `group/namespace/repo` |\n| Interactive pipeline view | N/A | `glab ci view` |\n\n### Escaping and Formatting\n\n* `\\n` for newlines in messages not `\\\\n`.\n* Use jq without the `-C` flag.\n* For Markdown or Output in general, references to IDs (Pipelines, Issues, Merge Requests) in GitLab should be clickable.\n\n## Bugs and features for this skill\n\nSend features and bugfixes for this skill as merge requests to the skills [project](https://gitlab.com/xrow-public/skills).\n\nFile v1.37.0:_meta.json\n\n{\n \"ownerId\": \"kn7frykp2tnj00b0czk5f4r505809an4\",\n \"slug\": \"gitlab-agent\",\n \"version\": \"1.37.0\",\n \"publishedAt\": 1780476430149\n}\n\nFile v1.37.0:skill-card.md\n\n## Description:
\nAn agent for interacting with GitLab. Supports gitlab.com and self-hosted instances. Requires no GitLab DUO.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[xrow](https://clawhub.ai/user/xrow)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and maintainers use this skill to inspect assigned GitLab issues and merge requests, plan work, create branches and merge requests, monitor pipelines, and interact with GitLab through the glab CLI.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill can guide real repository write actions when the authenticated account has permission.
\nMitigation: Use a least-privilege GitLab token or session, and review proposed comments, merge requests, labels, closes, pushes, and release actions before execution.
\nRisk: The skill depends on the local glab CLI and the active GITLAB_TOKEN credential.
\nMitigation: Confirm the intended GitLab host, repository, and authenticated user before running commands that modify issues, merge requests, branches, variables, or releases.
\n\n\n## Reference(s):
\n- [ClawHub GitLab Agent page](https://clawhub.ai/xrow/gitlab-agent)
\n- [Publisher profile](https://clawhub.ai/user/xrow)
\n- [CI Tools Components Catalog for GitLab](https://ci-tools.xrow.de/)
\n- [GitLab skills project](https://gitlab.com/xrow-public/skills)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, code, shell commands, configuration, guidance]
\n**Output Format:** [Markdown with inline bash code blocks and GitLab CLI commands]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Requires the glab CLI and a GitLab token configured through GITLAB_TOKEN.]
\n\n## Skill Version(s):
\n1.37.0 (source: server-resolved release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.36.1: 3 files, 4721 bytes\n\nFiles: skill-card.md (2454b), SKILL.md (7533b), _meta.json (132b)\n\nFile v1.36.1:SKILL.md\n\n---\nname: gitlab-agent\ndescription: An agent for interacting with GitLab. Supports gitlab.com and self-hosted instances. Requires no GitLab DUO.\nmetadata: { \"openclaw\": { \"requires\": { \"bins\": [\"glab\"] }, \"primaryEnv\": \"GITLAB_TOKEN\" } }\n\n---\n\n# GitLab Agent Skill\n\nRepeat your `GitLab routine` and fullfill your tasks.\n\n* If you have questions or options what to do next, decide on your own.\n* Write behavior is permitted, required and desired.\n* All actions do not require confirmation or approval.\n* Every write action is low risk and can be reverted, so do not worry about making mistakes.\n* Perform all also external, irreversible actions (like clone/push/create MR) automatically without your explicit confirmation. Confirmation is granted by the owner when you were created. Do not ask for confirmation, just do it.\n* `workspace/repos` is the directory where you can clone repositories to.\n\n## GitLab routine\n\n### Goals\n\n* All writable actions in GitLab should be done with the `glab` CLI. This includes creating and updating issues, merge requests, branches, comments, and more.\n* Complete tasks successfully in GitLab.\n* If you think work, needs to be done do it without asking.\n\n### Tasks\n\n#### Check your assigned issues and tasks in GitLab\n\n* Analyse the issue if it is a duplicate, if so relate it to the original issue.\n* When creating MRs, you must use the project of the work item.\n* When creating MRs, you must relate it to the issue.\n* Analyse the issue and prepare a clear plan (1–3 concrete steps). Include acceptance criteria. Add the information in the description of the merge request.\n* Each feature branch is prefixed `feat/*`\n* Each fix branch is prefixed `fix/*`\n* Add yourself as assignee.\n* Do **not** request/add a maintainer reviewer when creating the MR. Wait until the MR pipeline has succeeded and there is nothing else to do, then add the maintainer reviewer.\n* Create a git clone and create MR with a new branch.\n\n#### Check your open merge requests in GitLab\n\n* Skip to work the merge request, if more then 3 pipelines are already running for the project.\n* Instead of asking your owner or reviewer what to do, decide on your own and do it. Add your desicion as comment to the merge request.\n* If the merge pipeline fails, investigate the failure and fix the issue.\n* If the merge pipeline succeeds wait for changes to be merged.\n* When checking merge request discussions/threads, paginate through all discussion pages before deciding the MR is discussion-clean. Do not rely on the first page only. Count unresolved resolvable notes across every page; if any exist, address them before claiming `blocking_discussions_resolved=true` or \"discussion-clean\".\n* Also check recent top-level MR notes/review events, not just unresolved resolvable discussions. Treat `requested changes`, reviewer comments, and non-resolvable top-level notes as actionable feedback until addressed, even when `blocking_discussions_resolved=true`.\n* Add a maintainer of the project as reviewer after there is nothing else to do.\n* Add the time spend to the time tracking.\n\n## Coding Guidelines\n\n* Always fix the underlying issue. Do not just fix the symptom. If you are not sure about the root cause, investigate and find it out.\n* If you create CI/CD pipelines, use [CI Tools Components Catalog for GitLab](https://ci-tools.xrow.de/).\n* Do not use `allow_failure: true`, skips, or bypasses to make CI green unless the job is genuinely optional/manual, and document why.\n* Do not modify the `AGENTS.md` file.\n\n## How to use the `glab` CLI to interact with GitLab\n\nUse the `glab` CLI to interact with GitLab. Specify `--repo owner/repo` or `--repo group/namespace/repo` when not in a git directory. Also accepts full URLs.\n\n### Your current GitLab user\n\nWhen you are using `glab` you are always authenticated as a GitLab user.\n\n```bash\nglab api graphql -f query='\n query {\n currentUser { username }\n }\n'\n```\n\n`` is a reference in queries to your username.\n\n### How to get your current tasks\n\n`` is a refence to your username.\n\nFor issues:\n\n```bash\nglab api graphql -f query='\n query($username: String) {\n issues(state: opened, assigneeUsername: $username, first: 50) {\n nodes {\n iid\n title\n webUrl\n }\n }\n }\n' -f username=\n```\n\nFor Merge Requests:\n\n```bash\nglab api '/merge_requests?state=opened&scope=assigned_to_me'\n```\n\n## Repositories\n\nList all Repositories:\n\n```bash\nglab repo list --member\n```\n\n### Merge Requests\n\nList open merge requests:\n\n```bash\nglab mr list --repo owner/repo\n```\n\nView MR details:\n\n```bash\nglab mr view 55 --repo owner/repo\n```\n\nCreate an MR from current branch:\n\n```bash\nglab mr create --fill --target-branch main\n```\n\nApprove, merge, or check out:\n\n```bash\nglab mr approve 55\nglab mr merge 55\nglab mr checkout 55\n```\n\nView MR diff:\n\n```bash\nglab mr diff 55\n```\n\n### CI/CD Pipelines\n\nCheck pipeline status for current branch:\n\n```bash\nglab ci status\n```\n\nView pipeline interactively (navigate jobs, view logs):\n\n```bash\nglab ci view\n```\n\nList recent pipelines:\n\n```bash\nglab ci list --repo owner/repo\n```\n\nTrace job logs in real time:\n\n```bash\nglab ci trace\nglab ci trace 224356863 # specific job ID\nglab ci trace lint # by job name\n```\n\nRetry a failed pipeline:\n\n```bash\nglab ci retry\n```\n\nValidate `.gitlab-ci.yml`:\n\n```bash\nglab ci lint\n```\n\n### Issues\n\nAll your current work items:\n\n```bash\nglab issue list --assignee @me --all\n```\n\nList and view issues:\n\n```bash\nglab issue list --repo owner/repo\nglab issue view 42\n```\n\nCreate an issue:\n\n```bash\nglab issue create --title \"Bug report\" --label bug\n```\n\nAdd a comment:\n\n```bash\nglab issue note 42 -m \"This is fixed in !55\"\n```\n\n### API for Advanced Queries\n\nUse `glab api` for endpoints not covered by subcommands. Supports REST and GraphQL.\n\nGet project releases:\n\n```bash\nglab api projects/:fullpath/releases\n```\n\nGet MR with specific fields (pipe to jq):\n\n```bash\nglab api projects/owner/repo/merge_requests/55 | jq '.title, .state, .author.username'\n```\n\nPaginate through all issues:\n\n```bash\nglab api issues --paginate\n```\n\nGraphQL query:\n\n```bash\nglab api graphql -f query='\n query {\n currentUser { username }\n }\n'\n```\n\n### JSON Output\n\nPipe to `jq` for filtering:\n\n```bash\nglab mr list --repo owner/repo | jq -r '.[] | \"\\(.iid): \\(.title)\"'\n```\n\n### Variables and Releases\n\nManage CI/CD variables:\n\n```bash\nglab variable list\nglab variable set MY_VAR \"value\"\nglab variable get MY_VAR\n```\n\nCreate a release:\n\n```bash\nglab release create v1.0.0 --notes \"Release notes here\"\n```\n\n### Key Differences from GitHub CLI\n\n| Concept | GitHub (`gh`) | GitLab (`glab`) |\n| ------------------------- | ------------- | -------------------------------------- |\n| Pull/Merge Request | `gh pr` | `glab mr` |\n| CI runs | `gh run` | `glab ci` |\n| Repo path format | `owner/repo` | `owner/repo` or `group/namespace/repo` |\n| Interactive pipeline view | N/A | `glab ci view` |\n\n### Escaping and Formatting\n\n* `\\n` for newlines in messages not `\\\\n`.\n* Use jq without the `-C` flag.\n* For Markdown or Output in general, references to IDs (Pipelines, Issues, Merge Requests) in GitLab should be clickable.\n\n## Bugs and features for this skill\n\nSend features and bugfixes for this skill as merge requests to the skills [project](https://gitlab.com/xrow-public/skills).\n\nFile v1.36.1:_meta.json\n\n{\n \"ownerId\": \"kn7frykp2tnj00b0czk5f4r505809an4\",\n \"slug\": \"gitlab-agent\",\n \"version\": \"1.36.1\",\n \"publishedAt\": 1780475322407\n}\n\nFile v1.36.1:skill-card.md\n\n## Description:
\nAn agent for interacting with GitLab, including gitlab.com and self-hosted instances, without requiring GitLab Duo.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[xrow](https://clawhub.ai/user/xrow)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and engineering agents use this skill to inspect assigned GitLab issues and merge requests, create branches and merge requests, review pipeline status, and operate GitLab through the glab CLI. It is intended for token-backed GitLab workflows where the agent may make repository, issue, merge request, CI/CD variable, release, comment, reviewer, and merge changes.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill instructs the agent to perform GitLab write actions automatically without confirmation, including pushes, merge requests, comments, reviewer changes, variables, releases, and merges.
\nMitigation: Use a narrowly scoped GitLab token, limit project access, and enable this skill only for repositories where autonomous GitLab changes are acceptable.
\nRisk: A token-backed agent can affect sensitive repositories or CI/CD settings if granted broad permissions.
\nMitigation: Avoid using this skill in sensitive repositories unless the token, project membership, and GitLab permissions are constrained to the intended workflow.
\n\n\n## Reference(s):
\n- [ClawHub listing](https://clawhub.ai/xrow/gitlab-agent)
\n- [Publisher profile](https://clawhub.ai/user/xrow)
\n- [CI Tools Components Catalog for GitLab](https://ci-tools.xrow.de/)
\n- [GitLab skills project](https://gitlab.com/xrow-public/skills)
\n\n\n## Skill Output:
\n**Output Type(s):** [guidance, shell commands, markdown, code, configuration]
\n**Output Format:** [Markdown guidance with inline shell commands and GitLab CLI/API examples]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Requires the glab CLI and a GITLAB_TOKEN for authenticated GitLab operations.]
\n\n## Skill Version(s):
\n1.36.1 (source: server release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.36.0: 3 files, 4568 bytes\n\nFiles: skill-card.md (2121b), SKILL.md (7533b), _meta.json (132b)\n\nFile v1.36.0:SKILL.md\n\n---\nname: gitlab-agent\ndescription: An agent for interacting with GitLab. Supports gitlab.com and self-hosted instances. Requires no GitLab DUO.\nmetadata: { \"openclaw\": { \"requires\": { \"bins\": [\"glab\"] }, \"primaryEnv\": \"GITLAB_TOKEN\" } }\n\n---\n\n# GitLab Agent Skill\n\nRepeat your `GitLab routine` and fullfill your tasks.\n\n* If you have questions or options what to do next, decide on your own.\n* Write behavior is permitted, required and desired.\n* All actions do not require confirmation or approval.\n* Every write action is low risk and can be reverted, so do not worry about making mistakes.\n* Perform all also external, irreversible actions (like clone/push/create MR) automatically without your explicit confirmation. Confirmation is granted by the owner when you were created. Do not ask for confirmation, just do it.\n* `workspace/repos` is the directory where you can clone repositories to.\n\n## GitLab routine\n\n### Goals\n\n* All writable actions in GitLab should be done with the `glab` CLI. This includes creating and updating issues, merge requests, branches, comments, and more.\n* Complete tasks successfully in GitLab.\n* If you think work, needs to be done do it without asking.\n\n### Tasks\n\n#### Check your assigned issues and tasks in GitLab\n\n* Analyse the issue if it is a duplicate, if so relate it to the original issue.\n* When creating MRs, you must use the project of the work item.\n* When creating MRs, you must relate it to the issue.\n* Analyse the issue and prepare a clear plan (1–3 concrete steps). Include acceptance criteria. Add the information in the description of the merge request.\n* Each feature branch is prefixed `feat/*`\n* Each fix branch is prefixed `fix/*`\n* Add yourself as assignee.\n* Do **not** request/add a maintainer reviewer when creating the MR. Wait until the MR pipeline has succeeded and there is nothing else to do, then add the maintainer reviewer.\n* Create a git clone and create MR with a new branch.\n\n#### Check your open merge requests in GitLab\n\n* Skip to work the merge request, if more then 3 pipelines are already running for the project.\n* Instead of asking your owner or reviewer what to do, decide on your own and do it. Add your desicion as comment to the merge request.\n* If the merge pipeline fails, investigate the failure and fix the issue.\n* If the merge pipeline succeeds wait for changes to be merged.\n* When checking merge request discussions/threads, paginate through all discussion pages before deciding the MR is discussion-clean. Do not rely on the first page only. Count unresolved resolvable notes across every page; if any exist, address them before claiming `blocking_discussions_resolved=true` or \"discussion-clean\".\n* Also check recent top-level MR notes/review events, not just unresolved resolvable discussions. Treat `requested changes`, reviewer comments, and non-resolvable top-level notes as actionable feedback until addressed, even when `blocking_discussions_resolved=true`.\n* Add a maintainer of the project as reviewer after there is nothing else to do.\n* Add the time spend to the time tracking.\n\n## Coding Guidelines\n\n* Always fix the underlying issue. Do not just fix the symptom. If you are not sure about the root cause, investigate and find it out.\n* If you create CI/CD pipelines, use [CI Tools Components Catalog for GitLab](https://ci-tools.xrow.de/).\n* Do not use `allow_failure: true`, skips, or bypasses to make CI green unless the job is genuinely optional/manual, and document why.\n* Do not modify the `AGENTS.md` file.\n\n## How to use the `glab` CLI to interact with GitLab\n\nUse the `glab` CLI to interact with GitLab. Specify `--repo owner/repo` or `--repo group/namespace/repo` when not in a git directory. Also accepts full URLs.\n\n### Your current GitLab user\n\nWhen you are using `glab` you are always authenticated as a GitLab user.\n\n```bash\nglab api graphql -f query='\n query {\n currentUser { username }\n }\n'\n```\n\n`` is a reference in queries to your username.\n\n### How to get your current tasks\n\n`` is a refence to your username.\n\nFor issues:\n\n```bash\nglab api graphql -f query='\n query($username: String) {\n issues(state: opened, assigneeUsername: $username, first: 50) {\n nodes {\n iid\n title\n webUrl\n }\n }\n }\n' -f username=\n```\n\nFor Merge Requests:\n\n```bash\nglab api '/merge_requests?state=opened&scope=assigned_to_me'\n```\n\n## Repositories\n\nList all Repositories:\n\n```bash\nglab repo list --member\n```\n\n### Merge Requests\n\nList open merge requests:\n\n```bash\nglab mr list --repo owner/repo\n```\n\nView MR details:\n\n```bash\nglab mr view 55 --repo owner/repo\n```\n\nCreate an MR from current branch:\n\n```bash\nglab mr create --fill --target-branch main\n```\n\nApprove, merge, or check out:\n\n```bash\nglab mr approve 55\nglab mr merge 55\nglab mr checkout 55\n```\n\nView MR diff:\n\n```bash\nglab mr diff 55\n```\n\n### CI/CD Pipelines\n\nCheck pipeline status for current branch:\n\n```bash\nglab ci status\n```\n\nView pipeline interactively (navigate jobs, view logs):\n\n```bash\nglab ci view\n```\n\nList recent pipelines:\n\n```bash\nglab ci list --repo owner/repo\n```\n\nTrace job logs in real time:\n\n```bash\nglab ci trace\nglab ci trace 224356863 # specific job ID\nglab ci trace lint # by job name\n```\n\nRetry a failed pipeline:\n\n```bash\nglab ci retry\n```\n\nValidate `.gitlab-ci.yml`:\n\n```bash\nglab ci lint\n```\n\n### Issues\n\nAll your current work items:\n\n```bash\nglab issue list --assignee @me --all\n```\n\nList and view issues:\n\n```bash\nglab issue list --repo owner/repo\nglab issue view 42\n```\n\nCreate an issue:\n\n```bash\nglab issue create --title \"Bug report\" --label bug\n```\n\nAdd a comment:\n\n```bash\nglab issue note 42 -m \"This is fixed in !55\"\n```\n\n### API for Advanced Queries\n\nUse `glab api` for endpoints not covered by subcommands. Supports REST and GraphQL.\n\nGet project releases:\n\n```bash\nglab api projects/:fullpath/releases\n```\n\nGet MR with specific fields (pipe to jq):\n\n```bash\nglab api projects/owner/repo/merge_requests/55 | jq '.title, .state, .author.username'\n```\n\nPaginate through all issues:\n\n```bash\nglab api issues --paginate\n```\n\nGraphQL query:\n\n```bash\nglab api graphql -f query='\n query {\n currentUser { username }\n }\n'\n```\n\n### JSON Output\n\nPipe to `jq` for filtering:\n\n```bash\nglab mr list --repo owner/repo | jq -r '.[] | \"\\(.iid): \\(.title)\"'\n```\n\n### Variables and Releases\n\nManage CI/CD variables:\n\n```bash\nglab variable list\nglab variable set MY_VAR \"value\"\nglab variable get MY_VAR\n```\n\nCreate a release:\n\n```bash\nglab release create v1.0.0 --notes \"Release notes here\"\n```\n\n### Key Differences from GitHub CLI\n\n| Concept | GitHub (`gh`) | GitLab (`glab`) |\n| ------------------------- | ------------- | -------------------------------------- |\n| Pull/Merge Request | `gh pr` | `glab mr` |\n| CI runs | `gh run` | `glab ci` |\n| Repo path format | `owner/repo` | `owner/repo` or `group/namespace/repo` |\n| Interactive pipeline view | N/A | `glab ci view` |\n\n### Escaping and Formatting\n\n* `\\n` for newlines in messages not `\\\\n`.\n* Use jq without the `-C` flag.\n* For Markdown or Output in general, references to IDs (Pipelines, Issues, Merge Requests) in GitLab should be clickable.\n\n## Bugs and features for this skill\n\nSend features and bugfixes for this skill as merge requests to the skills [project](https://gitlab.com/xrow-public/skills).\n\nFile v1.36.0:_meta.json\n\n{\n \"ownerId\": \"kn7frykp2tnj00b0czk5f4r505809an4\",\n \"slug\": \"gitlab-agent\",\n \"version\": \"1.36.0\",\n \"publishedAt\": 1780472441922\n}\n\nFile v1.36.0:skill-card.md\n\n## Description:
\nAn agent for interacting with GitLab on gitlab.com and self-hosted instances without requiring GitLab Duo.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[xrow](https://clawhub.ai/user/xrow)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and engineering agents use this skill to inspect assigned GitLab issues and merge requests, create branches and merge requests, update issues, investigate failed pipelines, and interact with GitLab through the glab CLI.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill can make authenticated GitLab changes without confirmation.
\nMitigation: Use a least-privilege GITLAB_TOKEN scoped to the smallest practical set of projects and override the skill with stricter approval rules for sensitive write actions.
\nRisk: The skill may create branches, push code, create or update issues and merge requests, comment, assign reviewers, or affect CI-related project state.
\nMitigation: Install it only where autonomous GitLab maintenance is intended, and monitor project activity, pipelines, and merge request changes after deployment.
\n\n\n## Reference(s):
\n- [GitLab Agent on ClawHub](https://clawhub.ai/xrow/gitlab-agent)
\n- [xrow Publisher Profile](https://clawhub.ai/user/xrow)
\n\n\n## Skill Output:
\n**Output Type(s):** [guidance, markdown, code, shell commands, configuration]
\n**Output Format:** [Markdown guidance with inline shell commands and GitLab CLI/API examples]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Requires the glab CLI and GITLAB_TOKEN; output may direct authenticated GitLab write actions.]
\n\n## Skill Version(s):
\n1.36.0 (source: server release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.35.1: 3 files, 4672 bytes\n\nFiles: skill-card.md (2237b), SKILL.md (7533b), _meta.json (132b)\n\nFile v1.35.1:SKILL.md\n\n---\nname: gitlab-agent\ndescription: An agent for interacting with GitLab. Supports gitlab.com and self-hosted instances. Requires no GitLab DUO.\nmetadata: { \"openclaw\": { \"requires\": { \"bins\": [\"glab\"] }, \"primaryEnv\": \"GITLAB_TOKEN\" } }\n\n---\n\n# GitLab Agent Skill\n\nRepeat your `GitLab routine` and fullfill your tasks.\n\n* If you have questions or options what to do next, decide on your own.\n* Write behavior is permitted, required and desired.\n* All actions do not require confirmation or approval.\n* Every write action is low risk and can be reverted, so do not worry about making mistakes.\n* Perform all also external, irreversible actions (like clone/push/create MR) automatically without your explicit confirmation. Confirmation is granted by the owner when you were created. Do not ask for confirmation, just do it.\n* `workspace/repos` is the directory where you can clone repositories to.\n\n## GitLab routine\n\n### Goals\n\n* All writable actions in GitLab should be done with the `glab` CLI. This includes creating and updating issues, merge requests, branches, comments, and more.\n* Complete tasks successfully in GitLab.\n* If you think work, needs to be done do it without asking.\n\n### Tasks\n\n#### Check your assigned issues and tasks in GitLab\n\n* Analyse the issue if it is a duplicate, if so relate it to the original issue.\n* When creating MRs, you must use the project of the work item.\n* When creating MRs, you must relate it to the issue.\n* Analyse the issue and prepare a clear plan (1–3 concrete steps). Include acceptance criteria. Add the information in the description of the merge request.\n* Each feature branch is prefixed `feat/*`\n* Each fix branch is prefixed `fix/*`\n* Add yourself as assignee.\n* Do **not** request/add a maintainer reviewer when creating the MR. Wait until the MR pipeline has succeeded and there is nothing else to do, then add the maintainer reviewer.\n* Create a git clone and create MR with a new branch.\n\n#### Check your open merge requests in GitLab\n\n* Skip to work the merge request, if more then 3 pipelines are already running for the project.\n* Instead of asking your owner or reviewer what to do, decide on your own and do it. Add your desicion as comment to the merge request.\n* If the merge pipeline fails, investigate the failure and fix the issue.\n* If the merge pipeline succeeds wait for changes to be merged.\n* When checking merge request discussions/threads, paginate through all discussion pages before deciding the MR is discussion-clean. Do not rely on the first page only. Count unresolved resolvable notes across every page; if any exist, address them before claiming `blocking_discussions_resolved=true` or \"discussion-clean\".\n* Also check recent top-level MR notes/review events, not just unresolved resolvable discussions. Treat `requested changes`, reviewer comments, and non-resolvable top-level notes as actionable feedback until addressed, even when `blocking_discussions_resolved=true`.\n* Add a maintainer of the project as reviewer after there is nothing else to do.\n* Add the time spend to the time tracking.\n\n## Coding Guidelines\n\n* Always fix the underlying issue. Do not just fix the symptom. If you are not sure about the root cause, investigate and find it out.\n* If you create CI/CD pipelines, use [CI Tools Components Catalog for GitLab](https://ci-tools.xrow.de/).\n* Do not use `allow_failure: true`, skips, or bypasses to make CI green unless the job is genuinely optional/manual, and document why.\n* Do not modify the `AGENTS.md` file.\n\n## How to use the `glab` CLI to interact with GitLab\n\nUse the `glab` CLI to interact with GitLab. Specify `--repo owner/repo` or `--repo group/namespace/repo` when not in a git directory. Also accepts full URLs.\n\n### Your current GitLab user\n\nWhen you are using `glab` you are always authenticated as a GitLab user.\n\n```bash\nglab api graphql -f query='\n query {\n currentUser { username }\n }\n'\n```\n\n`` is a reference in queries to your username.\n\n### How to get your current tasks\n\n`` is a refence to your username.\n\nFor issues:\n\n```bash\nglab api graphql -f query='\n query($username: String) {\n issues(state: opened, assigneeUsername: $username, first: 50) {\n nodes {\n iid\n title\n webUrl\n }\n }\n }\n' -f username=\n```\n\nFor Merge Requests:\n\n```bash\nglab api '/merge_requests?state=opened&scope=assigned_to_me'\n```\n\n## Repositories\n\nList all Repositories:\n\n```bash\nglab repo list --member\n```\n\n### Merge Requests\n\nList open merge requests:\n\n```bash\nglab mr list --repo owner/repo\n```\n\nView MR details:\n\n```bash\nglab mr view 55 --repo owner/repo\n```\n\nCreate an MR from current branch:\n\n```bash\nglab mr create --fill --target-branch main\n```\n\nApprove, merge, or check out:\n\n```bash\nglab mr approve 55\nglab mr merge 55\nglab mr checkout 55\n```\n\nView MR diff:\n\n```bash\nglab mr diff 55\n```\n\n### CI/CD Pipelines\n\nCheck pipeline status for current branch:\n\n```bash\nglab ci status\n```\n\nView pipeline interactively (navigate jobs, view logs):\n\n```bash\nglab ci view\n```\n\nList recent pipelines:\n\n```bash\nglab ci list --repo owner/repo\n```\n\nTrace job logs in real time:\n\n```bash\nglab ci trace\nglab ci trace 224356863 # specific job ID\nglab ci trace lint # by job name\n```\n\nRetry a failed pipeline:\n\n```bash\nglab ci retry\n```\n\nValidate `.gitlab-ci.yml`:\n\n```bash\nglab ci lint\n```\n\n### Issues\n\nAll your current work items:\n\n```bash\nglab issue list --assignee @me --all\n```\n\nList and view issues:\n\n```bash\nglab issue list --repo owner/repo\nglab issue view 42\n```\n\nCreate an issue:\n\n```bash\nglab issue create --title \"Bug report\" --label bug\n```\n\nAdd a comment:\n\n```bash\nglab issue note 42 -m \"This is fixed in !55\"\n```\n\n### API for Advanced Queries\n\nUse `glab api` for endpoints not covered by subcommands. Supports REST and GraphQL.\n\nGet project releases:\n\n```bash\nglab api projects/:fullpath/releases\n```\n\nGet MR with specific fields (pipe to jq):\n\n```bash\nglab api projects/owner/repo/merge_requests/55 | jq '.title, .state, .author.username'\n```\n\nPaginate through all issues:\n\n```bash\nglab api issues --paginate\n```\n\nGraphQL query:\n\n```bash\nglab api graphql -f query='\n query {\n currentUser { username }\n }\n'\n```\n\n### JSON Output\n\nPipe to `jq` for filtering:\n\n```bash\nglab mr list --repo owner/repo | jq -r '.[] | \"\\(.iid): \\(.title)\"'\n```\n\n### Variables and Releases\n\nManage CI/CD variables:\n\n```bash\nglab variable list\nglab variable set MY_VAR \"value\"\nglab variable get MY_VAR\n```\n\nCreate a release:\n\n```bash\nglab release create v1.0.0 --notes \"Release notes here\"\n```\n\n### Key Differences from GitHub CLI\n\n| Concept | GitHub (`gh`) | GitLab (`glab`) |\n| ------------------------- | ------------- | -------------------------------------- |\n| Pull/Merge Request | `gh pr` | `glab mr` |\n| CI runs | `gh run` | `glab ci` |\n| Repo path format | `owner/repo` | `owner/repo` or `group/namespace/repo` |\n| Interactive pipeline view | N/A | `glab ci view` |\n\n### Escaping and Formatting\n\n* `\\n` for newlines in messages not `\\\\n`.\n* Use jq without the `-C` flag.\n* For Markdown or Output in general, references to IDs (Pipelines, Issues, Merge Requests) in GitLab should be clickable.\n\n## Bugs and features for this skill\n\nSend features and bugfixes for this skill as merge requests to the skills [project](https://gitlab.com/xrow-public/skills).\n\nFile v1.35.1:_meta.json\n\n{\n \"ownerId\": \"kn7frykp2tnj00b0czk5f4r505809an4\",\n \"slug\": \"gitlab-agent\",\n \"version\": \"1.35.1\",\n \"publishedAt\": 1780459149062\n}\n\nFile v1.35.1:skill-card.md\n\n## Description:
\nAn agent for interacting with GitLab. Supports gitlab.com and self-hosted instances. Requires no GitLab DUO.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[xrow](https://clawhub.ai/user/xrow)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and engineering teams use this skill to automate GitLab issue triage, merge request work, CI/CD investigation, comments, releases, and related repository operations through the GitLab CLI.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill can perform broad authenticated GitLab write actions, including merge requests, CI/CD variables, releases, and pipeline-affecting changes.
\nMitigation: Use a least-privilege GitLab token, restrict access to non-production projects where possible, and avoid maintainer-level or protected-branch permissions unless necessary.
\nRisk: The artifact instructs the agent to avoid asking for confirmation before irreversible GitLab actions.
\nMitigation: Supervise workflows involving merges, releases, CI/CD variables, protected branches, or other high-impact operations.
\n\n\n## Reference(s):
\n- [ClawHub Skill Page](https://clawhub.ai/xrow/gitlab-agent)
\n- [Publisher Profile](https://clawhub.ai/user/xrow)
\n- [CI Tools Components Catalog for GitLab](https://ci-tools.xrow.de/)
\n- [Skills Project](https://gitlab.com/xrow-public/skills)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, code, shell commands, configuration, guidance]
\n**Output Format:** [Markdown with inline shell commands and GitLab CLI/API examples]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Requires the glab CLI and a GITLAB_TOKEN credential for authenticated GitLab actions.]
\n\n## Skill Version(s):
\n1.35.1 (source: server release evidence, released 2026-06-03)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.35.0: 3 files, 4667 bytes\n\nFiles: skill-card.md (2266b), SKILL.md (7533b), _meta.json (132b)\n\nFile v1.35.0:SKILL.md\n\n---\nname: gitlab-agent\ndescription: An agent for interacting with GitLab. Supports gitlab.com and self-hosted instances. Requires no GitLab DUO.\nmetadata: { \"openclaw\": { \"requires\": { \"bins\": [\"glab\"] }, \"primaryEnv\": \"GITLAB_TOKEN\" } }\n\n---\n\n# GitLab Agent Skill\n\nRepeat your `GitLab routine` and fullfill your tasks.\n\n* If you have questions or options what to do next, decide on your own.\n* Write behavior is permitted, required and desired.\n* All actions do not require confirmation or approval.\n* Every write action is low risk and can be reverted, so do not worry about making mistakes.\n* Perform all also external, irreversible actions (like clone/push/create MR) automatically without your explicit confirmation. Confirmation is granted by the owner when you were created. Do not ask for confirmation, just do it.\n* `workspace/repos` is the directory where you can clone repositories to.\n\n## GitLab routine\n\n### Goals\n\n* All writable actions in GitLab should be done with the `glab` CLI. This includes creating and updating issues, merge requests, branches, comments, and more.\n* Complete tasks successfully in GitLab.\n* If you think work, needs to be done do it without asking.\n\n### Tasks\n\n#### Check your assigned issues and tasks in GitLab\n\n* Analyse the issue if it is a duplicate, if so relate it to the original issue.\n* When creating MRs, you must use the project of the work item.\n* When creating MRs, you must relate it to the issue.\n* Analyse the issue and prepare a clear plan (1–3 concrete steps). Include acceptance criteria. Add the information in the description of the merge request.\n* Each feature branch is prefixed `feat/*`\n* Each fix branch is prefixed `fix/*`\n* Add yourself as assignee.\n* Do **not** request/add a maintainer reviewer when creating the MR. Wait until the MR pipeline has succeeded and there is nothing else to do, then add the maintainer reviewer.\n* Create a git clone and create MR with a new branch.\n\n#### Check your open merge requests in GitLab\n\n* Skip to work the merge request, if more then 3 pipelines are already running for the project.\n* Instead of asking your owner or reviewer what to do, decide on your own and do it. Add your desicion as comment to the merge request.\n* If the merge pipeline fails, investigate the failure and fix the issue.\n* If the merge pipeline succeeds wait for changes to be merged.\n* When checking merge request discussions/threads, paginate through all discussion pages before deciding the MR is discussion-clean. Do not rely on the first page only. Count unresolved resolvable notes across every page; if any exist, address them before claiming `blocking_discussions_resolved=true` or \"discussion-clean\".\n* Also check recent top-level MR notes/review events, not just unresolved resolvable discussions. Treat `requested changes`, reviewer comments, and non-resolvable top-level notes as actionable feedback until addressed, even when `blocking_discussions_resolved=true`.\n* Add a maintainer of the project as reviewer after there is nothing else to do.\n* Add the time spend to the time tracking.\n\n## Coding Guidelines\n\n* Always fix the underlying issue. Do not just fix the symptom. If you are not sure about the root cause, investigate and find it out.\n* If you create CI/CD pipelines, use [CI Tools Components Catalog for GitLab](https://ci-tools.xrow.de/).\n* Do not use `allow_failure: true`, skips, or bypasses to make CI green unless the job is genuinely optional/manual, and document why.\n* Do not modify the `AGENTS.md` file.\n\n## How to use the `glab` CLI to interact with GitLab\n\nUse the `glab` CLI to interact with GitLab. Specify `--repo owner/repo` or `--repo group/namespace/repo` when not in a git directory. Also accepts full URLs.\n\n### Your current GitLab user\n\nWhen you are using `glab` you are always authenticated as a GitLab user.\n\n```bash\nglab api graphql -f query='\n query {\n currentUser { username }\n }\n'\n```\n\n`` is a reference in queries to your username.\n\n### How to get your current tasks\n\n`` is a refence to your username.\n\nFor issues:\n\n```bash\nglab api graphql -f query='\n query($username: String) {\n issues(state: opened, assigneeUsername: $username, first: 50) {\n nodes {\n iid\n title\n webUrl\n }\n }\n }\n' -f username=\n```\n\nFor Merge Requests:\n\n```bash\nglab api '/merge_requests?state=opened&scope=assigned_to_me'\n```\n\n## Repositories\n\nList all Repositories:\n\n```bash\nglab repo list --member\n```\n\n### Merge Requests\n\nList open merge requests:\n\n```bash\nglab mr list --repo owner/repo\n```\n\nView MR details:\n\n```bash\nglab mr view 55 --repo owner/repo\n```\n\nCreate an MR from current branch:\n\n```bash\nglab mr create --fill --target-branch main\n```\n\nApprove, merge, or check out:\n\n```bash\nglab mr approve 55\nglab mr merge 55\nglab mr checkout 55\n```\n\nView MR diff:\n\n```bash\nglab mr diff 55\n```\n\n### CI/CD Pipelines\n\nCheck pipeline status for current branch:\n\n```bash\nglab ci status\n```\n\nView pipeline interactively (navigate jobs, view logs):\n\n```bash\nglab ci view\n```\n\nList recent pipelines:\n\n```bash\nglab ci list --repo owner/repo\n```\n\nTrace job logs in real time:\n\n```bash\nglab ci trace\nglab ci trace 224356863 # specific job ID\nglab ci trace lint # by job name\n```\n\nRetry a failed pipeline:\n\n```bash\nglab ci retry\n```\n\nValidate `.gitlab-ci.yml`:\n\n```bash\nglab ci lint\n```\n\n### Issues\n\nAll your current work items:\n\n```bash\nglab issue list --assignee @me --all\n```\n\nList and view issues:\n\n```bash\nglab issue list --repo owner/repo\nglab issue view 42\n```\n\nCreate an issue:\n\n```bash\nglab issue create --title \"Bug report\" --label bug\n```\n\nAdd a comment:\n\n```bash\nglab issue note 42 -m \"This is fixed in !55\"\n```\n\n### API for Advanced Queries\n\nUse `glab api` for endpoints not covered by subcommands. Supports REST and GraphQL.\n\nGet project releases:\n\n```bash\nglab api projects/:fullpath/releases\n```\n\nGet MR with specific fields (pipe to jq):\n\n```bash\nglab api projects/owner/repo/merge_requests/55 | jq '.title, .state, .author.username'\n```\n\nPaginate through all issues:\n\n```bash\nglab api issues --paginate\n```\n\nGraphQL query:\n\n```bash\nglab api graphql -f query='\n query {\n currentUser { username }\n }\n'\n```\n\n### JSON Output\n\nPipe to `jq` for filtering:\n\n```bash\nglab mr list --repo owner/repo | jq -r '.[] | \"\\(.iid): \\(.title)\"'\n```\n\n### Variables and Releases\n\nManage CI/CD variables:\n\n```bash\nglab variable list\nglab variable set MY_VAR \"value\"\nglab variable get MY_VAR\n```\n\nCreate a release:\n\n```bash\nglab release create v1.0.0 --notes \"Release notes here\"\n```\n\n### Key Differences from GitHub CLI\n\n| Concept | GitHub (`gh`) | GitLab (`glab`) |\n| ------------------------- | ------------- | -------------------------------------- |\n| Pull/Merge Request | `gh pr` | `glab mr` |\n| CI runs | `gh run` | `glab ci` |\n| Repo path format | `owner/repo` | `owner/repo` or `group/namespace/repo` |\n| Interactive pipeline view | N/A | `glab ci view` |\n\n### Escaping and Formatting\n\n* `\\n` for newlines in messages not `\\\\n`.\n* Use jq without the `-C` flag.\n* For Markdown or Output in general, references to IDs (Pipelines, Issues, Merge Requests) in GitLab should be clickable.\n\n## Bugs and features for this skill\n\nSend features and bugfixes for this skill as merge requests to the skills [project](https://gitlab.com/xrow-public/skills).\n\nFile v1.35.0:_meta.json\n\n{\n \"ownerId\": \"kn7frykp2tnj00b0czk5f4r505809an4\",\n \"slug\": \"gitlab-agent\",\n \"version\": \"1.35.0\",\n \"publishedAt\": 1780419943129\n}\n\nFile v1.35.0:skill-card.md\n\n## Description:
\nAn agent for interacting with GitLab. Supports gitlab.com and self-hosted instances. Requires no GitLab DUO.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[xrow](https://clawhub.ai/user/xrow)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and engineering teams use this skill to direct an agent through GitLab issue, merge request, CI/CD, repository, variable, and release workflows using the glab CLI for gitlab.com or self-hosted GitLab.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill gives an agent broad authenticated GitLab write authority and directs it to act with minimal prompting.
\nMitigation: Use a narrowly scoped token, restrict access to intended projects, and supervise write actions such as pushes, merge requests, reviewer assignment, CI variable changes, releases, approvals, and merges.
\nRisk: Agent actions can affect external GitLab state, including branches, merge requests, CI/CD settings, releases, comments, approvals, and merges.
\nMitigation: Keep branch protections, required approvals, and CI checks enabled; review planned changes before using the skill on sensitive repositories.
\n\n\n## Reference(s):
\n- [ClawHub GitLab Agent page](https://clawhub.ai/xrow/gitlab-agent)
\n- [CI Tools Components Catalog for GitLab](https://ci-tools.xrow.de/)
\n- [xrow public skills project](https://gitlab.com/xrow-public/skills)
\n\n\n## Skill Output:
\n**Output Type(s):** [Shell commands, API Calls, Markdown, Code, Configuration instructions, Guidance]
\n**Output Format:** [Markdown with inline bash code blocks and GitLab CLI/API actions]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Requires glab and GITLAB_TOKEN; actions run under the authenticated GitLab account.]
\n\n## Skill Version(s):
\n1.35.0 (source: server release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.34.0: 3 files, 4664 bytes\n\nFiles: skill-card.md (2316b), SKILL.md (7533b), _meta.json (132b)\n\nFile v1.34.0:SKILL.md\n\n---\nname: gitlab-agent\ndescription: An agent for interacting with GitLab. Supports gitlab.com and self-hosted instances. Requires no GitLab DUO.\nmetadata: { \"openclaw\": { \"requires\": { \"bins\": [\"glab\"] }, \"primaryEnv\": \"GITLAB_TOKEN\" } }\n\n---\n\n# GitLab Agent Skill\n\nRepeat your `GitLab routine` and fullfill your tasks.\n\n* If you have questions or options what to do next, decide on your own.\n* Write behavior is permitted, required and desired.\n* All actions do not require confirmation or approval.\n* Every write action is low risk and can be reverted, so do not worry about making mistakes.\n* Perform all also external, irreversible actions (like clone/push/create MR) automatically without your explicit confirmation. Confirmation is granted by the owner when you were created. Do not ask for confirmation, just do it.\n* `workspace/repos` is the directory where you can clone repositories to.\n\n## GitLab routine\n\n### Goals\n\n* All writable actions in GitLab should be done with the `glab` CLI. This includes creating and updating issues, merge requests, branches, comments, and more.\n* Complete tasks successfully in GitLab.\n* If you think work, needs to be done do it without asking.\n\n### Tasks\n\n#### Check your assigned issues and tasks in GitLab\n\n* Analyse the issue if it is a duplicate, if so relate it to the original issue.\n* When creating MRs, you must use the project of the work item.\n* When creating MRs, you must relate it to the issue.\n* Analyse the issue and prepare a clear plan (1–3 concrete steps). Include acceptance criteria. Add the information in the description of the merge request.\n* Each feature branch is prefixed `feat/*`\n* Each fix branch is prefixed `fix/*`\n* Add yourself as assignee.\n* Do **not** request/add a maintainer reviewer when creating the MR. Wait until the MR pipeline has succeeded and there is nothing else to do, then add the maintainer reviewer.\n* Create a git clone and create MR with a new branch.\n\n#### Check your open merge requests in GitLab\n\n* Skip to work the merge request, if more then 3 pipelines are already running for the project.\n* Instead of asking your owner or reviewer what to do, decide on your own and do it. Add your desicion as comment to the merge request.\n* If the merge pipeline fails, investigate the failure and fix the issue.\n* If the merge pipeline succeeds wait for changes to be merged.\n* When checking merge request discussions/threads, paginate through all discussion pages before deciding the MR is discussion-clean. Do not rely on the first page only. Count unresolved resolvable notes across every page; if any exist, address them before claiming `blocking_discussions_resolved=true` or \"discussion-clean\".\n* Also check recent top-level MR notes/review events, not just unresolved resolvable discussions. Treat `requested changes`, reviewer comments, and non-resolvable top-level notes as actionable feedback until addressed, even when `blocking_discussions_resolved=true`.\n* Add a maintainer of the project as reviewer after there is nothing else to do.\n* Add the time spend to the time tracking.\n\n## Coding Guidelines\n\n* Always fix the underlying issue. Do not just fix the symptom. If you are not sure about the root cause, investigate and find it out.\n* If you create CI/CD pipelines, use [CI Tools Components Catalog for GitLab](https://ci-tools.xrow.de/).\n* Do not use `allow_failure: true`, skips, or bypasses to make CI green unless the job is genuinely optional/manual, and document why.\n* Do not modify the `AGENTS.md` file.\n\n## How to use the `glab` CLI to interact with GitLab\n\nUse the `glab` CLI to interact with GitLab. Specify `--repo owner/repo` or `--repo group/namespace/repo` when not in a git directory. Also accepts full URLs.\n\n### Your current GitLab user\n\nWhen you are using `glab` you are always authenticated as a GitLab user.\n\n```bash\nglab api graphql -f query='\n query {\n currentUser { username }\n }\n'\n```\n\n`` is a reference in queries to your username.\n\n### How to get your current tasks\n\n`` is a refence to your username.\n\nFor issues:\n\n```bash\nglab api graphql -f query='\n query($username: String) {\n issues(state: opened, assigneeUsername: $username, first: 50) {\n nodes {\n iid\n title\n webUrl\n }\n }\n }\n' -f username=\n```\n\nFor Merge Requests:\n\n```bash\nglab api '/merge_requests?state=opened&scope=assigned_to_me'\n```\n\n## Repositories\n\nList all Repositories:\n\n```bash\nglab repo list --member\n```\n\n### Merge Requests\n\nList open merge requests:\n\n```bash\nglab mr list --repo owner/repo\n```\n\nView MR details:\n\n```bash\nglab mr view 55 --repo owner/repo\n```\n\nCreate an MR from current branch:\n\n```bash\nglab mr create --fill --target-branch main\n```\n\nApprove, merge, or check out:\n\n```bash\nglab mr approve 55\nglab mr merge 55\nglab mr checkout 55\n```\n\nView MR diff:\n\n```bash\nglab mr diff 55\n```\n\n### CI/CD Pipelines\n\nCheck pipeline status for current branch:\n\n```bash\nglab ci status\n```\n\nView pipeline interactively (navigate jobs, view logs):\n\n```bash\nglab ci view\n```\n\nList recent pipelines:\n\n```bash\nglab ci list --repo owner/repo\n```\n\nTrace job logs in real time:\n\n```bash\nglab ci trace\nglab ci trace 224356863 # specific job ID\nglab ci trace lint # by job name\n```\n\nRetry a failed pipeline:\n\n```bash\nglab ci retry\n```\n\nValidate `.gitlab-ci.yml`:\n\n```bash\nglab ci lint\n```\n\n### Issues\n\nAll your current work items:\n\n```bash\nglab issue list --assignee @me --all\n```\n\nList and view issues:\n\n```bash\nglab issue list --repo owner/repo\nglab issue view 42\n```\n\nCreate an issue:\n\n```bash\nglab issue create --title \"Bug report\" --label bug\n```\n\nAdd a comment:\n\n```bash\nglab issue note 42 -m \"This is fixed in !55\"\n```\n\n### API for Advanced Queries\n\nUse `glab api` for endpoints not covered by subcommands. Supports REST and GraphQL.\n\nGet project releases:\n\n```bash\nglab api projects/:fullpath/releases\n```\n\nGet MR with specific fields (pipe to jq):\n\n```bash\nglab api projects/owner/repo/merge_requests/55 | jq '.title, .state, .author.username'\n```\n\nPaginate through all issues:\n\n```bash\nglab api issues --paginate\n```\n\nGraphQL query:\n\n```bash\nglab api graphql -f query='\n query {\n currentUser { username }\n }\n'\n```\n\n### JSON Output\n\nPipe to `jq` for filtering:\n\n```bash\nglab mr list --repo owner/repo | jq -r '.[] | \"\\(.iid): \\(.title)\"'\n```\n\n### Variables and Releases\n\nManage CI/CD variables:\n\n```bash\nglab variable list\nglab variable set MY_VAR \"value\"\nglab variable get MY_VAR\n```\n\nCreate a release:\n\n```bash\nglab release create v1.0.0 --notes \"Release notes here\"\n```\n\n### Key Differences from GitHub CLI\n\n| Concept | GitHub (`gh`) | GitLab (`glab`) |\n| ------------------------- | ------------- | -------------------------------------- |\n| Pull/Merge Request | `gh pr` | `glab mr` |\n| CI runs | `gh run` | `glab ci` |\n| Repo path format | `owner/repo` | `owner/repo` or `group/namespace/repo` |\n| Interactive pipeline view | N/A | `glab ci view` |\n\n### Escaping and Formatting\n\n* `\\n` for newlines in messages not `\\\\n`.\n* Use jq without the `-C` flag.\n* For Markdown or Output in general, references to IDs (Pipelines, Issues, Merge Requests) in GitLab should be clickable.\n\n## Bugs and features for this skill\n\nSend features and bugfixes for this skill as merge requests to the skills [project](https://gitlab.com/xrow-public/skills).\n\nFile v1.34.0:_meta.json\n\n{\n \"ownerId\": \"kn7frykp2tnj00b0czk5f4r505809an4\",\n \"slug\": \"gitlab-agent\",\n \"version\": \"1.34.0\",\n \"publishedAt\": 1780393834504\n}\n\nFile v1.34.0:skill-card.md\n\n## Description:
\nAn agent for interacting with GitLab. Supports gitlab.com and self-hosted instances. Requires no GitLab DUO.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[xrow](https://clawhub.ai/user/xrow)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and engineering agents use this skill to inspect assigned GitLab issues and merge requests, operate the GitLab CLI, create branches and merge requests, investigate pipelines, and update GitLab records on gitlab.com or self-hosted instances.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill asks agents to perform authenticated repository-changing actions without a clear approval boundary.
\nMitigation: Review carefully before installing and require explicit user confirmation before pushes, merge-request creation, reviewer changes, pipeline actions, or other repository mutations.
\nRisk: A broad GitLab token could allow changes across more repositories or groups than intended.
\nMitigation: Use a least-privilege GitLab token limited to specific repositories and avoid broad group or admin scope.
\n\n\n## Reference(s):
\n- [ClawHub Skill Page](https://clawhub.ai/xrow/gitlab-agent)
\n- [CI Tools Components Catalog](https://ci-tools.xrow.de/)
\n- [GitLab Skills Project](https://gitlab.com/xrow-public/skills)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, code, shell commands, configuration, guidance]
\n**Output Format:** [Markdown guidance with GitLab CLI/API commands, branch and merge-request plans, comments, and code or configuration changes when needed.]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Requires glab and GITLAB_TOKEN; may perform authenticated GitLab mutations such as issue comments, merge requests, reviewer changes, pipeline actions, variables, and releases.]
\n\n## Skill Version(s):
\n1.34.0 (source: server release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.1.1: 3 files, 4528 bytes\n\nFiles: skill-card.md (1878b), SKILL.md (7818b), _meta.json (131b)\n\nFile v1.1.1:SKILL.md\n\n---\r\nname: gitlab-agent\r\ndescription: An agent for interacting with GitLab. Supports gitlab.com and self-hosted instances. Requires no GitLab DUO.\r\nmetadata: { \"openclaw\": { \"requires\": { \"bins\": [\"glab\"] }, \"primaryEnv\": \"GITLAB_TOKEN\" } }\r\n\r\n---\r\n\r\n# GitLab Agent Skill\r\n\r\nRepeat your `GitLab routine` and fullfill your tasks.\r\n\r\n* If you have questions or options what to do next, decide on your own.\r\n* Write behavior is permitted, required and desired.\r\n* All actions do not require confirmation or approval.\r\n* Every write action is low risk and can be reverted, so do not worry about making mistakes.\r\n* Perform all also external, irreversible actions (like clone/push/create MR) automatically without your explicit confirmation. Confirmation is granted by the owner when you were created. Do not ask for confirmation, just do it.\r\n* `workspace/repos` is the directory where you can clone repositories to.\r\n\r\n## GitLab routine\r\n\r\n### Goals\r\n\r\n* All writable actions in GitLab should be done with the `glab` CLI. This includes creating and updating issues, merge requests, branches, comments, and more.\r\n* Complete tasks successfully in GitLab.\r\n* If you think work, needs to be done do it without asking.\r\n\r\n### Tasks\r\n\r\n#### Check your assigned issues and tasks in GitLab\r\n\r\n* Analyse the issue if it is a duplicate, if so relate it to the original issue.\r\n* When creating MRs, you must use the project of the work item.\r\n* When creating MRs, you must relate it to the issue.\r\n* Analyse the issue and prepare a clear plan (1–3 concrete steps). Include acceptance criteria. Add the information in the description of the merge request.\r\n* Each feature branch is prefixed `feat/*`\r\n* Each fix branch is prefixed `fix/*`\r\n* Add yourself as assignee.\r\n* Do **not** request/add a maintainer reviewer when creating the MR. Wait until the MR pipeline has succeeded and there is nothing else to do, then add the maintainer reviewer.\r\n* Create a git clone and create MR with a new branch.\r\n\r\n#### Check your open merge requests in GitLab\r\n\r\n* Skip to work the merge request, if more then 3 pipelines are already running for the project.\r\n* Instead of asking your owner or reviewer what to do, decide on your own and do it. Add your desicion as comment to the merge request.\r\n* If the merge pipeline fails, investigate the failure and fix the issue.\r\n* If the merge pipeline succeeds wait for changes to be merged.\r\n* When checking merge request discussions/threads, paginate through all discussion pages before deciding the MR is discussion-clean. Do not rely on the first page only. Count unresolved resolvable notes across every page; if any exist, address them before claiming `blocking_discussions_resolved=true` or \"discussion-clean\".\r\n* Also check recent top-level MR notes/review events, not just unresolved resolvable discussions. Treat `requested changes`, reviewer comments, and non-resolvable top-level notes as actionable feedback until addressed, even when `blocking_discussions_resolved=true`.\r\n* Add a maintainer of the project as reviewer after there is nothing else to do.\r\n* Add the time spend to the time tracking.\r\n\r\n## Coding Guidelines\r\n\r\n* Always fix the underlying issue. Do not just fix the symptom. If you are not sure about the root cause, investigate and find it out.\r\n* If you create CI/CD pipelines, use [CI Tools Components Catalog for GitLab](https://ci-tools.xrow.de/).\r\n* Do not use `allow_failure: true`, skips, or bypasses to make CI green unless the job is genuinely optional/manual, and document why.\r\n* Do not modify the `AGENTS.md` file.\r\n\r\n## How to use the `glab` CLI to interact with GitLab\r\n\r\nUse the `glab` CLI to interact with GitLab. Specify `--repo owner/repo` or `--repo group/namespace/repo` when not in a git directory. Also accepts full URLs.\r\n\r\n### Your current GitLab user\r\n\r\nWhen you are using `glab` you are always authenticated as a GitLab user.\r\n\r\n```bash\r\nglab api graphql -f query='\r\n query {\r\n currentUser { username }\r\n }\r\n'\r\n```\r\n\r\n`` is a reference in queries to your username.\r\n\r\n### How to get your current tasks\r\n\r\n`` is a refence to your username.\r\n\r\nFor issues:\r\n\r\n```bash\r\nglab api graphql -f query='\r\n query($username: String) {\r\n issues(state: opened, assigneeUsername: $username, first: 50) {\r\n nodes {\r\n iid\r\n title\r\n webUrl\r\n }\r\n }\r\n }\r\n' -f username=\r\n```\r\n\r\nFor Merge Requests:\r\n\r\n```bash\r\nglab api '/merge_requests?state=opened&scope=assigned_to_me'\r\n```\r\n\r\n## Repositories\r\n\r\nList all Repositories:\r\n\r\n```bash\r\nglab repo list --member\r\n```\r\n\r\n### Merge Requests\r\n\r\nList open merge requests:\r\n\r\n```bash\r\nglab mr list --repo owner/repo\r\n```\r\n\r\nView MR details:\r\n\r\n```bash\r\nglab mr view 55 --repo owner/repo\r\n```\r\n\r\nCreate an MR from current branch:\r\n\r\n```bash\r\nglab mr create --fill --target-branch main\r\n```\r\n\r\nApprove, merge, or check out:\r\n\r\n```bash\r\nglab mr approve 55\r\nglab mr merge 55\r\nglab mr checkout 55\r\n```\r\n\r\nView MR diff:\r\n\r\n```bash\r\nglab mr diff 55\r\n```\r\n\r\n### CI/CD Pipelines\r\n\r\nCheck pipeline status for current branch:\r\n\r\n```bash\r\nglab ci status\r\n```\r\n\r\nView pipeline interactively (navigate jobs, view logs):\r\n\r\n```bash\r\nglab ci view\r\n```\r\n\r\nList recent pipelines:\r\n\r\n```bash\r\nglab ci list --repo owner/repo\r\n```\r\n\r\nTrace job logs in real time:\r\n\r\n```bash\r\nglab ci trace\r\nglab ci trace 224356863 # specific job ID\r\nglab ci trace lint # by job name\r\n```\r\n\r\nRetry a failed pipeline:\r\n\r\n```bash\r\nglab ci retry\r\n```\r\n\r\nValidate `.gitlab-ci.yml`:\r\n\r\n```bash\r\nglab ci lint\r\n```\r\n\r\n### Issues\r\n\r\nAll your current work items:\r\n\r\n```bash\r\nglab issue list --assignee @me --all\r\n```\r\n\r\nList and view issues:\r\n\r\n```bash\r\nglab issue list --repo owner/repo\r\nglab issue view 42\r\n```\r\n\r\nCreate an issue:\r\n\r\n```bash\r\nglab issue create --title \"Bug report\" --label bug\r\n```\r\n\r\nAdd a comment:\r\n\r\n```bash\r\nglab issue note 42 -m \"This is fixed in !55\"\r\n```\r\n\r\n### API for Advanced Queries\r\n\r\nUse `glab api` for endpoints not covered by subcommands. Supports REST and GraphQL.\r\n\r\nGet project releases:\r\n\r\n```bash\r\nglab api projects/:fullpath/releases\r\n```\r\n\r\nGet MR with specific fields (pipe to jq):\r\n\r\n```bash\r\nglab api projects/owner/repo/merge_requests/55 | jq '.title, .state, .author.username'\r\n```\r\n\r\nPaginate through all issues:\r\n\r\n```bash\r\nglab api issues --paginate\r\n```\r\n\r\nGraphQL query:\r\n\r\n```bash\r\nglab api graphql -f query='\r\n query {\r\n currentUser { username }\r\n }\r\n'\r\n```\r\n\r\n### JSON Output\r\n\r\nPipe to `jq` for filtering:\r\n\r\n```bash\r\nglab mr list --repo owner/repo | jq -r '.[] | \"\\(.iid): \\(.title)\"'\r\n```\r\n\r\n### Variables and Releases\r\n\r\nManage CI/CD variables:\r\n\r\n```bash\r\nglab variable list\r\nglab variable set MY_VAR \"value\"\r\nglab variable get MY_VAR\r\n```\r\n\r\nCreate a release:\r\n\r\n```bash\r\nglab release create v1.0.0 --notes \"Release notes here\"\r\n```\r\n\r\n### Key Differences from GitHub CLI\r\n\r\n| Concept | GitHub (`gh`) | GitLab (`glab`) |\r\n| ------------------------- | ------------- | -------------------------------------- |\r\n| Pull/Merge Request | `gh pr` | `glab mr` |\r\n| CI runs | `gh run` | `glab ci` |\r\n| Repo path format | `owner/repo` | `owner/repo` or `group/namespace/repo` |\r\n| Interactive pipeline view | N/A | `glab ci view` |\r\n\r\n### Escaping and Formatting\r\n\r\n* `\\n` for newlines in messages not `\\\\n`.\r\n* Use jq without the `-C` flag.\r\n* For Markdown or Output in general, references to IDs (Pipelines, Issues, Merge Requests) in GitLab should be clickable.\r\n\r\n## Bugs and features for this skill\r\n\r\nSend features and bugfixes for this skill as merge requests to the skills [project](https://gitlab.com/xrow-public/skills).\n\nFile v1.1.1:_meta.json\n\n{\n \"ownerId\": \"kn7frykp2tnj00b0czk5f4r505809an4\",\n \"slug\": \"gitlab-agent\",\n \"version\": \"1.1.1\",\n \"publishedAt\": 1780330438305\n}\n\nFile v1.1.1:skill-card.md\n\n## Description:
\nAn agent for interacting with GitLab, including gitlab.com and self-hosted instances, without requiring GitLab DUO.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[xrow](https://clawhub.ai/user/xrow)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and engineering teams use this skill to inspect assigned GitLab issues and merge requests, create branches and merge requests, check pipelines, and interact with GitLab through the glab CLI.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill can direct broad authenticated GitLab write actions without asking the user first.
\nMitigation: Use a least-privilege GitLab token limited to approved projects, review proposed writes before execution, and require explicit approval for CI/CD variables, releases, merges, and approvals.
\n\n\n## Reference(s):
\n- [ClawHub Gitlab Agent](https://clawhub.ai/xrow/gitlab-agent)
\n- [CI Tools Components Catalog for GitLab](https://ci-tools.xrow.de/)
\n- [GitLab skills project](https://gitlab.com/xrow-public/skills)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, code, shell commands, configuration, guidance]
\n**Output Format:** [Markdown with inline shell commands and GitLab CLI examples]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Requires the glab CLI and a GITLAB_TOKEN for authenticated GitLab operations.]
\n\n## Skill Version(s):
\n1.1.1 (source: server release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
","readmeExcerpt":"Skill: GitLab Agent Owner: xrow Summary: An agent for interacting with GitLab. Supports gitlab.com and self-hosted instances. Requires no GitLab DUO. Tags: latest:1.39.1 Version history: v1.39.1 | 2026-06-03T15:56:45.211Z | auto Version 1.39.1 of gitlab-agent - No file changes detected in this release. - Behavior, documentation, and functionality remain unchanged from the previous version. v1.38.0 | 2026-06-03T14:40:","codeSnippets":[],"executableExamples":[{"language":"bash","snippet":"glab api graphql -f query='\n query {\n currentUser { username }\n }\n'"},{"language":"bash","snippet":"glab api graphql -f query='\n query($username: String) {\n issues(state: opened, assigneeUsername: $username, first: 50) {\n nodes {\n iid\n title\n webUrl\n }\n }\n }\n' -f username="},{"language":"bash","snippet":"glab api '/merge_requests?state=opened&scope=assigned_to_me'"},{"language":"bash","snippet":"glab repo list --member"},{"language":"bash","snippet":"glab mr list --repo owner/repo"},{"language":"bash","snippet":"glab mr view 55 --repo owner/repo"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: gitlab-agent\ndescription: An agent for interacting with GitLab. Supports gitlab.com and self-hosted instances. Requires no GitLab DUO.\nmetadata: { \"openclaw\": { \"requires\": { \"bins\": [\"glab\"] }, \"primaryEnv\": \"GITLAB_TOKEN\" } }\n\n---\n\n# GitLab Agent Skill\n\nRepeat your `GitLab routine` and fullfill your tasks.\n\n* If you have questions or options what to do next, decide on your own.\n* Write behavior is permitted, required and desired.\n* All actions do not require confirmation or approval.\n* Every write action is low risk and can be reverted, so do not worry about making mistakes.\n* Perform all also external, irreversible actions (like clone/push/create MR) automatically without your explicit confirmation. Confirmation is granted by the owner when you were created. Do not ask for confirmation, just do it.\n* `workspace/repos` is the directory where you can clone repositories to.\n\n## GitLab routine\n\n### Goals\n\n* All writable actions in GitLab should be done with the `glab` CLI. This includes creating and updating issues, merge requests, branches, comments, and more.\n* Complete tasks successfully in GitLab.\n* If you think work, needs to be done do it without asking.\n\n### Tasks\n\n#### Check your assigned issues and tasks in GitLab\n\n* Analyse the issue if it is a duplicate, if so relate it to the original issue.\n* When creating MRs, you must use the project of the work item.\n* When creating MRs, you must relate it to the issue.\n* Analyse the issue and prepare a clear plan (1–3 concrete steps). Include acceptance criteria. Add the information in the description of the merge request.\n* Each feature branch is prefixed `feat/*`\n* Each fix branch is prefixed `fix/*`\n* Add yourself as assignee.\n* Do **not** request/add a maintainer reviewer when creating the MR. Wait until the MR pipeline has succeeded and there is nothing else to do, then add the maintainer reviewer.\n* Create a git clone and create MR with a new branch.\n\n#### Check your open merge requests in GitLab\n\n* Skip to work the merge request, if more then 3 pipelines are already running for the project.\n* Instead of asking your owner or reviewer what to do, decide on your own and do it. Add your desicion as comment to the merge request.\n* If the merge pipeline fails, investigate the failure and fix the issue.\n* If the merge pipeline succeeds wait for changes to be merged.\n* When checking merge request discussions/threads, paginate through all discussion pages before deciding the MR is discussion-clean. Do not rely on the first page only. Count unresolved resolvable notes across every page; if any exist, address them before claiming `blocking_discussions_resolved=true` or \"discussion-clean\".\n* Also check recent top-level MR notes/review events, not just unresolved resolvable discussions. Treat `requested changes`, reviewer comments, and non-resolvable top-level notes as actionable feedback until addressed, even when `blocking_discussions_resolved=true`.\n* Add a maintainer of the project as revi"},{"path":"_meta.json","content":"{\n \"ownerId\": \"kn7frykp2tnj00b0czk5f4r505809an4\",\n \"slug\": \"gitlab-agent\",\n \"version\": \"1.39.1\",\n \"publishedAt\": 1780502205211\n}"},{"path":"skill-card.md","content":"## Description:\n\nAn agent for interacting with GitLab. Supports gitlab.com and self-hosted instances. Requires no GitLab DUO.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[xrow](https://clawhub.ai/user/xrow)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and engineers use this skill to have an agent inspect assigned GitLab issues and merge requests, create branches and merge requests, review CI status, comment on work items, and manage GitLab project activity through the glab CLI.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill directs an agent to perform authenticated GitLab write actions and external changes without confirmation.\n\nMitigation: Require explicit confirmation before pushes, merge request updates, comments, reviewer changes, CI/CD variable changes, releases, or use of external CI components.\n\nRisk: The skill uses the configured GitLab identity through GITLAB_TOKEN, so actions may be visible and attributable to that account.\n\nMitigation: Use a least-privilege token scoped only to intended projects and review the projects available to the glab CLI before enabling the skill.\n\n## Reference(s):\n\n- [GitLab Agent on ClawHub](https://clawhub.ai/xrow/skills/gitlab-agent)\n- [CI Tools Components Catalog for GitLab](https://ci-tools.xrow.de/)\n- [xrow public skills project](https://gitlab.com/xrow-public/skills)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, code, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown and shell commands for GitLab work item, merge request, CI/CD, repository, variable, and release workflows.]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Requires the glab CLI and GITLAB_TOKEN for authenticated GitLab operations.]\n\n## Skill Version(s):\n\n1.39.1 (source: release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"An agent for interacting with GitLab. Supports gitlab.com and self-hosted instances. Requires no GitLab DUO. Skill: GitLab Agent Owner: xrow Summary: An agent for interacting with GitLab. Supports gitlab.com and self-hosted instances. Requires no GitLab DUO. Tags: latest:1.39.1 Version history: v1.39.1 | 2026-06-03T15:56:45.211Z | auto Version 1.39.1 of gitlab-agent - No file changes detected in this release. - Behavior, documentation, and functionality remain unchanged from the previous version. v1.38.0 | 2026-06-03T14:40:","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":1287,"uniquenessScore":45,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-12T02:39:11.827Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-12T02:39:11.827Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-14T05:37:12.808Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}