home / skills / a5c-ai / babysitter / yaml

This skill helps you craft and validate YAML configurations for CI/CD, Docker Compose, and Kubernetes deployments.

npx playbooks add skill a5c-ai/babysitter --skill yaml

Review the files below or copy the command above to add this skill to your agents.

Files (2)
SKILL.md
696 B
---
name: yaml
description: YAML configuration for CI/CD, Docker Compose, and Kubernetes.
allowed-tools: Read, Write, Edit, Bash, Glob, Grep
---

# YAML Skill

Expert assistance for YAML configuration files.

## Capabilities

- Write YAML configurations
- Handle complex structures
- Validate YAML syntax
- Configure CI/CD
- Set up Docker Compose

## Examples

```yaml
# Docker Compose
services:
  web:
    build: .
    ports:
      - '3000:3000'
    environment:
      - NODE_ENV=production
    depends_on:
      - db

  db:
    image: postgres:15
    volumes:
      - postgres_data:/var/lib/postgresql/data
```

## Target Processes

- ci-cd-configuration
- docker-setup
- kubernetes-deployment

Overview

This skill provides expert assistance creating and validating YAML configuration files for CI/CD pipelines, Docker Compose stacks, and Kubernetes deployments. It produces clear, deterministic, and resumable configurations that integrate with automated orchestration workflows. The focus is practical: working examples, error checking, and fast iteration for development and production environments.

How this skill works

The skill analyzes requirements and generates YAML structures tailored to the target system (CI/CD, Docker Compose, or Kubernetes). It validates syntax, suggests schema-compliant fields, and produces minimal reproducible examples you can drop into your repo. For complex setups it splits concerns into reusable fragments (overlays, templates, or service definitions) and documents required secrets, volumes, and dependencies.

When to use it

  • Creating or migrating CI/CD pipeline YAML for GitHub Actions, GitLab CI, or similar systems
  • Defining multi-service Docker Compose stacks for local development or testing
  • Generating Kubernetes manifests (Deployments, Services, ConfigMaps, Helm-friendly YAML)
  • Validating and linting existing YAML files to catch syntax and schema errors
  • Splitting monolithic config into overlays, templates, or environment-specific variants

Best practices

  • Keep secrets out of YAML — reference secret managers or environment variables instead
  • Use anchors and aliases responsibly to reduce duplication while keeping readability
  • Separate development and production values with overlays or distinct files
  • Pin images and versions to improve reproducibility
  • Run a YAML linter and dry-run deployments before applying changes

Example use cases

  • Create a GitHub Actions workflow YAML that builds, tests, and publishes Docker images
  • Compose a Docker Compose file with web, worker, and database services, plus named volumes
  • Generate Kubernetes Deployment and Service manifests with resource requests and liveness/readiness probes
  • Validate an existing CI/CD YAML file and produce a corrected version with notes on breaking changes
  • Refactor a large Compose file into service-specific fragments and an environment overlay

FAQ

Can you validate YAML syntax and schema?

Yes. The skill checks YAML syntax and can validate common schemas (Kubernetes API objects, basic CI schemas). It returns errors with line hints and suggested fixes.

Do you include secrets directly in files?

No. I recommend referencing secret stores or environment variables. I will flag embedded secrets and provide secure alternatives.