GitLab Stack Config Generator — Claude Code skill: install guide
GitLab Stack Config Generator writes per-service configs for a GitLab stack into ./config, reads values from .env, and checks that secrets stay out of config files.
no license 303 installs ★ 93 updated 2025-10-20
npx skills add rknall/claude-skills --skill gitlab-stack-config-generator -a claude-codeWhat GitLab Stack Config Generator does
It builds per-service configs for a GitLab stack project. Each service gets a folder under ./config — nginx, PostgreSQL, Redis or your own — and the files sit flat inside it. Every value comes from .env; the config files carry no settings of their own.
The skill also lays down project meta files: CLAUDE.md, a .gitignore that keeps ./secrets and _temporary out of git, and .dockerignore. It checks that paths named in configs exist and that .env matches .env.example. Docker settings go through the docker-validation skill, secret files through secrets-manager.
A password never lands in nginx.conf: secrets stay in ./secrets and reach the container as Docker secrets, so a config only points at them. A project without the ./config and ./secrets layout has to be reshaped first.
What it helps with
- scaffold nginx, PostgreSQL and Redis configs under
./config - keep stack variables in
.envand mirror them in.env.example - move passwords out of config files into Docker secrets
- add
CLAUDE.md,.gitignoreand.dockerignoreto a new repo - verify that paths inside configs point at real files
Example prompts for the agent
- Generate nginx and PostgreSQL configs in
./configand pull values from.env. - Check the configs for secrets and sync
.envwith.env.example. - Add
CLAUDE.md,.gitignoreand.dockerignoreto this project.
How to install GitLab Stack Config Generator
1Skills CLI (Vercel)
npx skills add rknall/claude-skills --skill gitlab-stack-config-generator -a claude-code2Manually: put the files in place
~/.claude/skills/config-generator/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/config-generator/
1Skills CLI (Vercel)
npx skills add rknall/claude-skills --skill gitlab-stack-config-generator -a codex2Manually: put the files in place
.agents/skills/config-generator/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add rknall/claude-skills --skill gitlab-stack-config-generator -a cursor2Manually: put the files in place
.cursor/skills/config-generator/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install rknall/claude-skills config-generator2Manually: put the files in place
.github/skills/config-generator/SKILL.md1Skills CLI (Vercel)
npx skills add rknall/claude-skills --skill gitlab-stack-config-generator -a gemini-cli2Platform CLI
gemini skills install https://github.com/rknall/claude-skills --path config-generatorManually: put the files in place
.devin/skills/config-generator/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add rknall/claude-skills --skill gitlab-stack-config-generator -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about GitLab Stack Config Generator
How to install GitLab Stack Config Generator in Claude Code?
Run npx skills add rknall/claude-skills --skill gitlab-stack-config-generator -a claude-code. That adds the skill to Claude Code.
What does GitLab Stack Config Generator do?
It writes service configs for a GitLab stack into ./config, sources values from .env, and keeps secrets out of the files.
Where do secrets go?
Into ./secrets, mounted as Docker secrets, so configs only reference them. The secrets-manager skill handles the secret files.