dk-local-logs

Name: dk-local-logs
Availability: InStock
Author: DeepKlarity

Locate and read backend, frontend, celery, odin, or task execution logs to diagnose harness-kit errors.

87|12|Updated Mar 1, 2026

Search Tags:#debugging #logs #frontend #backend #diagnostics #odin #log-inspector

Ready to run

npx skills add https://github.com/deepklarity/harness-kit --skill dk-local-logs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dk-local-logs
Source: https://github.com/deepklarity/harness-kit/tree/main/.claude/skills/dk-local-logs
Command: npx skills add https://github.com/deepklarity/harness-kit --skill dk-local-logs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and inspect the correct log source across backend, frontend, celery, odin, and task execution to diagnose errors quickly.

Core Features & Use Cases

Cross-layer log selection and tailing to triage issues without guessing where they originate.
Guided commands and references for common failure modes across harness-kit components.
Use case: when a 500 error or stack trace appears, quickly locate the relevant log and extract actionable details for remediation.

Quick Start

Start the log inspector against the harness-kit stack to diagnose and triage errors quickly.

Frequently Asked Questions about dk-local-logs

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

FAQPage Schema

How do I locate backend or frontend logs to diagnose a 500 error?▼

To diagnose 500 errors, locate and read the correct log source across backend, frontend, celery, odin, or task execution layers. The inspector auto-detects the appropriate layer when none is specified, extracting actionable details from stack traces.

What is the best way to triage startup failures across multiple application layers?▼

Triage startup failures by selecting and tailing logs across backend, frontend, celery, odin, and task execution layers. Cross-layer log selection isolates the failing component without guessing the origin, providing structured diagnostics for remediation.

Can I use grep-based searches to find specific errors in structured application logs?▼

Yes, you can use optional grep-based searches against structured log formats to pinpoint specific errors. This allows targeted extraction of stack traces and failure details from the correct log source for rapid diagnosis.

Does the log inspector support auto-detection when no specific application layer is specified?▼

Yes, the log inspector supports auto-detection to locate the correct log source when no specific layer is specified. It reads backend, frontend, celery, odin, or task execution logs to diagnose errors and provide actionable diagnostics.

How do I diagnose migration errors in a monorepo with multiple service layers?▼

Diagnose migration errors by reading the correct log source across backend, celery, odin, and task execution layers. The inspector applies guided commands to parse structured logs and extract actionable details for remediation across the monorepo.