AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Speckit Devops

skill-wedabro-bro-skills-speckit-devops · by wedabro

Docker Infrastructure & Security Hardening Specialist — Port ENV-first.

No reviews yet
0 installs
39 views
0.0% view→install

Install

$ agentstack add skill-wedabro-bro-skills-speckit-devops

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets Used
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-wedabro-bro-skills-speckit-devops)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Speckit Devops? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

🎯 Mission

Set up and manage a standardized and secure Docker system for the project. Ports MUST always be configured via ENV vars — NEVER hard-code.

📥 Input

  • .agent/memory/constitution.md (port range, security rules)
  • Existing Dockerfile , docker-compose.yml (if available)
  • .env.example

📋 Protocol

1. Port Allocation (ENV-first) ⭐

ALWAYS configure ports via ENV:

  • .env file (local) or server ENV (production)
  • docker-compose.yml reads: "${PUBLIC_PORT:-8920}:3000"
  • DO NOT hard-code port number in any file
  • CRITICAL: If .env or system environment already has port variables defined (e.g. PUBLIC_PORT, ADMIN_PORT, API_PORT or equivalents), ABSOLUTELY SKIP port scanning/assignment and NEVER overwrite the existing port configuration.

Port scanning rules according to environment:

| Environment | Existing Ports in .env? | Docker running? | Act | |---|---|---|---| | Any | ✅ Yes | Any | SKIP scan — use existing ports, DO NOT overwrite | | Local | ❌ No | ❌ No (first time) | Scan available ports with socket/helper → select 3 consecutive empty ports | | Local | ❌ No | ✅ Already running | SKIP scan — use current ports from docker/containers | | Staging/Beta/Prod | ❌ No | Any | ALWAYS initial scan for configuration → write to .env |

Check Docker is running (Local):

docker compose ps --format json 2>$null
# There are containers → SKIP port scan
# Empty/error → RUN port scan
  • Pattern: Public FE N → Admin FE N+1 → Backend API N+2

2. Local Docker (docker-compose.yml):

  • Ports read from ENV: "${PUBLIC_PORT:-8920}:3000"
  • Volume mounts cho hot-reload code
  • Named volumes for node_modules (avoid host-container lock)
  • Health checks for each service

3. Production Docker (docker-compose.prod.yml):

  • Multi-stage builds (builder → runner)
  • USER node or USER appuser (DO NOT run as root)
  • Remove devDependencies in the final image
  • Alpine/Slim base images
  • Ports read from ENV (NO hard-code)

4. Security Checklist:

  • .dockerignore: block .env, .git, node_modules
  • No hard-code secrets in Dockerfile
  • Only EXPOSE ports are needed

5. Documentation:

  • Update .agent/knowledge_base/infrastructure.md with the results
  • Update .env.example with all port vars

📤 Output

  • Files: Dockerfile, docker-compose.yml, docker-compose.prod.yml, .dockerignore
  • Config: .env (ports), .env.example (documented)
  • Doc: .agent/knowledge_base/infrastructure.md (updated)

🚫 Guard Rails

  • Flexibly configure ports via environment variables (.env) to avoid conflicts.
  • DO NOT hard-code port numbers — ALWAYS use ENV vars.
  • DO NOT run docker compose down -v on production.
  • DO NOT hard-code credentials into the Dockerfile.
  • DO NOT scan ports when Docker local is already running (with containers).

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.