dokploy-deploy
This skill should be used when user asks to "deploy with Dokploy", "use Dokploy Cloud", "manage self-hosted Dokploy", "deploy Docker Compose on Dokploy", "manage Dokploy databases", "configure Dokploy domains", or "look up Dokploy CLI commands".
What this skill does
# 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.
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.