Навыки debug-tauri
📦
debug-tauri
Ревизия содержимого r1 Высокий риск 🌐 Доступ к сети📁 Доступ к файловой системе⚙️ Внешние команды
Отладка приложений Tauri WebView
Баги Tauri WebView сложно диагностировать, когда логи, скриншоты и состояние выполнения разбросаны по разным местам. Этот навык дает Claude, Codex и Claude Code повторяемый рабочий процесс для сбора диагностических данных и подготовки понятного отчета об отладке.
Поддерживает: Claude Codex Code(CC)
Остановитесь и запросите подтверждение перед установкой.
Проверьте план и получите явное согласие пользователя перед изменением файлов.
Установить с помощью моего Агента
Скопируйте этот запрос в своего Агента. Он содержит каноническую страницу Skill и манифест.
Запрос агента
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.Ваш Агент по-прежнему должен показать план и запросить все подтверждения, требуемые политикой безопасности.
Ресурсы для AI-агентов
Используйте эти ссылки, когда AI-агенту, crawler или script нужен чистый контекст вместо полной страницы.
Протестировать
Использование «debug-tauri». Приложение Tauri открывается с пустым окном, и разработчику нужна быстрая первичная диагностика.
Ожидаемый результат:
- В отчете указано, запущен ли процесс приложения, а также зафиксированы текущие наблюдения по памяти и CPU.
- Он описывает скриншот как пустой WebView и перечисляет видимые индикаторы ошибок, если они есть.
- Он обобщает недавние ошибки в логах и рекомендует сначала проверить инициализацию фронтенда и разрешения WebView.
Использование «debug-tauri». Мейнтейнер мигрирует со скрипта создания скриншотов для macOS на официальные плагины Tauri.
Ожидаемый результат:
- Обзор миграции перечисляет старые команды создания скриншотов, которые нужно заменить.
- Он подтверждает ожидаемые разрешения для логирования и скриншотов в новом рабочем процессе с плагинами.
- Он выделяет платформенные задачи проверки для macOS, Windows и Linux.
Использование «debug-tauri». У QA-инженера есть логи, скриншоты и состояние WebView после неудачного запуска.
Ожидаемый результат:
- Отчет об отладке группирует данные по визуальному состоянию, консольным логам, метаданным WebView и наблюдениям за производительностью.
- Он отделяет основные причины от сопутствующих факторов и дает конкретные следующие шаги для проверки.
Аудит безопасности
Высокий рискv7 • 05.07.2026 Открыть версионный отчет
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
Просканировано файлов
2,169
Проанализировано строк
19
Пункты проверки
0
Ложные срабатывания проигнорированы
Подтверждённые проблемы безопасности (47)
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Показать все подтверждённые находки (47)
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Высокий
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.
Низкий
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.
Низкий
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.
Пункты проверки возможностей (19)
Это реальные локальные возможности, которые могут ожидаться для этого навыка, поэтому они требуют проверки, но не считаются подтверждённым вредоносным поведением.
Высокий
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.
Высокий
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.
Средний
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.
Средний
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.
Средний
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.
Средний
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.
Средний
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.
Средний
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.
Средний
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.
Средний
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.
Средний
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.
Средний
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.
Средний
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.
Средний
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.
Средний
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.
Средний
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.
Средний
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.
Средний
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.
Средний
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.
Факторы риска
🌐 Доступ к сети (2)
📁 Доступ к файловой системе (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
⚙️ Внешние команды (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
Обнаруженные паттерны
Screen capture upload×43System reconnaissance×2
Аудитор:: codex Посмотреть историю аудитов →
Поделиться и цитировать этот отчет
Делитесь версионным отчетом об оценке, нейтральным значком, встраиваемой карточкой и цитатами. Skillstore публикует доказательства, не решая, безопасен ли этот Skill.
Копировать ссылку на отчёт
https://skillstore.io/skills/8beeeaaat-debug-tauri/audits/7?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportЗначок Markdown
[](https://skillstore.io/skills/8beeeaaat-debug-tauri?utm_source=security_passport_badge)Значок HTML
<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>Встраиваемая карточка
<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>Академические ссылки (APA · BibTeX · CFF)
Цитата APA
8beeeaaat. (2026). debug-tauri security audit report (audit version 7) [Author version unspecified]. Skillstore. https://skillstore.io/skills/8beeeaaat-debug-tauri/audits/7Цитата BibTeX
@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
Почему такая оценка Достоверность доказательств: Средний 68
Архитектура
85
Сопровождаемость
87
Контент
70
Сообщество
83
Соответствие спецификации
Что вы можете построить
Диагностика багов рендеринга WebView
Собирайте скриншоты, логи и состояние WebView, чтобы разобраться с пустыми экранами, сбоями верстки или видимыми ошибками выполнения.
Проверка настройки инструментов отладки
Проверяйте, готовы ли логирование, создание скриншотов, разрешения и структура проекта перед воспроизведением пользовательских проблем.
Создание баг-репортов на основе данных
Преобразуйте данные процесса, результаты анализа консоли, скриншоты и наблюдения за состоянием в структурированный отчет для разработчиков.
Попробуйте эти промпты
Проверь мое приложение Tauri
Используй рабочий процесс debug-tauri, чтобы проверить, запущено ли мое приложение Tauri, зафиксировать текущее состояние UI и кратко описать первые проблемы для проверки.
Проанализируй логи и скриншот
Проанализируй последний скриншот Tauri и логи плагинов. Определи видимые проблемы UI, недавние ошибки, вероятные причины и следующие шаги проверки.
Проверь миграцию плагинов
Проверь мою настройку отладки Tauri по руководству по миграции. Проверь логирование, скриншоты, разрешения, расположение файлов и оставшиеся устаревшие зависимости.
Собери отчет об отладке
Создай полный отчет об отладке Tauri на основе состояния процесса, наблюдений по скриншотам, статистики логов, состояния WebView, анализа первопричины и приоритизированных исправлений.
Лучшие практики
- По возможности используйте официальные плагины Tauri вместо устаревших платформенных скриптов.
- Перед передачей отчета скрывайте конфиденциальные данные на скриншотах, в логах, локальных путях, URL, именах пользователей и аргументах команд.
- Запускайте проверку перед глубокой отладкой, чтобы отсутствующие разрешения или плагины не скрывали настоящую проблему.
Избегать
- Не захватывайте весь монитор, когда достаточно захвата окна приложения.
- Не вставляйте сырые логи или скриншоты во внешние системы до проверки на наличие конфиденциальных данных.
- Не считайте отсутствующий процесс или отсутствующий файл логов багом приложения без предварительной проверки настройки.
Часто задаваемые вопросы
Что помогает отлаживать этот навык?
Он помогает отлаживать проблемы Tauri WebView, собирая скриншоты, логи, состояние процесса, состояние WebView и данные для отчета.
Требуется ли Tauri v2?
Документация предполагает плагины, совместимые с Tauri v2, включая tauri-plugin-log и tauri-plugin-screenshots.
Может ли он работать на Windows и Linux?
Рекомендуемый рабочий процесс с плагинами является кроссплатформенным. Устаревший скрипт захвата работает только на macOS.
Исправляет ли он баги автоматически?
Нет. Он собирает и систематизирует данные, чтобы разработчик мог выбрать и проверить исправления.
Какие данные пользователи должны защищать?
Пользователям следует проверять скриншоты, консольные логи, локальные пути к файлам, URL, команды процессов и состояние WebView перед передачей другим.
Какие AI-инструменты могут его использовать?
В отчете указана поддержка Claude, Codex и Claude Code.
Сведения для разработчиков
Автор
8beeeaaatЛицензия
MIT
Ревизия Skillstore
r1
Примечание о версии
Автор не указал версию.
Ссылка
c4037264bbd363c572662d6154a3ab28f5ca4f53
Актуальность поддержки
18.07.2026
Использование
7 загрузок · 223 просмотров
Структура файлов