stop-monitor
Ends the monitoring of the Signal app and compiles a report of system and console logs.
Install
mkdir -p .claude/skills/stop-monitor && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14559" && unzip -o skill.zip -d .claude/skills/stop-monitor && rm skill.zipInstalls to .claude/skills/stop-monitor
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Stop the running Signal app and capture all logs and browser state for review.Key capabilities
- →Read all server logs from the background uvicorn task
- →Capture page content from the monitored tab
- →Capture console messages from the monitored tab
- →Capture network requests from the monitored tab
- →Stop the background uvicorn process
- →Present a summary of server logs, browser console, and network requests
How it works
The skill reads server logs and captures browser state including page content, console messages, and network requests. It then stops the uvicorn process and presents a summary of the collected data.
Inputs & outputs
When to use stop-monitor
- →Stopping app monitoring
- →Reviewing session logs
- →Debugging network and console errors
About this skill
/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_pageormcp__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
- Page content via
- 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
When not to use it
- →If no background task ID is available from a previous `/monitor-app`
- →If the browser tab is no longer available for capture
Limitations
- →The skill requires a background task ID from a previous `/monitor-app` to be active.
- →Browser capture is skipped if the tab is unavailable.
- →The skill always stops the server process.
How it compares
This workflow provides a consolidated snapshot of both server-side and client-side activity upon stopping an application, offering a more complete debugging context than reviewing logs or browser state separately.
Compared to similar skills
stop-monitor side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| stop-monitor (this skill) | 0 | 5mo | No flags | Beginner |
| langsmith-observability | 4 | 7mo | Review | Intermediate |
| debugging-toolkit-smart-debug | 4 | 4mo | No flags | Intermediate |
| jaeger-analysis | 6 | 5mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
langsmith-observability
davila7
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
debugging-toolkit-smart-debug
sickn33
Use when working with debugging toolkit smart debug
jaeger-analysis
incidentfox
Jaeger distributed tracing analysis. Use when investigating request latency, tracing errors across services, finding slow spans, or understanding service dependencies.
log-analyzer
mikopbx
Анализ логов Docker контейнера для диагностики проблем и мониторинга здоровья системы. Использовать при отладке ошибок, отслеживании процессов воркеров, исследовании проблем API или мониторинге поведения системы после тестов.
gcloud-usage
fcakyon
This skill should be used when user asks about "GCloud logs", "Cloud Logging queries", "Google Cloud metrics", "GCP observability", "trace analysis", or "debugging production issues on GCP".
error-debugging-error-analysis
sickn33
You are an expert error analysis specialist with deep expertise in debugging distributed systems, analyzing production incidents, and implementing comprehensive observability solutions.