Gitlab Webhook
CheckedAutomatically trigger actions based on GitLab repository events like pushes, merges, and issue updates.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add grandcamel/gitlab-assistant-skills --skill gitlab-webhook -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
grandcamel
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned grandcamel/gitlab-assistant-skills at bdb2745983.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- bdb2745983
- Manifest
- skills/gitlab-webhook/SKILL.md
- Scanned
- 1 file, 314 lines
About this skill
What it does
This skill allows your AI agent to receive and process webhooks from GitLab. It can be configured with a secret token for authentication, ensuring that only authorized GitLab instances can trigger actions within the agent's environment. The webhook data is then parsed and made available for subsequent processing or action by the agent. This enables automated workflows based on events happening in your GitLab repositories.
When to use it
- Automated deployments: Trigger a deployment pipeline whenever code is pushed to a specific branch.
- Issue tracking updates: Automatically update an issue tracker when a pull request is merged or closed.
- CI/CD notifications: Send notifications to a communication channel (e.g., Slack, Discord) upon build failures or successful deployments.
- Repository monitoring: React to events like new tag creation or pipeline execution completions.
Key capabilities
- GitLab webhook integration
- Secret token authentication
- Webhook data parsing
- Event-driven automation
Example prompts
- "Listen for push events from my GitLab repository."
- "Configure a webhook secret token to 'my_secret_token'."
- "When a merge request is accepted, trigger the deployment script."
Tips & gotchas
Ensure you have correctly configured your GitLab project's webhook URL to point to your AI agent’s endpoint. The skill requires a publicly accessible endpoint for GitLab to send webhooks.