Agent skill · software engineering · aiskillstore
debug-tauri
Automates Tauri WebView debugging using official plugins (tauri-plugin-log + screenshots) with process verification, automated screenshots, console logs, and state analysis. Use when debugging Tauri apps, investigating WebView issues, analyzing runtime errors, or troubleshooting UI problems.
Why this skill is useful
Adds an executable debugging workflow with scripts and specific commands for Tauri app debugging that aren't widely known.
What it needs
Requires tauri-plugin-debug-tools, tauri-plugin-log, tauri-plugin-screenshots installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Tauri WebView Debugger Automated debugging workflow for Tauri applications using tauri-plugin-debug-tools with official plugin integration. Prerequisites tauri-plugin-debug-tools installed and registered tauri-plugin-log (v2.0+): Official logging plugin for automatic console collection tauri-plugin-screenshots (v2.0+): Cross-platform screenshot capture Debug permissions enabled: debug-tools:default, log:default, screenshots:default Frontend logger initialized via attachConsole() (recommended for automatic log forwarding) Quick Start Run TAURIAPPNAME=<app-binary-name> scripts/capture.sh to verify process and capture screenshot. If process not found, start your dev server (e.g., tauri dev) and retry. Debug Workflow Copy this checklist to track progress: Step 1: Verify Process Status Run: TAURIAPPNAME=<your-app> scripts/capture.sh This checks if the app is running and captures an initial screenshot. Step 2: Capture Screenshot Via Plugin API (Recommended): Legacy: capture.sh script (macOS screencapture). See SCREENSHOTS.md for details. Step 3: Collect Console Logs Console Logger (Frontend - Recommended): The consoleLogger automatically collects frontend logs and errors in a ring buffer and flushes them to a temp file. Finding consoleLogger Log Files: Platform-specific consoleLogger locations: macOS: /tmp/tauriconsolelogs[appname][pid].jsonl Linux: /tmp/tauriconsolelogs[appname][pid].jsonl Windows: %TEMP%\tauriconsolelogs[appname][pid].jsonl Where [appname] is the application name and [pid] is the process ID. Backend Logs (tauri-plugin-log): Backend log locations: macOS: ~/Library/Logs/{bundleid}/debug.log Linux: ~/.local/share/{bundleid}/logs/debug.log Windows: {LOCALAPPDATA}\{bundleid}\logs\debug.log Alternative: Use debugBridge API. See IPCCOMMANDS.md for all methods. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/debug-tauri