Agent skill · software engineering · rknall
GitLab Stack Creator
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.
Why this skill is useful
Adds specific directory structure and validation scripts for GitLab stack projects that the AI wouldn't reliably generate on its own.
What it needs
Requires docker installed locally. About 11k tokens when loaded. Last updated 2025-10-20. 58 stars on the source repository.
What this skill does
GitLab Stack Creator Expert assistance for creating new GitLab stack projects with proper structure, git configuration, validation scripts, and comprehensive documentation. When to Use This Skill This skill should be triggered when: Creating a new GitLab stack project Initializing a Docker stack with proper structure Setting up a project with ./config, ./secrets, ./temporary directories Configuring git repository for stack projects Setting up validation hooks and scripts Bootstrapping a stack project with best practices Core Principles This skill follows the GitLab Stack Management patterns: 1. Everything configured through docker-compose.yml and ./config 2. Secrets stored in ./secrets and Docker secrets 3. docker-entrypoint.sh scripts only when containers don't support native secrets 4. All container files owned by the user running docker (no root-owned files) 5. ./temporary directory for transient setup files (cleaned up after use) 6. Complete validation before considering stack creation complete Stack Creation is Complete When A stack creation is considered COMPLETE only when: 1. ✅ stack-validator skill reports NO issues 2. ✅ secrets-manager skill is satisfied with NO open issues 3. ✅ docker-validation skill is satisfied with NO issues 4. ✅ All validation scripts execute successfully 5. ✅ Git repository is properly initialized and configured 6. ✅ Documentation is complete in ./docs IMPORTANT: NEVER use workarounds. If the direct approach is not working, STOP and ask the user what to do instead. Stack Creation Workflow Phase 1: Project Initialization 1.1 Gather Requirements Ask the user: Project name Primary services needed (nginx, PostgreSQL, Redis, etc.) Remote git repository URL (if any) Environment (development, staging, production) Special requirements NEVER assume - always ask if information is missing. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills rknall/stack-creator