dokku

Installs, upgrades, and manages Dokku apps, deploys code or images, runs tasks, and cleans up containers on Dokku hosts via CLI commands.

Security Scan

The skill's files and runtime instructions are coherent with a Dokku administration/helper skill: it documents installing, upgrading, and operating Dokku and does not request unexplained credentials or install arbitrary code.

Purpose & Capability

The skill is clearly about Dokku administration (install, upgrade, deploy, cleanup). This matches the included command reference files. One minor inconsistency: the SKILL.md frontmatter contains metadata requiring the 'dokku' binary (metadata: {"openclaw":{"requires":{"bins":["dokku"]}}}), while the registry-level requirements show no required binaries — that likely means the skill expects Dokku to be present for many commands but also documents how to install Dokku. This is plausible for a combined 'install + manage' skill, but it's worth noting.

Instruction Scope

The instructions are mostly scoped to Dokku host administration and explicitly state commands run on the Dokku host (SSH or local). They include potentially destructive admin operations (e.g., docker system prune, dokku apps:destroy, dokku-nuke plugin) and guidance to read the user's SSH authorized_keys for adding keys (cat ~/.ssh/authorized_keys | sudo dokku ssh-keys:add admin). Those actions are relevant to Dokku setup/cleanup but are high-privilege and should only be executed on hosts you control and after confirming intent.

Install Mechanism

This is an instruction-only skill (no install spec, no code files to execute). The install instructions reference downloading bootstrap.sh from dokku.com and installing plugins from GitHub — both are standard, well-known sources. No arbitrary/personal server download URLs are present in the documentation.

Credentials

The skill does not declare or require any environment variables or credentials. It does reference system files and admin operations (reading ~/.ssh/authorized_keys, running sudo, manipulating Docker). Those are proportionate to installing and administering Dokku, but they involve sensitive data and root-level actions, so operators should expect to provide SSH/sudo access to the Dokku host when using the skill.

Persistence & Privilege

The skill does not request permanent presence (always: false) and is user-invocable. It does not attempt to modify other skills or global agent settings in the provided files. Autonomous invocation is allowed (platform default) but is not combined with other concerning privileges here.

Assessment

This skill appears to be a straightforward Dokku administration reference and helper; it's instruction-only and doesn't request secrets. Before using it, consider the following: 1) Many commands are high-privilege (sudo, docker prune, dokku apps:destroy, plugin installs). Only run them on servers you control and after backups. 2) The install instructions download Dokku's bootstrap script from dokku.com and may instruct adding SSH keys by reading ~/.ssh/authorized_keys — review any commands the agent proposes before executing them. 3) The SKILL.md metadata indicates it expects the dokku binary for many operations; if you plan to run the install steps from the skill, the dokku binary won't exist yet — follow install instructions first. 4) If you will allow the agent to run commands against a remote Dokku host, be prepared to supply explicit SSH access and confirm destructive actions. If any part of the skill proposes unexpected network endpoints, credential collection, or actions outside Dokku host administration, stop and review the exact commands.

Dokku is a PaaS; commands run on the Dokku host (SSH or local). Prefer running long operations (deploys, builds) in the background — use exec with background: true or short yieldMs when the tool allows.

Section index

Detailed command syntax and examples live in each section file. Read the relevant file when performing that category of task.

Section	File	Commands / topics
Apps	apps/commands.md	create, destroy, list, rename, clone, lock, unlock, report
Config	config/commands.md	get, set, unset, export
Domains	domains/commands.md	add, set, remove, set-global, report
Git / deploy	git/commands.md	from-image, set, deploy-branch, git push
Run (one-off / background)	run/commands.md	run, run:detached
Logs	logs/commands.md	logs, logs:failed, logs:set
Process (ps)	ps/commands.md	scale, rebuild, restart, start, stop
Plugin	plugin/commands.md	list, install, update, uninstall
Certs	certs/commands.md	add, remove, generate
Nginx	nginx/commands.md	build-config, show-config, set
Storage	storage/commands.md	mount, list
Network	network/commands.md	report, bind-all-interfaces
Install	install/commands.md	Installing Dokku (bootstrap, post-install, alternatives)
Upgrade	upgrade/commands.md	Upgrading Dokku; check migration guides before upgrading
Cleanup	cleanup/commands.md	Cleaning up Dokku and containers (prune, builder prune, apps)

Quick reference

• Create app: dokku apps:create <app-name>
• Deploy (git): Add remote dokku@<host>:<app-name>, then git push dokku <branch>:master
• Deploy (image): dokku git:from-image <app> <docker-image>
• Run in background (Dokku): dokku run:detached <app> <cmd> or dokku run --detach <app> <cmd>
• Agent-side background: For long deploys/installs, run the shell command via exec with background: true or short yieldMs; poll or check logs as needed.

For full command details and options, see the section files above.