How do I install the Stack skill?

Run npx skillmds@latest add khaitrang1995/stack in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Stack skill do?

Generate a Docker Swarm stack file — services, deploy policy (replicas, placement, rolling update/rollback), overlay network. It is listed under DevOps & Infra on SkillMD.

Is Stack safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Stack?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Stack free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

KhaiTrang1995 (@khaitrang1995) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Stack by khaitrang1995 — Agent Skill

Name: Stack
Author: KhaiTrang1995

File contents

/stack — Generate a Swarm Stack File

Input examples

/stack .NET API + Angular + Postgres --replicas 3
/stack worker service --replicas 2 --with-db
/stack fullstack --with-proxy    (adds a Traefik front, see traefik-proxy-stack.yml)

Process

Detect the services and their dependency order.
For each service: base image (reuse docker-kit/docker-conventions.md for the Dockerfile side), deploy: stanza per swarm-conventions.md, healthcheck.
Sensitive values → reference an external: true secret, never an inline env var — see /secret.
Attach all services to a stack-scoped overlay network.
L1 approval → Write.

Mandatory rules

deploy.replicas explicit for every service — never rely on the Swarm default of 1
resources.limits + .reservations both set
update_config + rollback_config both set — a rollout with no rollback plan is incomplete
Secrets via docker secret — never plain env vars for passwords/keys/tokens
Stateful services (db, anything with local volume) get placement.constraints
No inline Ingress — routing by hostname needs a proxy front (--with-proxy), Swarm has no Ingress resource

Output

docker-stack.yml
.env.example              (placeholders only — real secrets are never written to a file the agent generates)

References

@.claude/rules/swarm-conventions.md
@../../docker-kit/.claude/rules/docker-conventions.md

Frequently asked questions

Stack