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

Docker Deploy

skill-frontier-ai-next-mgarlbot-docker-deploy · by frontier-ai-next

Inspect repo, author Dockerfile/compose, long builds, run with a clear deploy report

↗ Repository
— No reviews yet
0 installs
0 views
— view→install

Install

$ agentstack add skill-frontier-ai-next-mgarlbot-docker-deploy

Open-source listing, not yet scanned by AgentStack. Follow the source repository for install instructions.

Security review

⚠ Flagged

1 finding(s); flagged for manual review. · v0.1.0 How review works →

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

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 →

Reliability & compatibility

— Not yet reviewed
0 installs to date
— no reviews yet
● 5d 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 Docker Deploy? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Docker / Compose (test or prod stack)

Default chain: inspect project → artifacts → validate config → build (may take long) → detached run for daemons → report.

Work inside the target project tree (relative paths, cd into the service directory). With HOST SHELL MODE you may use absolute paths to other project roots on this machine.

If the user asks for apt / OS-level commands on a remote VPS, use skill vpshostssh (ssh -F /data/.ssh/config vps '...'), not local compose unless they explicitly want local only.

Public URL, Traefik/Nginx/frp, and REG.RU DNS — skills opsreverseproxy and opsdnsregru (inspect proxy on the VPS first, then config).

Do not read or paste .env, keys, or tokens into the user-facing reply.

Steps

  1. Analyze: language/runtime from pyproject.toml, package.json, go.mod, requirements.txt, existing Dockerfile; entrypoint (CMD), ports, env var names only (not secret values).
  2. Files: minimal working Dockerfile, sensible .dockerignore, docker-compose.yml if needed (build, ports, env_file: without baking secrets into the image).
  3. Config: docker compose config (or docker-compose config) — fix until clean.
  4. Build: docker compose build — iterate from logs; do not treat a long build as failure until the command exits with an error.
  5. Run: for APIs/web/daemons use docker compose up -d so the session does not block on foreground logs unless the user asks for attached logs.
  6. Verify: docker compose ps or docker ps --filter name=...; on failure docker compose logs --tail=80 .
  7. Report: briefly what changed, service/container names, published ports, commands to verify and tail logs. State clearly e.g. “Deployed; check …”.

Do not

  • Put real secrets in Dockerfile or print .env contents.
  • Suggest rm -rf /, chmod-the-world, or destructive actions outside the task.

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.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Cloud & Infrastructure