plugins/dp-cto/skills/setup-engine/SKILL.md
Use when dp-engine binary is missing or needs reinstallation -- called by plan skill on first use, not directly by user.
npx skillsauth add raisedadead/dotplugins setup-engineInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
The dp-engine binary is user-managed (brew, curl installer, or go install).
The SessionStart hook surfaces install guidance when the binary is missing;
invoke this skill to print the same guidance on demand, then re-run.
command -v dp-engine || bash "${CLAUDE_PLUGIN_ROOT}/lib/dp-engine-install.sh"
The script detects OS via uname -s and prints:
brew install mrugesh/tap/dp-enginecurl -sSfL https://raw.githubusercontent.com/raisedadead/dotplugins/main/install.sh | shgo install github.com/raisedadead/dotplugins/cmd/dp-engine@latestInstallation is user-driven. The script never writes files.
After installing, keep dp-engine current with its built-in self-updater:
dp-engine self-update --check
dp-engine self-update
self-update verifies SHA256 against the GitHub release checksums.txt and
atomically replaces the binary on success.
After install, register the seven cto-* statuses in the tracker:
dp-engine init
dp-engine init is idempotent — running on an already-registered workspace is
safe. Report failures to the user. STOP on non-zero exit.
darwin-arm64, darwin-amd64, linux-amd64. On any other platform use
go install — no prebuilt binary is published.
go installinit step -- a binary without registered statuses leaves the user blocked on any subsequent dp-cto flowinit --check here — it only verifies, never registers; that is the bug this skill was designed to preventdevelopment
Use when the user shares a URL, names a resource from SOURCES.md, shares operational feedback, says 'adopt', 'learn from', 'what can we steal from', 'compare with', 'self-develop', or 'how do we get better'.
tools
Use when you need to set up or rebuild the dp-lsp Docker image after installing the plugin — 'set up LSP', 'build the image', 'install language servers'.
development
Use when you want to write tests first, enforce test-driven development, or add test coverage — 'write tests for this', 'TDD this feature', 'add test coverage'. Strict RED-GREEN-REFACTOR discipline.
testing
Use when starting major work that needs formal design review — cross-team changes, architectural decisions, or complex features where requirements need discovery before implementation.