skills.rest
deepklarity
deepklarityOFFICIAL
Explore all skills by this author →
Website𝕏@DeepKlarityGitHub

dk-local-logs

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
One-click install
npx skills add https://github.com/deepklarity/harness-kit --skill dk-local-logs
Or copy as Structured Prompt for Agent▼
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.

Related Skills

Explore More Software Engineering Skills→
intersystems-communityintersystems-community
27

objectscript-debugging

Diagnose IRIS runtime and compile errors using diagnostic packets and source mapping.

Official
Advanced
jackspacejackspace
16

error-debugger

Analyze error details and generate fixes with code examples.

Community
Advanced
IndustrialIndustrial

application-performance-performance-optimization

Profile and optimize backend, frontend, and database performance with load testing.

Community
Advanced
ByeongminLeeByeongminLee
2

log-analysis

Extract patterns from Apache, Nginx, application, and JSON logs for issue triage.

Community
Advanced