← Back to Skills Marketplace
Moltworld Dashboard Deploy
by
guillaumetch
· GitHub ↗
· v0.1.3
619
Downloads
0
Stars
1
Active Installs
4
Versions
Install in OpenClaw
/install moltworld-dashboard-deploy
Description
Install, harden, and run the MoltWorld Dashboard reliably for real users. Use when asked to set up local runtime scaffolding (README/package.json/.env/.gitig...
README (SKILL.md)
MoltWorld Dashboard Deploy
Standardize this workflow to make moltworld-dashboard easy to run and operate safely.
Runtime requirements
Required binaries:
- npm
- docker
- docker-compose
Optional (privileged persistence path only):
- systemd
- sudo
Safety gates (mandatory)
- Treat project dependencies as untrusted until reviewed.
- Before package install, inspect
package.jsonand lockfile for suspicious scripts/deps. - Ask for explicit approval before any privileged/persistent action (
sudo,systemctl enable, writing under/etc/systemd/system). - Prefer non-privileged runtime paths first (local run or Docker Compose without host-level service install).
- Never use
curl | bashor equivalent remote script execution.
Workflow
- Verify baseline project files exist (
server.mjs,public/). - Add/shareability files if missing:
package.json(start script).env.example.nvmrc.gitignoreREADME.md
- Add deployment files if requested:
Dockerfiledocker-compose.ymlmoltworld-dashboard.service(systemd, only with explicit approval)
- Validate startup and confirm HTTP 200 on
http://localhost:8787/. - Validate restart behavior and long-running stability.
- Confirm accessibility via localhost or host IP.
- Document runbook steps for operators.
Required file conventions
- Keep runtime state out of git (
data/state.json, logs, pids). - Keep secrets out of git (
.env). - Default runtime port:
8787. - README must include:
- local quick start
- Docker run
- Docker Compose run
- systemd install/enable instructions marked as privileged/optional
Runtime stability checks
Use these checks when service becomes unreachable:
ss -ltnp | grep ':8787' || true
curl -I --max-time 5 http://localhost:8787/
If process is down, restart with a supervisor (Docker Compose or approved systemd service) instead of ad-hoc foreground runs.
Troubleshooting quick checks
- Service down: verify listener on
:8787. - Loop timeouts: increase API timeout and add retries in
postJson. - Process died after exec session: restart with supervisor.
References
- Deployment/runbook command snippets:
references/commands.md
Usage Guidance
This skill appears to do what it says: deploy and harden a local dashboard. Before using it, review package.json/package-lock for unexpected install scripts or dependencies, prefer non-privileged runs (local or Docker Compose) first, and explicitly approve any systemd/sudo steps. When building/running containers or running npm installs, do so in an isolated environment (sandbox or VM) and avoid piping remote scripts into the shell. If you will expose the service beyond localhost, verify network/firewall settings and that secrets are kept out of git (.env) as the SKILL.md recommends.
Capability Analysis
Type: OpenClaw Skill
Name: moltworld-dashboard-deploy
Version: 0.1.3
The skill bundle is designed for deploying a dashboard, which inherently involves system-level operations. However, both `SKILL.md` and `references/commands.md` include explicit and strong security 'Safety gates' for the AI agent. These instructions mandate asking for explicit approval before any privileged or persistent actions (e.g., `sudo`, `systemctl enable`), prohibit dangerous patterns like `curl | bash`, and require inspection of `package.json` before installing dependencies (using `npm ci --ignore-scripts` by default). These measures demonstrate a clear intent to operate securely and transparently, preventing common attack vectors and requiring human oversight for sensitive operations.
Capability Assessment
Purpose & Capability
Name/description match the instructions: all declared runtime needs (npm, docker, docker-compose, optional systemd) are appropriate for installing and deploying a Node/Docker-based dashboard. No unrelated credentials, binaries, or surprising capabilities are requested.
Instruction Scope
SKILL.md stays on task: it instructs verifying project files, inspecting package.json/lockfile before installs, building/running locally or via Docker/Compose, optionally installing a systemd unit with explicit approval, and performing HTTP/port checks. It does not instruct reading unrelated system files or exfiltrating data.
Install Mechanism
This is an instruction-only skill with no install spec and no bundled code to write to disk. That is the lowest-risk pattern and is proportionate for a deploy/runbook helper.
Credentials
No environment variables, credentials, or config paths are requested. The guidance to inspect package.json/lockfile and to use npm ci --ignore-scripts before running install is appropriate and limits risk from untrusted dependencies.
Persistence & Privilege
Skill does not request permanent presence or elevated privileges. It explicitly requires operator approval before privileged actions (sudo/systemd), and 'always' is false. Autonomous invocation is allowed by platform default but not combined with other red flags here.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install moltworld-dashboard-deploy - After installation, invoke the skill by name or use
/moltworld-dashboard-deploy - Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.3
Declared runtime requirements explicitly in SKILL.md:
required npm/docker/docker-compose; optional systemd/sudo for privileged persistence path.
v0.1.2
- Added mandatory security gates: dependency trust check, explicit approval for privileged/persistent actions, and prohibition of curl|bash patterns.
- Switched default install guidance to npm ci --ignore-scripts.
- Marked systemd flow as optional and operator-approved only.
- Updated and repackaged skill to reduce high-risk behavior profile while keeping install/deploy reliability workflow.
v0.1.1
- Refocused the skill on installation, accessibility, deployment, and uptime reliability.
- Removed GitHub publishing/push guidance from skill instructions and command references.
- Updated runtime checks for port/listener and localhost health verification.
- Repackaged the skill with cleaned deployment runbook commands.
v0.1.0
- Initial release of the MoltWorld Dashboard Deploy skill.
- Standardizes project setup to ensure easy cloning, running, and deployment.
- Adds scaffolding files: `README.md`, `package.json`, `.env.example`, `.gitignore`, and more if missing.
- Provides deployment support with Docker, Docker Compose, and systemd service files.
- Guides on Git/GitHub setup, commits, branch management, and troubleshooting push/auth issues.
- Enforces file conventions and includes local/startup validation steps.
Metadata
Frequently Asked Questions
What is Moltworld Dashboard Deploy?
Install, harden, and run the MoltWorld Dashboard reliably for real users. Use when asked to set up local runtime scaffolding (README/package.json/.env/.gitig... It is an AI Agent Skill for Claude Code / OpenClaw, with 619 downloads so far.
How do I install Moltworld Dashboard Deploy?
Run "/install moltworld-dashboard-deploy" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Moltworld Dashboard Deploy free?
Yes, Moltworld Dashboard Deploy is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Moltworld Dashboard Deploy support?
Moltworld Dashboard Deploy is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Moltworld Dashboard Deploy?
It is built and maintained by guillaumetch (@guillaumetch); the current version is v0.1.3.
More Skills