Mission control webapp testing

Skill MN755/Codex-Mission_Control/plugins/mission-control/skills/mission-control-webapp-testing

Plan or run web application testing through Mission Control. Use for local browser smoke tests, console errors, accessibility checks, screenshots, and regression validation.From its SKILL.md

Install

npx -y skills add MN755/Codex-Mission_Control --skill mission-control-webapp-testing

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.3 KB, 429 tokens by cl100k_base, as published. Nobody here has run it

Mission Control Webapp Testing

Purpose

Use Mission Control to coordinate practical browser and web regression testing without making the chat agent improvise test coverage.

The Codex chat agent is not the Mission Control Manager. It is the bridge between the user and the Mission Control Manager.

Use when

A web app needs smoke testing.
Frontend changes need browser verification.
The user asks for screenshots, console checks, accessibility checks, or regressions.

Workflow

Ask Mission Control to identify the app URL, startup command, and target flows.
Check the project-scoped Webwright readiness surface.
Request a compact test plan.
Prefer Webwright for approved multi-step browser checks when it is actually ready.
Summarize observed behavior, errors, screenshots, and gaps.

Mission Control calls

Tools:

mission_control_start_task
mission_control_get_status
mission_control_get_webwright_status

Resources:

mission-control://projects/{project_id}/validation-summary
mission-control://projects/{project_id}/diagnostics
mission-control://projects/{project_id}/status
mission-control://projects/{project_id}/webwright

User-facing output

Include URL tested, flows checked, console/network errors, visual issues, and validation gaps.

Approval behavior

Ask before starting servers, installing browser dependencies, or running external-network tests.

Webwright preference

If Webwright is ready, prefer it for multi-step browser automation, screenshot-backed verification, and reusable browser scripts.
If Webwright is not ready, say exactly what is missing and keep the browser automation claim unverified.

Never do

Do not declare UI working without opening or testing the target.
Do not edit guarded UI areas unless the user asked for UI work.
Do not hide flaky or skipped checks.

Failure and fallback

If browser automation is unavailable, provide a manual smoke checklist and mark automation unverified.

Example invocation

Use Mission Control to smoke test the local web app and report console errors.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.