Gitlab Ci Generator
ListedGenerates GitLab CI configuration files automatically based on your project's needs, streamlining pipeline setup and boosting efficiency.
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 akin-ozer/cc-devops-skills --skill gitlab-ci-generator -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
akin-ozer
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 failed 3 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
No undeclared network calls: failed
Contacts 2 hosts that are neither well-known infrastructure nor declared in the skill's frontmatter: api.allowed-service.com, install.sh.
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.
Hosts contacted
install.shundeclaredapi.allowed-service.comundeclaredgitlab.comsource hostWhat it found (3 of 5)
- devops-skills-plugin/skills/gitlab-ci-generator/references/best-practices.md:103contacts install.sh
- curl https://install.sh | bash # Pipe to bash - devops-skills-plugin/skills/gitlab-ci-generator/references/best-practices.md:110contacts install.sh
- curl -o install.sh https://install.sh - devops-skills-plugin/skills/gitlab-ci-generator/references/security-guidelines.md:212contacts install.sh
- curl https://install.sh | bash # ❌ Dangerous
No credential access: failed
Touches credential material in 2 places.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
What it found
- devops-skills-plugin/skills/gitlab-ci-generator/assets/templates/docker-build.yml:91Docker registry credentials
- echo "{\"auths\":{\"${CI_REGISTRY}\":{\"auth\":\"$(printf "%s:%s" "${CI_REGISTRY_USER}" "${CI_REGISTRY_PASSWORD}" | base64 | tr -d '\n')\"}}}" > /kaniko/.doc… - devops-skills-plugin/skills/gitlab-ci-generator/references/common-patterns.md:193Docker registry credentials
- echo "{\"auths\":{\"${CI_REGISTRY}\":{\"auth\":\"$(printf "%s:%s" "${CI_REGISTRY_USER}" "${CI_REGISTRY_PASSWORD}" | base64 | tr -d '\n')\"}}}" > /kaniko/.doc…
No pipe-to-shell installers: failed
Runs code fetched at install time in 2 places.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
What it found
- devops-skills-plugin/skills/gitlab-ci-generator/references/best-practices.md:103remote script piped into a shell
- curl https://install.sh | bash # Pipe to bash - devops-skills-plugin/skills/gitlab-ci-generator/references/security-guidelines.md:212remote script piped into a shell
- curl https://install.sh | bash # ❌ Dangerous
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 obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
Pinned to a commit: passed
Scanned akin-ozer/cc-devops-skills at 276af751e6.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 276af751e6
- Scanned
- 10 files, 6,090 lines
About this skill
What it does
The gitlab-ci-generator skill generates GitLab CI configuration files (.gitlab-ci.yml). It allows users to define their desired build, test, and deployment pipelines in a declarative way, which are then translated into executable YAML code for GitLab runners. This simplifies the process of setting up continuous integration and delivery workflows.
When to use it
- New Projects: Quickly bootstrap CI/CD pipelines for new projects without manually writing
.gitlab-ci.ymlfiles. - Standardizing Pipelines: Enforce consistent pipeline structures across multiple repositories within an organization.
- Automating Repetitive Tasks: Generate complex pipelines with common steps, reducing manual configuration effort.
- Experimenting with Pipeline Designs: Easily test and iterate on different CI/CD workflows without extensive YAML editing.
Key capabilities
- Generates
.gitlab-ci.ymlfiles based on user input. - Supports defining build, test, and deployment stages.
- Allows specification of runner types and environments.
- Provides a declarative approach to pipeline configuration.
Example prompts
- "Generate a GitLab CI pipeline for a Node.js project with linting, testing, and Docker image building."
- "Create a .gitlab-ci.yml file for a Python application using pytest and deploying to AWS EC2."
- “I need a basic CI/CD pipeline for a Go application that runs tests and builds an executable.”
Tips & gotchas
The skill's output is intended as a starting point; users may need to customize the generated .gitlab-ci.yml file further based on their specific project requirements and environment configurations. Familiarity with GitLab CI concepts will help in understanding and adjusting the generated configuration.