skills.rest
patrickjaja
patrickjajaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

debug

Collect session transcripts, logs, and daemon state to diagnose Claude Desktop and cowork failures.

Updated Jul 30, 2026
Search Tags:#troubleshooting#logs#audit#debug#diagnostics#jsonl
One-click install
npx skills add https://github.com/patrickjaja/claude-desktop-bin --skill debug-patrickjaja
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/patrickjaja/claude-desktop-bin/tree/main/.claude/skills/debug
Command: npx skills add https://github.com/patrickjaja/claude-desktop-bin --skill debug-patrickjaja

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps diagnose broken Claude Desktop and cowork behavior by gathering the right local evidence first, so you can avoid guessing at the cause of an issue.

Core Features & Use Cases

  • Session Transcript Review: Pulls the newest local-agent-mode audit trail to see the exact user prompt, tool calls, and any errors the model encountered.
  • Log Collection and Triage: Checks Claude Desktop logs, crash reports, and cowork-svc daemon output to surface permission errors, missing files, protocol drift, and runtime failures.
  • Targeted Troubleshooting: Useful for dispatch problems, cowork failures, profile/path mismatches, and computer-use issues where the root cause depends on local state and recent activity.

Quick Start

Ask the debug skill to collect the newest audit transcript, Claude logs, and cowork-svc output for your issue, then summarize the most likely cause and what extra evidence is still needed.

Frequently Asked Questions about debug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I troubleshoot Claude Desktop crashes and cowork failures?▼

Diagnose broken Claude Desktop behavior by collecting the newest local-agent-mode audit transcript, relevant logs, and daemon state to identify the exact tool calls and errors the model encountered.

How do I find the root cause of a cowork dispatch or computer use failure?▼

Pinpoint cowork dispatch and computer use failures by gathering local evidence including the newest session transcript, Claude logs, and cowork-svc daemon state to surface runtime errors and protocol drift.

What logs do I need to diagnose broken Claude Desktop behavior?▼

To diagnose broken Claude Desktop behavior, collect the newest session transcript, Claude Desktop logs, crash reports, and cowork-svc daemon output to surface permission errors, missing files, protocol drift, and runtime failures.

Can I debug profile or patch-related failures using local session transcripts?▼

Debug profile and patch-related failures by collecting the newest local-agent-mode session transcript and relevant logs to review exact user prompts, tool calls, and errors that determine the root cause from local state.

What should I do if Claude Desktop logs are incomplete for troubleshooting?▼

When available data is incomplete during troubleshooting, ask targeted follow-up questions and ensure accurate configuration-path resolution to gather sufficient local evidence for determining the root cause.

Related Skills

Explore More Software Engineering Skills→
BryceEWatsonBryceEWatson

chat-history-search

Search local Claude chat histories across CLI JSONL and Cowork transcripts.

Community
Advanced
korchasakorchasa

flowai-reflect-by-history

Analyze historical IDE session transcripts to classify recurring agent behavior patterns and issues.

Community
Advanced
jshsakurajshsakura
22

error-coordinator

Organize scattered error signals into a prioritized triage map.

Community
Advanced
johnnymo87johnnymo87
4

notify-telegram

Register Claude Code sessions with a Telegram webhook daemon for notifications.

Community
Intermediate