
pluginagentmarketplace/custom-plugin-docker
12 skills12 installs24 starsGitHub
Install
npx skills add https://github.com/pluginagentmarketplace/custom-plugin-dockerSkills in this repo
1Docker Ci Cddocker-ci-cd is a ready-made GitHub Actions workflow for solo and indie builders who ship containerized apps. It wires checkout, QEMU, Docker Buildx, GHCR login with GITHUB_TOKEN, semantic and SHA tagging, and conditional push so pull requests only build while main, develop, and version tags publish images. The template fits SaaS APIs, CLIs, and agent backends that need consistent images without hand-rolling CI on every repo. Install it when you are moving from local docker build to automated registry delivery and want scan hooks and package write permissions aligned with GitHub’s container registry defaults.1installs2Docker Compose Setupdocker-compose-setup is an agent skill for solo builders who need a sane default Docker Compose layout instead of copying fragile snippets from forums. It ships a version 3.8 production template: build context, published ports, NODE_ENV=production, HTTP healthchecks, restart policy, and an isolated bridge network. Configuration layers separate skill metadata, validation strictness, markdown output with examples, and environment-specific overrides so development stays permissive while production turns strict validation on. The packaged schema validates semver skill versions and structure for automation-friendly agents. Use it when you are containerizing a Node-style app for a single-host or small-team deploy path; extend services for databases and workers yourself. It complements—not replaces—full orchestration on Kubernetes or managed PaaS.1installs3Docker DebuggingDocker Debugging Commands Reference is a compact command cheat sheet for solo and indie builders who run services in containers on laptops, CI, or small VPS fleets. It groups everyday Docker workflows into five areas so you do not search Stack Overflow while a deploy is red: container inspection for IDs, ports, and live stats; log analysis with follow, tail, timestamps, and time-bounded since queries; interactive debugging via docker exec for shells and one-off commands; network debugging for DNS, ping, and listening ports; and resource analysis starting with docker system df for disk pressure. The skill does not replace observability stacks—it gives procedural knowledge your coding agent can cite while you pair on incidents. Use it when stdout is empty, health checks fail, or a service cannot reach another container on the compose network. Intermediate familiarity with container IDs and compose service names is assumed.1installs4Dockerfile Basicsdockerfile-basics teaches agent-assisted Dockerfile fundamentals for solo builders shipping Node services in containers. The bundled production template walks through a three-stage pattern—dependency install with npm ci, build stage, and a minimal runner that copies dist and node_modules under a non-root user—so you do not hand-roll insecure single-stage images on deploy day. The skill also documents layer optimization, security pinning, and performance habits, plus a small shell wrapper to lint any Dockerfile via local Hadolint or the official Hadolint container image. Use it when you are moving from a working local build to something registry-ready for Fly, ECS, Kubernetes, or any Docker host. It pairs naturally with CI that builds and scans images; it does not replace orchestration manifests or cloud-specific deploy skills. Complexity is beginner-friendly for the template copy path and intermediate if you customize stages for monorepos or alternate runtimes.1installs5Docker Multi StageDocker Multi-Stage is an agent skill that ships a concrete Node.js Dockerfile pattern for solo builders who want smaller images and safer defaults without hand-rolling every layer. The template separates dependency install, compile/build, and a minimal production stage so devDependencies never bloat what runs in the cluster or on a VPS. It uses Alpine, npm ci, npm prune --production, and copies dist plus trimmed node_modules into a non-root nextjs user context with an HTTP health check—typical for shipping a compiled Node or Next-style backend after the Build phase. Invoke it when you are preparing first production deploy, tightening an existing bloated image, or teaching your coding agent consistent container conventions. It is a template skill, not a full CI pipeline; you still wire registry push, secrets, and orchestration separately.1installs6Docker NetworkingDocker Networking is a configuration-reference agent skill from a containers-category plugin that helps solo builders choose Docker network drivers and apply the right CLI patterns. It documents bridge as the default single-host option, overlay for Docker Swarm multi-host services, host for performance-sensitive workloads that share the host network namespace, and none for fully isolated containers. The bundled YAML-style settings describe logging, validation strictness, markdown output with examples, and environment overrides that tighten validation in production. Use it when you are sketching compose files, debugging why containers cannot reach each other, or standardizing network creation commands across dev and prod. It is reference and template material rather than an automated provisioner, so you still run Docker on your machine or CI. Multi-phase placement reflects design during build integrations and ongoing operate/infra tuning after ship.1installs7Docker Optimizationdocker-optimization is a containers-focused agent skill that encodes opinionated defaults and checklists for smaller images, faster CI builds, and steadier runtime behavior. Indie SaaS and API builders invoke it when Dockerfile drift has bloated images, layer caches miss constantly, or production containers lack sensible memory caps and health probes. The skill ships structured YAML-style settings (enabled flags, log levels, dev versus production strict validation) plus categorized guidance across image_size, build_speed, and runtime_performance—suitable for agents that emit markdown recommendations or plugin configuration. It is not a full security hardening or Kubernetes manifest generator; it complements those steps by making the container layer cheap to build and reliable to run. Use during late Build when first containerizing, during Ship when tightening CI, and during Operate when revisiting limits after incidents. Pair with your registry and orchestrator docs so limits match your host.1installs8Docker Productiondocker-production is a configuration-oriented agent skill that packages a Docker production playbook as skill metadata plus a four-part checklist: pre-deployment, monitoring, high availability, and backup/recovery. Solo builders shipping APIs or SaaS in containers can use it as a repeatable gate before promoting images, instead of improvising ops steps in chat. The bundled schema toggles validation strictness by environment (looser in development, strict in production) and wires optional integrations for git, linter, and formatter. It does not replace a full platform runbook, but it gives your coding agent a consistent vocabulary and ordered concerns when reviewing Dockerfiles, compose files, or deployment manifests for production readiness.1installs9Docker RegistryDocker Registry is a template skill that packages a ready-to-run private image registry for indie teams tired of pushing every build to a public hub. It wires the official Registry 2 daemon with Joxit’s UI so you can catalog tags, show digests, and delete images from a browser while keeping data on a local volume. Solo builders use it when self-hosting APIs, agents, or multi-service SaaS and need a cheap internal mirror for CI or staging deploys. The compose file documents ports, CORS headers, delete enablement, and UI catalog limits so an agent can adapt auth and TLS without rediscovering registry quirks. You still must harden REGISTRY_SECURED, authentication, and backups for production; this skill accelerates the first correct compose layout on your machine or edge server.1installs10Docker Securitydocker-security is a marketplace plugin skill aimed at solo builders and small teams who containerize services and want agent-guided security validation instead of ad-hoc Dockerfile reviews. The packaged configuration defines how validation runs: whether strict mode is on, whether the agent may auto-fix findings, and how results are formatted for downstream review. Development defaults keep logging verbose and rules relaxed so you can iterate; production profile tightens strict_mode and reduces log noise to warnings. Integrations with git, linters, and formatters position the skill inside your normal ship pipeline rather than as a one-off chat prompt. Use it when you are preparing images for registry push, tightening compose files, or aligning container settings with a repeatable security checklist the agent can apply consistently across repos.1installs11Docker SwarmDocker Swarm is an agent skill packaged as a production-oriented stack template for solo builders who self-host APIs and web fronts without adopting Kubernetes complexity. It encodes replicated nginx and application services, separated frontend, backend, and database networks, rolling update policies with automatic rollback, placement on worker nodes, and health-based orchestration. Config and secret references show how to wire TLS and database passwords in Swarm-native fashion. Use it when you already containerize with Docker and want HA-ish defaults on a small VPS fleet or homelab cluster. The skill is template-first: adapt image tags, replica counts, and constraint labels to your nodes, then deploy with docker stack deploy -c swarm-stack.yaml myapp.1installs12Docker VolumesDocker Volumes is a configuration-oriented agent skill from a custom Docker plugin marketplace, aimed at solo builders who containerize apps but need consistent defaults for volume-related behavior. The packaged YAML and JSON Schema define enabled state, log levels, validation strictness, auto-fix flags, and per-environment overrides so development stays permissive while production enforces stricter checks. Integrations for git, linters, and formatters suggest the skill fits into agent-assisted repo workflows rather than one-shot chat advice. For indies shipping Docker Compose or plugin-based stacks, it offers a structured place to encode how volume settings should be validated and reported—useful when you want repeatable agent guidance instead of re-explaining mount policies every session.1installs