/inspect
Full inspection of a running Tauri app - screenshot, logs, window info, and resources
$ npx -y skills add qdhenry/Claude-Command-Suite --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/inspect
Context preview
What this command does when you run it.
Full inspection of a running Tauri app - screenshot, logs, window info, and resources
Command definition
inspect.mdname: rust:tauri:inspect
description: Full inspection of a running Tauri app - screenshot, logs, window info, and resources
allowed-tools: mcp__tauri-mcp__take_screenshot, mcp__tauri-mcp__get_app_logs, mcp__tauri-mcp__get_window_info, mcp__tauri-mcp__monitor_resources, mcp__tauri-mcp__get_devtools_info, Read
author: Quintin Henry (https://github.com/qdhenry/)
<objective> Perform a comprehensive inspection of a running Tauri application, gathering all available diagnostic information in one command. </objective>
<instructions> Inspect the Tauri application: **$ARGUMENTS**
Arguments: `[process_id]`
Inspection Process
Gather ALL of the following in parallel where possible:
1. Window Information
Use `mcp__tauri-mcp__get_window_info`:
- Window dimensions (width, height)
- Window position (x, y)
- Window state (visible, focused, minimized, etc.)
2. Application Logs
Use `mcp__tauri-mcp__get_app_logs`:
- Last 50 lines of stdout/stderr
- Highlight any errors or warnings
3. Resource Usage
Use `mcp__tauri-mcp__monitor_resources`:
- CPU usage percentage
- Memory consumption
- Other available metrics
4. Screenshot
Use `mcp__tauri-mcp__take_screenshot`:
- Capture current visual state
- Save to temp location or docs/screenshots/
5. DevTools Information
Use `mcp__tauri-mcp__get_devtools_info`:
- DevTools connection details
- Debugging port if available
Usage Examples
# Full inspection
/tauri:inspect 12345
</instructions>
<output_format>
=== Tauri App Inspection Report ===
Process ID: [PID]
Timestamp: [current time]
--- Window ---
Size: [width]x[height]
Position: ([x], [y])
State: [visible/focused/minimized]
--- Resources ---
CPU: [X]%
Memory: [X] MB
[other metrics]
--- DevTools ---
Port: [port]
URL: [devtools URL if available]
--- Recent Logs ---
[last 10 significant log entries]
--- Screenshot ---
[path to screenshot]
[display image]
--- Health Summary ---
[OK/WARNING/ERROR]: [brief status]
</output_format>
<use_cases> **Debugging Sessions:** Get complete picture of app state when investigating issues.
**Performance Analysis:** Check resource usage alongside visual state.
**Development Workflow:** Quick status check during active development.
**Issue Reporting:** Gather all diagnostic info for bug reports. </use_cases>
Read more
name: rust:tauri:inspect description: Full inspection of a running Tauri app - screenshot, logs, window info, and resources allowed-tools: mcp__tauri-mcp__take_screenshot, mcp__tauri-mcp__get_app_logs, mcp__tauri-mcp__get_window_info, mcp__tauri-mcp__monitor_resources, mcp__tauri-mcp__get_devtools_info, Read author: Quintin Henry (https://github.com/qdhenry/)
<objective> Perform a comprehensive inspection of a running Tauri application, gathering all available diagnostic information in one command. </objective>
<instructions> Inspect the Tauri application: **$ARGUMENTS**
Arguments: `[process_id]`
Inspection Process
Gather ALL of the following in parallel where possible:
1. Window Information
Use `mcp__tauri-mcp__get_window_info`:
- Window dimensions (width, height)
- Window position (x, y)
- Window state (visible, focused, minimized, etc.)
2. Application Logs
Use `mcp__tauri-mcp__get_app_logs`:
- Last 50 lines of stdout/stderr
- Highlight any errors or warnings
3. Resource Usage
Use `mcp__tauri-mcp__monitor_resources`:
- CPU usage percentage
- Memory consumption
- Other available metrics
4. Screenshot
Use `mcp__tauri-mcp__take_screenshot`:
- Capture current visual state
- Save to temp location or docs/screenshots/
5. DevTools Information
Use `mcp__tauri-mcp__get_devtools_info`:
- DevTools connection details
- Debugging port if available
Usage Examples
# Full inspection /tauri:inspect 12345
</instructions>
<output_format>
=== Tauri App Inspection Report === Process ID: [PID] Timestamp: [current time] --- Window --- Size: [width]x[height] Position: ([x], [y]) State: [visible/focused/minimized] --- Resources --- CPU: [X]% Memory: [X] MB [other metrics] --- DevTools --- Port: [port] URL: [devtools URL if available] --- Recent Logs --- [last 10 significant log entries] --- Screenshot --- [path to screenshot] [display image] --- Health Summary --- [OK/WARNING/ERROR]: [brief status]
</output_format>
<use_cases> **Debugging Sessions:** Get complete picture of app state when investigating issues.
**Performance Analysis:** Check resource usage alongside visual state.
**Development Workflow:** Quick status check during active development.
**Issue Reporting:** Gather all diagnostic info for bug reports. </use_cases>
A comprehensive development toolkit designed following Anthropic's Claude Code Best Practices for AI-assisted software development.
Repo: qdhenry/Claude-Command-Suite
Other commands on claude-command-suite.
- /boundary-bbcr-fallback
Execute automatic BBCR (Collapse-Rebirth Correction) when knowledge boundaries are exceeded or reasoning fails.
Open command - /boundary-detect
Analyze semantic position relative to knowledge boundaries to prevent hallucination and identify uncertainty zones.
Open command - /boundary-heatmap
Generate a visual heatmap of knowledge boundaries showing safe zones, risk areas, and semantic coverage.
Open command - /boundary-risk-assess
Evaluate the current risk level and provide detailed analysis of potential hallucination or reasoning failure.
Open command - /boundary-safe-bridge
Find and construct semantic bridges to safely navigate from current position to target concept without crossing dangerous boundaries.
Open command - /optimize-prompt
Takes an input prompt and returns ONLY a token-optimized version that preserves meaning while minimizing token count. Based on LLM tokenization principles: common words tokenize more efficiently, unusual words break into more tokens, and conciseness reduces cost.
Open command

