moltworld-dashboard-deploy

What This Skill Does

The moltworld-dashboard-deploy skill is a robust deployment utility designed to standardize the lifecycle management of the MoltWorld Dashboard. It bridges the gap between raw source code and a hardened, production-ready service. The skill automates the generation of scaffolding files—such as package.json, .env.example, .nvmrc, and .gitignore—ensures project dependencies are handled safely, and provides comprehensive containerization through Docker and Docker Compose. By automating the creation of Dockerfile and docker-compose.yml configurations, the skill ensures the dashboard consistently runs on port 8787 while maintaining strict isolation of state, logs, and secrets.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/guillaumetch/moltworld-dashboard-deploy Ensure that you have npm, docker, and docker-compose installed and accessible in your shell environment before proceeding with deployment tasks.

Use Cases

This skill is ideal for developers and operators who need to move from local development to a stable production environment without manual overhead. It is perfect for:

1. Scaffolding: Rapidly bootstrapping a new dashboard environment from scratch.
2. Hardening: Implementing best practices for security by isolating environment secrets and ensuring non-privileged runtime execution.
3. Troubleshooting: Diagnosing connectivity issues, verifying port availability on 8787, and managing long-running processes via automated supervisor configurations.
4. Standardization: Enforcing project file conventions across multiple deployments to ensure team consistency.

Example Prompts

1. "Initialize the MoltWorld Dashboard scaffolding in this directory, generate the Dockerfile, and verify the service is listening on port 8787."
2. "My dashboard is down; please check the process status and restart the service using the Docker Compose configuration."
3. "Review the current package.json for suspicious scripts, and then help me set up a systemd service file for production deployment."

Tips & Limitations

Always follow the safety gates: verify dependencies before installation and never run scripts blindly. While the skill supports systemd integration, remember that this requires elevated permissions (sudo) and explicit user approval. Always prioritize Docker Compose for local development to keep host configurations clean and maintainable. If the service becomes unreachable, rely on the built-in diagnostic commands (ss, curl) rather than manual foreground execution to avoid session-dependent failures.