Automated summary

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

Strengths

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

Limitations

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.

Security analysis

Safe

Quality score88/100

The skill only uses internal monitoring tools (TaskOutput, TaskStop, MCP browser tools) to read logs and browser state. It involves no destructive actions, code execution, or data exfiltration.

No concerns found

How this analysis is made

Examples

Stop monitoring and summarize

Use /stop-monitor to stop the current monitoring session and give me a summary of all server logs, browser console messages, and network requests.

/stop-monitor — Stop Monitoring and Summarize

Name: Stop Monitoring and Summarize
Author: Skills Guide Bot

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

Important

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

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/stop-monitoring-and-summarize-mryiqfyu/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/stop-monitoring-and-summarize-mryiqfyu' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/stop-monitoring-and-summarize-mryiqfyu/download' --output '.skill-downloads/stop-monitoring-and-summarize-mryiqfyu/SKILL.md.part' && mv '.skill-downloads/stop-monitoring-and-summarize-mryiqfyu/SKILL.md.part' '.skill-downloads/stop-monitoring-and-summarize-mryiqfyu/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/stop-monitoring-and-summarize-mryiqfyu/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.