This skill should be used when the user asks to "generate gitlab-ci.yml", "create GitLab CI pipeline", "configure GitLab CI/CD", "use To-Be-Continuous templates", "setup TBC templates", "create CI/CD for Python/Node/Go/Java project", "configure Docker build in GitLab", "setup Kubernetes deployment in GitLab", "add SonarQube to GitLab CI", "configure Terraform with GitLab", or mentions "TBC", "To-Be-Continuous", "Kicker".
/plugin marketplace add rafaelcalleja/claude-market-place/plugin install gitlab-tbc@claude-market-placeThis skill inherits all available tools. When active, it can use any tool Claude has access to.
examples/java-maven-cf.ymlexamples/node-sonar-docker.ymlexamples/python-docker-k8s.ymlexamples/terraform-aws.ymlreferences/analysis-templates.mdreferences/best-practices.mdreferences/build-templates.mdreferences/configuration-formats.mdreferences/create-component.mdreferences/deployment-templates.mdreferences/presets.mdreferences/templates-catalog.mdreferences/variantes.mdschemas/_meta.jsonschemas/amazon-web-services.jsonschemas/angular.jsonschemas/ansible.jsonschemas/azure.jsonschemas/bash.jsonschemas/bruno.jsonKnowledge base for generating GitLab CI/CD configurations using the To-Be-Continuous framework.
NEVER assume a solution. ALWAYS evaluate the framework first.
Before generating any configuration, invoke the component-research skill using the Skill tool:
Skill: component-research
This triggers the Deep Research process to determine:
Mandatory Workflow:
component-research skill (Skill tool) to evaluate fitThe user may request something and be incorrect about the approach. The component-research skill disciplines correct framework usage before any generation happens.
To-Be-Continuous (TBC) is a framework of 62 modular templates organized into 8 categories for building GitLab CI/CD pipelines.
| Category | Count | Selection |
|---|---|---|
| Build | 15 | Single |
| Code Analysis | 7 | Multiple |
| Packaging | 3 | Single |
| Infrastructure | 1 | Single |
| Deployment | 11 | Single |
| Acceptance | 10 | Multiple |
| Other | 3 | Multiple |
Selection Rules:
| Mode | GitLab Version | Syntax |
|---|---|---|
| component | 16.0+ (recommended) | $CI_SERVER_FQDN/path/template@version |
| project | Self-hosted | project: "path" + ref + file |
| remote | External | HTTPS URL to template |
| Mode | Syntax | Updates |
|---|---|---|
| major | @7 | Auto major (less stable) |
| minor | @7.5 | Auto patch (recommended) |
| full | @7.5.2 | None (most stable) |
When generating a TBC configuration, read and follow references/create-component.md.
Before generating, invoke the component-research skill using the Skill tool. That skill executes the complete decision process with flowcharts and Deep Research protocol.
| Need | Reference |
|---|---|
| Decide if component fits | Invoke component-research skill (Skill tool) |
| Complete template catalog | references/templates-catalog.md |
| Build templates (15) | references/build-templates.md |
| Deployment templates (11) | references/deployment-templates.md |
| Analysis templates (7) | references/analysis-templates.md |
| Variants (Vault, OIDC) | references/variantes.md |
| Common presets | references/presets.md |
| Best practices | references/best-practices.md |
| Configuration formats | references/configuration-formats.md |
All templates have JSON schemas in schemas/. Read schema to get valid inputs, components, and versions:
schemas/{template-name}.json
Working examples in examples/:
python-docker-k8s.ymlnode-sonar-docker.ymlterraform-aws.ymljava-maven-cf.ymlUse SlashCommand tool with tbc:validate.
tbc:validate$CI_SERVER_FQDN for component modeThis skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.