Skip to main content
ZICQ

Skills ZICQ category:DevOps & Cloud docker-ci-cd

Docker Ci Cd

Docker integration with CI/CD pipelines for automated builds, testing, and deployments

55 installs

Official URL:skills.sh

What this skill does

Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.

What it does

Docker integration with CI/CD pipelines for automated builds, testing, and deployments

When to use it

The official description does not include a separate “Use when”. Per the spec, agents activate this skill when the task matches keywords in that description.

How agents load it

Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: Docker CI/CD Skill; Purpose; Parameters; GitHub Actions; Complete Workflow; Multi-Arch Build. It includes spec-recommended sections: step-by-step instructions.

File analysis

File analysis: besides SKILL.md, the body references assets/github-actions-docker.yaml, scripts/build-and-push.sh. Those resources load on demand.

Docker CI/CD SkillPurposeParametersGitHub ActionsComplete WorkflowMulti-Arch BuildGitLab CI.gitlab-ci.ymlBest PracticesCachingGitHub Actions BuildKit cacheGitLab cache

Source category:skills.sh agent-skill

SKILL.md & Agent activation

Official spec ↗
name
docker-ci-cd
description
Docker integration with CI/CD pipelines for automated builds, testing, and deployments
  1. DiscoverThe client exposes names and descriptions to the agent.
  2. ActivateYour request or the task context selects the skill and loads its instructions.
  3. Load resourcesReferenced scripts, documentation and assets are used when needed.
Files referenced by the instructions · 2
  • assets/github-actions-docker.yaml
  • scripts/build-and-push.sh

These paths are extracted from the text. Check the upstream package to verify the files exist.

Invocation syntax and available tools depend on your Agent client. Client integration guide ↗

Install this skill

Skills CLI ↗

Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.

This skill references supporting files. Retrieve the complete directory from the source; copying SKILL.md alone may leave missing dependencies.

Ask your Agent to install

Copy these instructions to a compatible agent and confirm the target directory matches your client.

Install the agent skill "docker-ci-cd" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-f38caab01111205e-Docker-Ci-Cd.html
Save it as .cursor/skills/docker-ci-cd/SKILL.md or .claude/skills/docker-ci-cd/SKILL.md and keep the frontmatter name and description exactly as-is.
This skill also ships scripts/, references/, or assets/ — fetch the whole folder from https://github.com/pluginagentmarketplace/custom-plugin-docker instead of creating only a SKILL.md.

Full package on GitHub ↗

Install from the terminal · Skills CLI

Requires Node.js and npx. First inspect the repository's skill list to confirm the name.

npx skills add 'https://github.com/pluginagentmarketplace/custom-plugin-docker' --list

npx skills add 'https://github.com/pluginagentmarketplace/custom-plugin-docker' --skill 'docker-ci-cd'

The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.

Readable layout

name: docker-ci-cd description: Docker integration with CI/CD pipelines for automated builds, testing, and deployments sasmp_version: "1.3.0" bonded_agent: 07-docker-production bond_type: SECONDARY_BOND

Docker CI/CD Skill

Integrate Docker with CI/CD pipelines for automated image builds, security scanning, and deployments.

Purpose

Set up automated Docker workflows with GitHub Actions, GitLab CI, and other CI/CD platforms.

Parameters

| Parameter | Type | Required | Default | Description | |-----------|------|----------|---------|-------------| | platform | enum | No | github | github/gitlab/jenkins | | registry | string | No | ghcr.io | Container registry | | scan | boolean | No | true | Include security scan |

GitHub Actions

Complete Workflow

name: Docker Build and Deploy

on:
  push:
    branches: [main]
  pull_request:
    branches: [main]

env:
  REGISTRY: ghcr.io
  IMAGE_NAME: ${{ github.repository }}

jobs:
  build:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      packages: write

    steps:
      - uses: actions/checkout@v4

      - name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v3

      - name: Login to Registry
        if: github.event_name != 'pull_request'
        uses: docker/login-action@v3
        with:
          registry: ${{ env.REGISTRY }}
          username: ${{ github.actor }}
          password: ${{ secrets.GITHUB_TOKEN }}

      - name: Extract metadata
        id: meta
        uses: docker/metadata-action@v5
        with:
          images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
          tags: |
            type=sha
            type=ref,event=branch
            type=semver,pattern={{version}}

      - name: Build and push
        uses: docker/build-push-action@v5
        with:
          context: .
          push: ${{ github.event_name != 'pull_request' }}
          tags: ${{ steps.meta.outputs.tags }}
          labels: ${{ steps.meta.outputs.labels }}
          cache-from: type=gha
          cache-to: type=gha,mode=max

      - name: Scan for vulnerabilities
        uses: aquasecurity/trivy-action@master
        with:
          image-ref: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}:sha-${{ github.sha }}
          exit-code: '1'
          severity: 'CRITICAL,HIGH'

Multi-Arch Build

- name: Set up QEMU
  uses: docker/setup-qemu-action@v3

- name: Build multi-arch
  uses: docker/build-push-action@v5
  with:
    platforms: linux/amd64,linux/arm64
    push: true
    tags: ${{ steps.meta.outputs.tags }}

GitLab CI

# .gitlab-ci.yml
stages:
  - build
  - scan
  - deploy

variables:
  DOCKER_IMAGE: $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA

build:
  stage: build
  image: docker:24
  services:
    - docker:24-dind
  script:
    - docker login -u $CI_REGISTRY_USER -p $CI_REGISTRY_PASSWORD $CI_REGISTRY
    - docker build -t $DOCKER_IMAGE .
    - docker push $DOCKER_IMAGE

scan:
  stage: scan
  image:
    name: aquasec/trivy
    entrypoint: [""]
  script:
    - trivy image --exit-code 1 --severity CRITICAL $DOCKER_IMAGE

deploy:
  stage: deploy
  script:
    - ssh deploy@server "docker pull $DOCKER_IMAGE && docker compose up -d"
  only:
    - main

Best Practices

Caching

# GitHub Actions BuildKit cache
cache-from: type=gha
cache-to: type=gha,mode=max

# GitLab cache
cache:
  key: docker-$CI_COMMIT_REF_SLUG
  paths:
    - .docker-cache

Security

# Scan before push
- name: Scan
  run: trivy image --exit-code 1 --severity CRITICAL $IMAGE

# Sign images (cosign)
- name: Sign
  run: cosign sign $IMAGE

Error Handling

Common Errors

| Error | Cause | Solution | |-------|-------|----------| | unauthorized | Bad credentials | Check registry login | | rate limit | Docker Hub limits | Use authenticated pulls | | cache miss | First build | Cache will populate |

Fallback Strategy

  1. Build without cache if cache corrupted
  2. Use fallback registry if primary down
  3. Deploy previous version on failure

Troubleshooting

Debug Checklist

  • [ ] Registry credentials valid?
  • [ ] Docker daemon running?
  • [ ] Build context correct?
  • [ ] Dockerfile present?

Usage

Skill("docker-ci-cd")

Assets

  • assets/github-actions-docker.yaml - GitHub Actions template
  • scripts/build-and-push.sh - Build script

Related Skills

  • docker-production
  • docker-security

Related skills

DevOps & Cloud

Docker Essentials

Essential Docker commands and workflows for container management, image operations, and debugging.

DevOps & Cloud

Find Skills

Discover and install skills from the open agent skills ecosystem. Use when: (1) user asks "how do I do X" where X might have an existing ski…

DevOps & Cloud

Microsoft Foundry

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd a…

DevOps & Cloud

Azure Deploy

Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT us…