GitLab Stack Config Generator
Generates service-specific configuration files for GitLab stack projects in ./config directory, using .env as the primary configuration source. Creates nginx, PostgreSQL, Redis, and custom service configs with strict validation for secrets, paths, and Docker best practices. Use when setting up service configurations, creating config templates, or ensuring configs follow stack patterns.
Install
/plugin marketplace add rknall/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add rknall/claude-skills --skill GitLab Stack Config Generatorgit clone --depth 1 https://github.com/rknall/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/config-generator ~/.claude/skills/GitLab-Stack-Config-GeneratorPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# GitLab Stack Config Generator This skill generates and manages service-specific configuration files for GitLab stack projects, ensuring configurations follow proper patterns, use .env for all variables, and never contain secrets. ## When to Use This Skill Activate this skill when the user requests: - Generate configuration files for services (nginx, PostgreSQL, Redis, etc.) - Create config templates for new services - Set up ./config directory structure - Validate existing configuration files - Ensure configs use .env variables correctly - Check that configs don't contain secrets - Set up project meta files (CLAUDE.md, .gitignore, .dockerignore) - Sync .env and .env.example ## Core Configuration Principles **CRITICAL RULES**: 1. **./env is Configuration Source**: All configuration variables in .env (NOT in config files) 2. **No Secrets in Configs**: NEVER put secrets in configuration files (use secrets-manager) 3. **Service Directories**: Each service gets `./config/service-name/` directory 4. **Flat Inside Service**: Config files flat inside service directory 5. **.env Sync**: .env and .env.example MUST always match 6. **Path Validation**: All referenced paths must exist 7. **Docker Validation**: Use docker-validation skill for Docker configs 8. **Project Meta Files**: CLAUDE.md, .gitignore, .dockerignore required ## Configuration Workflow ### Phase 1: Understanding Requirements **Step 1: Determine What to Generate** Ask the user (or infer):
Details
- Skill name
GitLab Stack Config Generator- Repository
- rknall/claude-skills
- Path
config-generator/SKILL.md- Repo updated
- 20 October 2025
FAQ
What does the GitLab Stack Config Generator skill do?
Generates service-specific configuration files for GitLab stack projects in ./config directory, using .env as the primary configuration source. Creates nginx, PostgreSQL, Redis, and custom service configs with strict validation for secrets, paths, and Docker best practices. Use when setting up service configurations, creating config templates, or ensuring configs follow stack patterns.
How do I install the GitLab Stack Config Generator skill?
Claude Code plugin: /plugin marketplace add rknall/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is GitLab Stack Config Generator popular?
It lives in rknall/claude-skills, which has 93 GitHub stars and 13 forks.
Related skills
Docker Configuration Validator
93rknall/claude-skills
Comprehensive Docker and Docker Compose validation following best practices and security standards. Use this skill when users ask to validate Dockerfiles, review Docker configurations, check Docker Compose files, verify multi-stage builds, audit Docker security, or ensure compliance with Docker best practices. Validates syntax, security, multi-stage builds, and modern Docker Compose requirements.
GitLab Stack Creator
93rknall/claude-skills
Create new GitLab stack projects from templates with proper directory structure, git configuration, validation hooks, and documentation. Use when initializing new Docker stack projects that follow GitLab stack patterns.
GitLab Stack Secrets Manager
93rknall/claude-skills
Manages Docker secrets for GitLab stack projects, ensuring secrets are never in .env or docker-compose.yml, properly stored in ./secrets directory, and securely integrated with Docker secrets. Use when users need to create secrets, migrate from environment variables, validate secret configuration, audit secret usage, or ensure secrets are never committed to git.
Kitchen Sink Skillset
117Peiiii/skild
Example Skillset that demonstrates inline + GitHub + registry dependencies.
Ingest Inbox Item
200lyndonkl/claude
Ingests a single file from the substacker inbox/ into corpus/seeds/ as a normalized markdown seed with full frontmatter. Orchestrates format normalization, topic tagging, intuition-density scoring, dedupe, changelog, ledger update, and inbox-file move to .processed/. Use when the user drops raw material into inbox/ and runs /ingest, at session start, or whenever a single inbox file needs to become an indexed seed. Trigger keywords — ingest, inbox, new note, new transcript, new highlight, index this, add to corpus.
GitLab Stack Validator
93rknall/claude-skills
Validates GitLab stack projects before deployment, ensuring proper architecture patterns, directory structure, secrets management, .env configuration, and Docker best practices. Use when users ask to validate a stack, check stack configuration, verify stack architecture, audit stack setup, or ensure stack deployment readiness.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.