Dokploy

**Verdict:** A capable and focused skill for managing a Dokploy instance programmatically. It exposes most core Dokploy operations (projects, apps, domains, env vars, deployments) in a consistent CLI-style interface, suitable for automation and assistant-driven operations. **Strengths:** - Good coverage of primary Dokploy features: create/update/delete for projects, apps, and domains; deployments and logs; environment variable management. - Configuration is straightforward via `DOKPLOY_API_URL` and `DOKPLOY_API_KEY` or the `dokploy-config` command. - Command layout mirrors the underlying API, which helps predictability and scripting. **Key Risks / Limitations:** - High-impact, destructive actions are available (`delete` operations on projects, applications, and domains), which can cause outages or data loss if misused. - No visible guardrails, confirmation prompts, or role scoping inside the skill itself; safety depends entirely on how it is used and how API keys are provisioned. - Requires correct resource IDs and a properly configured Dokploy instance; misconfiguration or pointing to the wrong environment can have unintended effects. **Recommended Scenarios:** - Teams already running Dokploy who want assistant- or script-driven automation for deployments and routine operations. - Internal tooling or chat-ops in a controlled environment where access and allowed operations are carefully governed. - Non-destructive workflows such as listing resources, viewing details, checking status, and reading deployment logs, with destructive commands restricted to experienced operators or locked behind policy.