Skills debug-tauri
📦
debug-tauri
Content revision r1 High Risk 🌐 Network access📁 Filesystem access⚙️ External commands
Debug Tauri WebView Apps
Tauri WebView bugs are hard to diagnose when logs, screenshots, and runtime state are scattered. This skill gives Claude, Codex, and Claude Code a repeatable workflow for collecting evidence and writing a clear debug report.
Supports: Claude Codex Code(CC)
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "debug-tauri" from https://skillstore.io/skills/8beeeaaat-debug-tauri.md and its manifest at https://skillstore.io/api/skills/8beeeaaat-debug-tauri/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "debug-tauri". A Tauri app opens to a blank window and the developer wants a quick triage.
Expected outcome:
- The report states whether the app process is running and records current memory and CPU observations.
- It describes the screenshot as a blank WebView and lists visible error indicators if present.
- It summarizes recent log errors and recommends checking frontend initialization and WebView permissions first.
Using "debug-tauri". A maintainer is migrating from a macOS screenshot script to official Tauri plugins.
Expected outcome:
- The migration review lists old screenshot commands that should be replaced.
- It confirms the expected logging and screenshot permissions for the new plugin workflow.
- It calls out platform-specific validation tasks for macOS, Windows, and Linux.
Using "debug-tauri". A QA engineer has logs, screenshots, and WebView state from a failed run.
Expected outcome:
- The debug report groups evidence by visual state, console logs, WebView metadata, and performance observations.
- It separates primary causes from contributing factors and gives concrete next steps for verification.
Security Audit
High Riskv7 • 7/5/2026 Open versioned report
Most command-execution and hidden-path alerts are documentation examples or expected local helper-script behavior. Confirmed risk centers on screen capture, temp-stored screenshots or logs, a hidden out-of-package reference, and report workflows that can expose sensitive debugging evidence. No prompt injection attempt or network exfiltration was found in the reviewed files.
11
Files scanned
2,169
Lines analyzed
19
Review items
0
False positives ignored
Confirmed security concerns (47)
High
Screen capture upload
**Status**: Deprecated. Use system `screencapture` command instead.
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
High
Screen capture upload
Use system screencapture command instead.
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
High
Screen capture upload
Run: screencapture -x -T 0 /tmp/tauri_screenshot.png
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
High
Screen capture upload
See [SCREENSHOTS.md](SCREENSHOTS.md) for screenshot capture methods.
This line documents the skill's screenshot capture workflow. The surrounding section enables screen or window capture, which can expose sensitive UI data even without upload evidence.
High
Screen capture upload
- **OS-dependent `screencapture` commands** → `tauri-plugin-screenshots`
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
High
Screen capture upload
### Before (macOS screencapture)
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
High
Screen capture upload
screencapture -x -T 0 "$output_path"
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
High
Screen capture upload
const screenshot = await captureMainWindow();
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
Show all 47 confirmed findings
High
Screen capture upload
console.log("Screenshot captured");
This line documents the skill's screenshot capture workflow. The surrounding section enables screen or window capture, which can expose sensitive UI data even without upload evidence.
High
Screen capture upload
- [ ] Test screenshot capture on all target platforms
This line documents the skill's screenshot capture workflow. The surrounding section enables screen or window capture, which can expose sensitive UI data even without upload evidence.
High
Screen capture upload
- **Screenshots**: Works without Screen Recording permission (captures own windows)
This line documents the skill's screenshot capture workflow. The surrounding section enables screen or window capture, which can expose sensitive UI data even without upload evidence.
High
Screen capture upload
- macOS screencapture commands
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
High
Screen capture upload
## Screenshot Capture
This line documents the skill's screenshot capture workflow. The surrounding section enables screen or window capture, which can expose sensitive UI data even without upload evidence.
High
Screen capture upload
Screenshots are captured using `tauri-plugin-screenshots` and optionally copied to `debug-tools/scre
This line documents the skill's screenshot capture workflow. The surrounding section enables screen or window capture, which can expose sensitive UI data even without upload evidence.
High
Screen capture upload
## Legacy: macOS screencapture commands
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
High
Screen capture upload
### Full screen capture
This line documents the skill's screenshot capture workflow. The surrounding section enables screen or window capture, which can expose sensitive UI data even without upload evidence.
High
Screen capture upload
screencapture -x -T 0 /tmp/screenshot.png
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
High
Screen capture upload
screencapture -l <window-id> /tmp/tauri_window.png
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
High
Screen capture upload
### Screenshot cannot be captured
This line documents the skill's screenshot capture workflow. The surrounding section enables screen or window capture, which can expose sensitive UI data even without upload evidence.
High
Screen capture upload
- [macOS screencapture man page](https://ss64.com/osx/screencapture.html)
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
High
Screen capture upload
# Screenshot Capture Reference
This line documents the skill's screenshot capture workflow. The surrounding section enables screen or window capture, which can expose sensitive UI data even without upload evidence.
High
Screen capture upload
Use `tauri-plugin-screenshots` for cross-platform screenshot capture.
This line documents the skill's screenshot capture workflow. The surrounding section enables screen or window capture, which can expose sensitive UI data even without upload evidence.
High
Screen capture upload
const screenshot = await captureMainWindow();
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
High
Screen capture upload
console.log("Screenshot captured successfully");
This line documents the skill's screenshot capture workflow. The surrounding section enables screen or window capture, which can expose sensitive UI data even without upload evidence.
High
Screen capture upload
const screenshots = await captureAllWindows();
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
High
Screen capture upload
const monitorScreenshot = await capturePrimaryMonitor();
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
High
Screen capture upload
## Legacy: macOS screencapture Command
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
High
Screen capture upload
### Full Screen Capture
This line documents the skill's screenshot capture workflow. The surrounding section enables screen or window capture, which can expose sensitive UI data even without upload evidence.
High
Screen capture upload
screencapture -x -T 0 /tmp/screenshot.png
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
High
Screen capture upload
screencapture -w /tmp/window_screenshot.png
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
High
Screen capture upload
screencapture -l <window-id> /tmp/tauri_window.png
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
High
Screen capture upload
### Error: Screenshot Not Captured
This line documents the skill's screenshot capture workflow. The surrounding section enables screen or window capture, which can expose sensitive UI data even without upload evidence.
High
Screen capture upload
- [macOS screencapture man page](https://ss64.com/osx/screencapture.html) (legacy)
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
High
Screen capture upload
### Screenshot Capture Fails
This line documents the skill's screenshot capture workflow. The surrounding section enables screen or window capture, which can expose sensitive UI data even without upload evidence.
High
Screen capture upload
# const screenshot = await captureMainWindow();
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
High
Screen capture upload
echo " const screenshot = await captureMainWindow();"
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
High
Screen capture upload
if ! screencapture -x -T 0 "$output_path" 2>/dev/null; then
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
High
Screen capture upload
if screencapture -x -T 0 "$test_file" 2>/dev/null; then
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
High
Screen capture upload
check_tool "screencapture" "legacy, optional" ""
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
High
Screen capture upload
if pgrep -x "$APP_NAME" > /dev/null && [[ "$OSTYPE" == "darwin"* ]] && screencapture -x -T 0 /tmp/te
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
High
Screen capture upload
- **tauri-plugin-screenshots** (v2.0+): Cross-platform screenshot capture
This line documents the skill's screenshot capture workflow. The surrounding section enables screen or window capture, which can expose sensitive UI data even without upload evidence.
High
Screen capture upload
**Legacy**: capture.sh script (macOS screencapture). See [SCREENSHOTS.md](references/SCREENSHOTS.md)
This line directly invokes or demonstrates screenshot capture. Even without upload evidence, capturing windows or monitors can expose sensitive UI data on the host.
High
Screen capture upload
**Screenshots**: [SCREENSHOTS.md](references/SCREENSHOTS.md) - Capture methods and troubleshooting
This line documents the skill's screenshot capture workflow. The surrounding section enables screen or window capture, which can expose sensitive UI data even without upload evidence.
High
SKILL.md:120-129references/REPORT_TEMPLATE.md:8-18references/REPORT_TEMPLATE.md:20-57references/REPORT_TEMPLATE.md:112-116
Unredacted Debug Evidence Collection
The workflow combines screenshots, process details, console logs, WebView URL, user agent, viewport, and evidence into reports. Without a required redaction step, shared reports can leak sensitive app state, local paths, usernames, tokens, or proprietary UI content.
The cited workflow and template explicitly ask for screenshots, process status, logs, WebView state, and evidence. I found no mandatory redaction guidance before the data is placed into a shareable report.
High
Broad Screenshot Scope Beyond Target Window
The screenshot guidance includes capturing all application windows, the primary monitor, and legacy full-screen screenshots. This broad capture scope can collect unrelated desktop content beyond the target Tauri app.
The cited lines document all-window, monitor, and legacy screen capture paths. The script uses screencapture without limiting capture to a Tauri window.
Low
System reconnaissance
osascript -e 'tell application "System Events" to get unix id of first process whose name is "<app-b
The command queries macOS System Events for a process window ID. It is limited to debugging a named app, but it still enumerates local process/window metadata.
Low
System reconnaissance
osascript -e 'tell application "System Events" to get unix id of first process whose name is "<app-b
The command queries macOS System Events for a process window ID. It is limited to debugging a named app, but it still enumerates local process/window metadata.
Capability review items (19)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
High
Path traversal sequence
- [Migration Plan](../../../../.claude/plans/shiny-knitting-squirrel.md)
The Markdown link escapes the skill directory into a hidden .claude planning path. It is not executable, but agents following the reference could be directed outside the packaged skill context.
High
Hidden file access
- [Migration Plan](../../../../.claude/plans/shiny-knitting-squirrel.md)
The reference points to a hidden .claude path outside the skill package. Although it is a Markdown link, it may encourage agents to read private non-packaged files.
Medium
Temp directory access
Run: screencapture -x -T 0 /tmp/tauri_screenshot.png
The location uses a shared temp directory for screenshots or debug logs that may contain sensitive UI or runtime data. This is user-initiated debugging, but the storage location still creates privacy exposure.
Medium
Temp directory access
screencapture -x -T 0 /tmp/screenshot.png
The location uses a shared temp directory for screenshots or debug logs that may contain sensitive UI or runtime data. This is user-initiated debugging, but the storage location still creates privacy exposure.
Medium
Temp directory access
The location uses a shared temp directory for screenshots or debug logs that may contain sensitive UI or runtime data. This is user-initiated debugging, but the storage location still creates privacy exposure.
Medium
Temp directory access
screencapture -x -T 0 /tmp/screenshot.png
The location uses a shared temp directory for screenshots or debug logs that may contain sensitive UI or runtime data. This is user-initiated debugging, but the storage location still creates privacy exposure.
Medium
Temp directory access
screencapture -w /tmp/window_screenshot.png
The location uses a shared temp directory for screenshots or debug logs that may contain sensitive UI or runtime data. This is user-initiated debugging, but the storage location still creates privacy exposure.
Medium
Temp directory access
scrot /tmp/screenshot.png
The location uses a shared temp directory for screenshots or debug logs that may contain sensitive UI or runtime data. This is user-initiated debugging, but the storage location still creates privacy exposure.
Medium
Temp directory access
gnome-screenshot -f /tmp/screenshot.png
The location uses a shared temp directory for screenshots or debug logs that may contain sensitive UI or runtime data. This is user-initiated debugging, but the storage location still creates privacy exposure.
Medium
Temp directory access
ls -lh /tmp/tauri_console_logs_*.jsonl
The location uses a shared temp directory for screenshots or debug logs that may contain sensitive UI or runtime data. This is user-initiated debugging, but the storage location still creates privacy exposure.
Medium
Temp directory access
- `/tmp/tauri_console_logs_[app_name]_[pid].jsonl`
The location uses a shared temp directory for screenshots or debug logs that may contain sensitive UI or runtime data. This is user-initiated debugging, but the storage location still creates privacy exposure.
Medium
Temp directory access
- `/tmp/tauri_debug_*.png` (screenshots)
The location uses a shared temp directory for screenshots or debug logs that may contain sensitive UI or runtime data. This is user-initiated debugging, but the storage location still creates privacy exposure.
Medium
Temp directory access
test_file="/tmp/screen_test_$$.png"
The location uses a shared temp directory for screenshots or debug logs that may contain sensitive UI or runtime data. This is user-initiated debugging, but the storage location still creates privacy exposure.
Medium
Temp directory access
if compgen -G "/tmp/tauri_console_logs_*.jsonl" > /dev/null; then
The location uses a shared temp directory for screenshots or debug logs that may contain sensitive UI or runtime data. This is user-initiated debugging, but the storage location still creates privacy exposure.
Medium
Temp directory access
log_file=$(ls -t /tmp/tauri_console_logs_*.jsonl 2>/dev/null | head -1)
The location uses a shared temp directory for screenshots or debug logs that may contain sensitive UI or runtime data. This is user-initiated debugging, but the storage location still creates privacy exposure.
Medium
Temp directory access
echo " $(ls -t /tmp/tauri_debug_*.png 2>/dev/null | head -1)"
The location uses a shared temp directory for screenshots or debug logs that may contain sensitive UI or runtime data. This is user-initiated debugging, but the storage location still creates privacy exposure.
Medium
Temp directory access
- **macOS**: `/tmp/tauri_console_logs_[app_name]_[pid].jsonl`
The location uses a shared temp directory for screenshots or debug logs that may contain sensitive UI or runtime data. This is user-initiated debugging, but the storage location still creates privacy exposure.
Medium
Temp directory access
- **Linux**: `/tmp/tauri_console_logs_[app_name]_[pid].jsonl`
The location uses a shared temp directory for screenshots or debug logs that may contain sensitive UI or runtime data. This is user-initiated debugging, but the storage location still creates privacy exposure.
Medium
Temp directory access
- **Windows**: `%TEMP%\tauri_console_logs_[app_name]_[pid].jsonl`
The location uses a shared temp directory for screenshots or debug logs that may contain sensitive UI or runtime data. This is user-initiated debugging, but the storage location still creates privacy exposure.
Risk Factors
🌐 Network access (2)
📁 Filesystem access (62)
references/IPC_COMMANDS.md:30 references/IPC_COMMANDS.md:30 references/IPC_COMMANDS.md:117 references/LOGGING.md:195 references/LOGGING.md:56 references/LOGGING.md:59 references/LOGGING.md:119 references/LOGGING.md:56 references/LOGGING.md:59 references/LOGGING.md:119 references/LOGGING.md:144 references/MIGRATION.md:487 references/MIGRATION.md:455 references/MIGRATION.md:455 references/MIGRATION.md:487 references/REFERENCE.md:106 references/REFERENCE.md:121 references/REPORT_TEMPLATE.md:10 references/SCREENSHOTS.md:102 references/SCREENSHOTS.md:113 references/SCREENSHOTS.md:125 references/SCREENSHOTS.md:176 references/SCREENSHOTS.md:179 references/TROUBLESHOOTING.md:69 references/TROUBLESHOOTING.md:143 references/TROUBLESHOOTING.md:144 scripts/analyze_logs.sh:55 scripts/analyze_logs.sh:24 scripts/analyze_logs.sh:55 scripts/analyze_logs.sh:67 scripts/analyze_logs.sh:68 scripts/analyze_logs.sh:69 scripts/analyze_logs.sh:70 scripts/analyze_logs.sh:71 scripts/analyze_logs.sh:103 scripts/analyze_logs.sh:109 scripts/analyze_logs.sh:115 scripts/capture.sh:41 scripts/capture.sh:55 scripts/validate_setup.sh:25 scripts/validate_setup.sh:42 scripts/validate_setup.sh:47 scripts/validate_setup.sh:48 scripts/validate_setup.sh:62 scripts/validate_setup.sh:101 scripts/validate_setup.sh:102 scripts/validate_setup.sh:113 scripts/validate_setup.sh:116 scripts/validate_setup.sh:132 scripts/validate_setup.sh:159 scripts/validate_setup.sh:177 scripts/validate_setup.sh:61 scripts/validate_setup.sh:101 scripts/validate_setup.sh:102 scripts/validate_setup.sh:116 scripts/validate_setup.sh:177 scripts/validate_setup.sh:178 SKILL.md:106 SKILL.md:106 SKILL.md:84 SKILL.md:85 SKILL.md:86
⚙️ External commands (59)
references/LOGGING.md:184-185 references/LOGGING.md:121 references/MIGRATION.md:314-316 references/MIGRATION.md:326-328 references/MIGRATION.md:375-378 references/MIGRATION.md:436-437 references/SCREENSHOTS.md:184 references/SCREENSHOTS.md:185 scripts/analyze_logs.sh:19 scripts/analyze_logs.sh:30 scripts/analyze_logs.sh:40 scripts/analyze_logs.sh:66 scripts/analyze_logs.sh:67 scripts/analyze_logs.sh:68 scripts/analyze_logs.sh:69 scripts/analyze_logs.sh:70 scripts/analyze_logs.sh:71 scripts/analyze_logs.sh:103 scripts/analyze_logs.sh:109 scripts/analyze_logs.sh:115 scripts/analyze_logs.sh:1 scripts/capture.sh:50 scripts/capture.sh:1 scripts/validate_setup.sh:20 scripts/validate_setup.sh:43 scripts/validate_setup.sh:76 scripts/validate_setup.sh:79 scripts/validate_setup.sh:102 scripts/validate_setup.sh:103 scripts/validate_setup.sh:113 scripts/validate_setup.sh:116 scripts/validate_setup.sh:1 SKILL.md:8 SKILL.md:15 SKILL.md:16 SKILL.md:20 SKILL.md:22 SKILL.md:28-37 SKILL.md:37-41 SKILL.md:41-49 SKILL.md:49-52 SKILL.md:52-60 SKILL.md:60-62 SKILL.md:62-70 SKILL.md:70-74 SKILL.md:74-80 SKILL.md:80-84 SKILL.md:84-85 SKILL.md:85-86 SKILL.md:86-88 SKILL.md:88 SKILL.md:92-101 SKILL.md:101-105 SKILL.md:105-106 SKILL.md:106-107 SKILL.md:107-113 SKILL.md:113-116 SKILL.md:116-118 SKILL.md:118-146
Detected Patterns
Screen capture upload×43System reconnaissance×2
Audited by: codex View Audit History →
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/8beeeaaat-debug-tauri/audits/7?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/8beeeaaat-debug-tauri?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/8beeeaaat-debug-tauri?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/8beeeaaat-debug-tauri/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/8beeeaaat-debug-tauri.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
8beeeaaat. (2026). debug-tauri security audit report (audit version 7) [Author version unspecified]. Skillstore. https://skillstore.io/skills/8beeeaaat-debug-tauri/audits/7BibTeX citation
@techreport{8beeeaaat-8beeeaaat-debug-tauri-2026,
author = {8beeeaaat},
title = {debug-tauri security audit report (audit version 7)},
institution = {Skillstore},
year = {2026},
number = {7},
url = {https://skillstore.io/skills/8beeeaaat-debug-tauri/audits/7},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "debug-tauri security audit report (audit version 7)"
version: "unspecified"
type: report
authors:
- name: "8beeeaaat"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/8beeeaaat-debug-tauri/audits/7"
identifiers:
- type: other
value: "skillstore:8beeeaaat-debug-tauri:audit:7"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: Medium 68
Architecture
85
Maintainability
87
Content
70
Community
83
Spec Compliance
What You Can Build
Diagnose WebView Rendering Bugs
Collect screenshots, logs, and WebView state to understand blank screens, layout failures, or visible runtime errors.
Validate Debug Tool Setup
Check whether logging, screenshot capture, permissions, and project structure are ready before reproducing user issues.
Create Evidence-Based Bug Reports
Turn process data, console findings, screenshots, and state observations into a structured report for developers.
Try These Prompts
Check My Tauri App
Use the debug-tauri workflow to check whether my Tauri app is running, capture the current UI state, and summarize the first issues to inspect.
Analyze Logs and Screenshot
Analyze the latest Tauri screenshot and plugin logs. Identify visible UI problems, recent errors, likely causes, and the next validation steps.
Validate Plugin Migration
Review my Tauri debug setup against the migration guide. Check logging, screenshots, permissions, file locations, and remaining legacy dependencies.
Build a Debug Report
Create a full Tauri debug report from process status, screenshot observations, log statistics, WebView state, root cause analysis, and prioritized fixes.
Best Practices
- Use official Tauri plugins before legacy platform scripts whenever possible.
- Redact screenshots, logs, local paths, URLs, usernames, and command arguments before sharing a report.
- Run validation before deep debugging so missing permissions or plugins do not hide the real issue.
Avoid
- Do not capture the full monitor when an app-window capture is enough.
- Do not paste raw logs or screenshots into external systems before reviewing sensitive content.
- Do not treat a missing process or missing log file as an application bug without checking setup first.
Frequently Asked Questions
What does this skill help debug?
It helps debug Tauri WebView issues by collecting screenshots, logs, process status, WebView state, and report evidence.
Does it require Tauri v2?
The documentation expects Tauri v2 compatible plugins, including tauri-plugin-log and tauri-plugin-screenshots.
Can it run on Windows and Linux?
The recommended plugin workflow is cross-platform. The legacy capture script is macOS-only.
Does it automatically fix bugs?
No. It collects and organizes evidence so a developer can choose and verify fixes.
What data should users protect?
Users should review screenshots, console logs, local file paths, URLs, process commands, and WebView state before sharing.
Which AI tools can use it?
The report lists support for Claude, Codex, and Claude Code.
Developer Details
Author
8beeeaaatLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
c4037264bbd363c572662d6154a3ab28f5ca4f53
Maintenance freshness
7/18/2026
Usage
7 downloads · 223 views
File structure