mission-control-visual-qa

What This Skill Does

The mission-control-visual-qa skill is a specialized automation tool designed to bridge the gap between local control and remote browser testing. By leveraging Puppeteer, this skill executes automated visual and structural checks on Mission Control web pages directly from your designated remote infrastructure. It operates by utilizing a local helper script to orchestrate the secure transfer (via SCP) and remote execution (via SSH) of a Node.js test runner. This ensures that QA checks are performed within the network context of your production or staging environments, rather than from your local machine, avoiding common firewall and connectivity bottlenecks.

Installation

To install this skill, use the OpenClaw CLI to fetch it from the repository: clawhub install openclaw/skills/skills/highlander89/mission-control-visual-qa. Ensure that your local machine has SSH access to the target remote host and that the target host satisfies the requirements for running Node.js and Puppeteer. Once installed, you can trigger it directly through the OpenClaw interface by referencing the skill name.

Use Cases

• Automated Sanity Testing: Automatically verify that dashboard elements are rendered correctly after a new deployment to Mission Control.
• Performance Benchmarking: Collect visual snapshots of page load states to identify regressions in UI components across different deployment environments.
• Remote Infrastructure Validation: Confirm that the internal web services are responding with expected DOM elements, providing a reliable heartbeat check for critical management consoles.

Example Prompts

1. "Run mission-control-visual-qa for the dashboard and status pages to verify they are rendering correctly on the production node."
2. "Perform a visual QA check on https://mission-control.example.local/logs using the highlander89 mission-control-visual-qa skill."
3. "Execute the mission-control-visual-qa runner against our staging environment and summarize any missing DOM elements."

Tips & Limitations

• Security: Always verify that your SSH identity is properly configured to avoid manual password prompts, which can cause the automated execution to hang.
• Environment: Ensure Node.js and the necessary Chromium dependencies are installed on the remote machine. If the script fails, check the REMOTE_RUN_DIR path for logs.
• Scope: This is a read-only utility. It will not click buttons or modify site state, making it safe for production environments, but it is not intended for functional end-to-end testing that requires user interaction or form submission.