dokploy-deploy
The dokploy-deploy skill provides guidance for deploying applications, managing databases, configuring domains, and operating Dokploy Cloud or self-hosted Dokploy instances. Use this skill when users request assistance with Dokploy deployment workflows, Docker Compose management, database operations, HTTPS configuration, remote server setup, or CLI command lookups. The skill references local documentation for current product steps and wording rather than relying on potentially outdated general knowledge.
git clone --depth 1 https://github.com/fcakyon/claude-codex-settings /tmp/dokploy-deploy && cp -r /tmp/dokploy-deploy/plugins/dokploy-skills/skills/dokploy-deploy ~/.claude/skills/dokploy-deploySKILL.md
# Dokploy Deploy Skill Skill for working with Dokploy Cloud and self-hosted Dokploy dashboards. Use the copied Dokploy docs for dashboard workflows and `references/cli-commands.md` for the CLI command index. Your knowledge of Dokploy plans, install flow, and product behavior may be outdated. Prefer the local references over memory when you need current steps or product wording. ## Quick Decision Trees ### "I need to choose Dokploy Cloud or self-hosted" ```text Need Dokploy Cloud? ├─ Managed Dokploy control plane → references/cloud/cloud.mdx ├─ Deploy to remote servers from Dokploy Cloud → references/cloud/cloud.mdx └─ Need the dashboard docs too → references/remote-servers/ + references/applications/ Need self-hosted Dokploy? ├─ Fresh install → references/getting-started/installation.mdx ├─ Custom install settings → references/getting-started/manual-installation.mdx └─ Day-to-day dashboard usage → references/applications/, references/docker-compose/, references/databases/ ``` ### "I need to deploy applications" ```text Need app deploy workflow? ├─ App overview and tabs → references/applications/index.mdx ├─ Build and deploy details → references/applications/build-type.mdx ├─ Production guidance → references/applications/going-production.mdx ├─ Zero downtime or rollbacks → references/applications/zero-downtime.mdx and references/applications/rollbacks.mdx └─ Preview deploys → references/applications/preview-deployments.mdx ``` ### "I need Docker Compose" ```text Need Docker Compose? ├─ Main workflow → references/docker-compose/index.mdx ├─ Domain handling → references/docker-compose/domains.mdx ├─ Example setup → references/docker-compose/example.mdx └─ Utility details → references/docker-compose/utilities.mdx ``` ### "I need databases" ```text Need database docs? ├─ Overview → references/databases/index.mdx ├─ Backups or restore → references/databases/backups.mdx and references/databases/restore.mdx ├─ Connection docs → references/databases/connection/ └─ CLI command lookup → references/cli-commands.md ``` ### "I need domains or HTTPS" ```text Need domains? ├─ Main domain workflow → references/domains/index.mdx ├─ Generated domains → references/domains/generated.mdx ├─ Cloudflare-specific flow → references/domains/cloudflare.mdx └─ Other DNS providers → references/domains/others.mdx ``` ### "I need remote servers" ```text Need remote servers? ├─ Feature overview → references/remote-servers/index.mdx ├─ Build server flow → references/remote-servers/build-server.mdx ├─ Deployment flow → references/remote-servers/deployments.mdx ├─ Setup instructions → references/remote-servers/instructions.mdx └─ Security and validation → references/remote-servers/security.mdx and references/remote-servers/validate.mdx ``` ### "I need the Dokploy CLI" ```text Need CLI lookup? └─ Full command index → references/cli-commands.md ``` ## Working Notes - Use copied Dokploy docs for product behavior and dashboard steps. - Use `references/cli-commands.md` for a quick command list sourced from `Dokploy/cli`. - If the docs and the CLI source disagree, treat the CLI source-derived command index as the source of truth for command names.
Agent-browser usage guide. Read this before running any agent-browser commands. Covers the snapshot-and-ref workflow, navigating pages, interacting with elements (click, fill, type, select), extracting text and data, taking screenshots, managing tabs, handling forms and auth, waiting for content, running multiple browser sessions in parallel, and troubleshooting common failures. Use when the user asks to interact with a website, fill a form, click something, extract data, take a screenshot, log into a site, test a web app, or automate any browser task.
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
Use when tasks involve reading, creating, or reviewing PDF files where rendering and layout matter; prefer visual checks by rendering pages (Poppler) and use Python tools such as `reportlab`, `pdfplumber`, and `pypdf` for generation and extraction.
Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions \"deck,\" \"slides,\" \"presentation,\" or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like \"the xlsx in my downloads\") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
This skill should be used when user asks to "query Azure resources", "list storage accounts", "manage Key Vault secrets", "work with Cosmos DB", "check AKS clusters", "use Azure MCP", or interact with any Azure service.
This skill should be used when user encounters "Tavily MCP error", "Tavily API key invalid", "web search not working", "Tavily failed", or needs help configuring Tavily integration.