📦
debugging
84오류와 근본 원인 디버그
작성자 89jobrien
증거가 로그, 스택 트레이스, 서비스 전반에 흩어져 있으면 오류와 인시던트를 분류하기 어렵습니다. 이 스킬은 진단을 구조화하고, 로그를 파싱하며, 패턴을 식별하고, 최소한의 수정으로 안내합니다.
코딩 및 개발 보기
스킬 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 에이전트, 크롤러, 스크립트가 전체 페이지 대신 정리된 컨텍스트만 필요할 때 이 링크를 사용하세요.
테스트해 보기
"debug-tauri" 사용 중입니다. Tauri 앱이 빈 창으로 열리고 개발자가 빠른 초기 진단을 원합니다.
예상 결과:
- 보고서는 앱 프로세스가 실행 중인지 명시하고 현재 메모리 및 CPU 관찰 내용을 기록합니다.
- 스크린샷을 빈 WebView로 설명하고, 표시되는 오류 지표가 있으면 나열합니다.
- 최근 로그 오류를 요약하고 frontend 초기화와 WebView 권한을 먼저 확인할 것을 권장합니다.
"debug-tauri" 사용 중입니다. maintainer가 macOS 스크린샷 스크립트에서 공식 Tauri plugin으로 마이그레이션하고 있습니다.
예상 결과:
- 마이그레이션 검토에서는 교체해야 할 기존 스크린샷 명령을 나열합니다.
- 새 plugin 워크플로에 필요한 예상 로깅 및 스크린샷 권한을 확인합니다.
- macOS, Windows, Linux에 대한 플랫폼별 검증 작업을 짚어 줍니다.
"debug-tauri" 사용 중입니다. QA 엔지니어가 실패한 실행에서 얻은 로그, 스크린샷, WebView 상태를 가지고 있습니다.
예상 결과:
- 디버그 보고서는 시각적 상태, 콘솔 로그, WebView 메타데이터, 성능 관찰 내용별로 증거를 그룹화합니다.
- 주요 원인과 기여 요인을 구분하고 검증을 위한 구체적인 다음 단계를 제공합니다.
보안 감사
높은 위험v7 • 2026. 7. 5. 버전별 보고서 열기
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_reportMarkdown 배지
[](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/7BibTeX 인용
@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 스크린샷과 plugin 로그를 분석하세요. 표시되는 UI 문제, 최근 오류, 가능한 원인, 다음 검증 단계를 식별하세요.
Plugin 마이그레이션 검증
마이그레이션 가이드에 따라 내 Tauri 디버그 설정을 검토하세요. 로깅, 스크린샷, 권한, 파일 위치, 남아 있는 레거시 의존성을 확인하세요.
디버그 보고서 작성
프로세스 상태, 스크린샷 관찰 내용, 로그 통계, WebView 상태, 근본 원인 분석, 우선순위가 지정된 수정 사항을 바탕으로 전체 Tauri 디버그 보고서를 작성하세요.
모범 사례
- 가능하면 레거시 플랫폼 스크립트보다 공식 Tauri plugin을 먼저 사용하세요.
- 보고서를 공유하기 전에 스크린샷, 로그, 로컬 경로, URL, 사용자 이름, 명령 인수를 수정하거나 가리세요.
- 깊이 있는 디버깅 전에 검증을 실행하여 누락된 권한이나 plugin이 실제 문제를 숨기지 않도록 하세요.
피하기
- 앱 창 캡처로 충분한 경우 전체 모니터를 캡처하지 마세요.
- 민감한 콘텐츠를 검토하기 전에 원시 로그나 스크린샷을 외부 시스템에 붙여 넣지 마세요.
- 설정을 먼저 확인하지 않고 누락된 프로세스나 누락된 로그 파일을 애플리케이션 버그로 간주하지 마세요.
자주 묻는 질문
이 스킬은 무엇을 디버그하는 데 도움이 되나요?
스크린샷, 로그, 프로세스 상태, WebView 상태, 보고서 증거를 수집하여 Tauri WebView 문제를 디버그하는 데 도움이 됩니다.
Tauri v2가 필요한가요?
문서에서는 tauri-plugin-log 및 tauri-plugin-screenshots를 포함한 Tauri v2 호환 plugin을 전제로 합니다.
Windows와 Linux에서 실행할 수 있나요?
권장 plugin 워크플로는 크로스 플랫폼입니다. 레거시 캡처 스크립트는 macOS 전용입니다.
버그를 자동으로 수정하나요?
아니요. 개발자가 수정 사항을 선택하고 검증할 수 있도록 증거를 수집하고 정리합니다.
사용자는 어떤 데이터를 보호해야 하나요?
사용자는 공유 전에 스크린샷, 콘솔 로그, 로컬 파일 경로, URL, 프로세스 명령, WebView 상태를 검토해야 합니다.
어떤 AI 도구에서 사용할 수 있나요?
보고서에는 Claude, Codex, Claude Code 지원이 명시되어 있습니다.
개발자 세부 정보
작성자
8beeeaaat라이선스
MIT
Skillstore 리비전
r1
버전 안내
작성자가 버전을 선언하지 않았습니다.
참조
c4037264bbd363c572662d6154a3ab28f5ca4f53
유지보수 최신성
2026. 7. 18.
사용량
7 다운로드 · 223 조회
파일 구조
관련 스킬
전체 보기📦
code-context-finder
83코드 컨텍스트 더 빠르게 찾기
작성자 89jobrien
개발자는 코드가 왜 존재하는지, 무엇이 그 코드에 의존하는지 추적하느라 시간을 잃는 경우가 많습니다. 이 스킬은 변경 전에 Claude, Codex, 또는 Claude Code가 관련 그래프 지식, 호출자, imports, 테스트를 수집하도록 유도합니다.
코딩 및 개발 보기
📦
systematic-debugging
81소프트웨어 문제를 체계적으로 디버깅하기
작성자 Asmayaseen
구조화되지 않은 버그 수정은 시간을 낭비하고 실제 실패 원인을 숨길 수 있습니다. 이 스킬은 Claude, Codex, Claude Code가 증거 기반 근본 원인 분석을 수행하도록 안내합니다.
코딩 및 개발 보기
📦
context-degradation
81AI 에이전트의 컨텍스트 저하 진단
작성자 ChakshuGautam
긴 대화와 큰 프롬프트는 AI 에이전트가 중요한 정보를 놓치거나 상충되는 컨텍스트를 따르게 만들 수 있습니다. 이 skill은 Claude, Codex, Claude Code가 저하 패턴을 식별하고 완화 전략을 선택하도록 돕습니다.
코딩 및 개발 보기
📦
code-instructor
80앱을 만들며 코드 가르치기
작성자 Emz1998
예제가 실제 프로젝트와 동떨어져 있으면 코드 학습은 추상적으로 느껴질 수 있습니다. 이 스킬은 작동하는 애플리케이션을 단계별로 만들면서 개념을 가르칩니다.
코딩 및 개발 보기
📦
safe-debug
80딥러닝 오류를 안전하게 진단하기
작성자 lllllllama
학습 실패는 근본 원인이 명확해지기 전에 에이전트가 위험한 패치를 적용하게 만들 수 있습니다. 이 스킬은 보수적인 진단, 세이브포인트 계획, 승인 기반 수정을 안내합니다.
코딩 및 개발 보기