Our review

Stops a running monitoring session, captures server logs, browser state, and network requests, then presents a comprehensive summary.

Captures all relevant diagnostic data in one step
Ensures background processes are properly terminated
Provides a structured summary with server logs, console messages, and network requests
Retains captured context for follow-up questions

Requires a prior /monitor-app session to have been started
Browser capture may fail if the monitored tab has been closed
Depends on specific MCP tools (e.g., claude-in-chrome) which may not be available in all environments

When to use it

Use this skill at the end of a monitoring session to stop the server and collect all logs and browser state for review.

When not to use it

Do not use this skill if no monitoring session has been initiated via /monitor-app, as there will be no background task to stop.

/stop-monitor — Stop Monitoring and Summarize

Stop the running Signal app and capture all logs and browser state for review.

Steps

Read all server logs from the background uvicorn task using TaskOutput
Capture the current browser state from the monitored tab:
- Page content via mcp__claude-in-chrome__read_page or mcp__claude-in-chrome__get_page_text
- Console messages via mcp__claude-in-chrome__read_console_messages
- Network requests via mcp__claude-in-chrome__read_network_requests
Stop the background uvicorn process using TaskStop
Present a summary to the user covering:
- Server logs: HTTP requests served, any errors or tracebacks
- Browser console: JavaScript errors, warnings, or notable log messages
- Network requests: Failed requests, slow responses, or error status codes
- Overall status: Whether the session was clean or had issues
Keep all captured context in the conversation so the user can ask follow-up questions

If no background task ID is available from a previous /monitor-app, tell the user no monitoring session is active
If the browser tab is no longer available, skip browser capture and note it in the summary
Always stop the server process to avoid orphaned background tasks