server-diagnostics

Diagnose server-side issues by analyzing JSONL logs from data/logs/server.jsonl.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/tylermorganme/crop_plan_2025 --skill server-diagnostics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: server-diagnostics
Source: https://github.com/tylermorganme/crop_plan_2025/tree/main/.claude/skills/server-diagnostics
Command: npx skills add https://github.com/tylermorganme/crop_plan_2025 --skill server-diagnostics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables rapid diagnosis of server-side issues by analyzing JSONL logs produced by server components. It helps identify slow operations, migration problems, data inconsistencies, and unexpected user-session events.

Core Features & Use Cases

  • Log inspection and filtering: Inspect data/logs/server.jsonl to surface slow API calls, errors, and migrations.
  • Event pattern analysis: Detect common patterns such as high durationMs, repeated migrations, or missing checkpoints.
  • Guided investigation: Provide step-by-step diagnostics and recommended follow-ups for incident response or performance tuning.

Quick Start

Use this skill to inspect the server logs and begin diagnosing issues. Start by listing recent logs and filtering for long durations:

  • tail -30 data/logs/server.jsonl
  • grep '"durationMs"' data/logs/server.jsonl | jq 'select(.durationMs > 100)'
  • grep '"event":"error"' data/logs/server.jsonl | jq . If you need deeper inspection, inspect specific plan or request context via related events such as hydration, migration, and checkpoint.

Frequently Asked Questions about server-diagnostics

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

FAQPage Schema
How do I debug slow API calls and errors from JSONL server logs?

To debug slow API calls and errors from JSONL server logs, you filter the log file for events with high durationMs values or error event types to surface performance bottlenecks and failures. This identifies slow operations and unexpected user-session events for diagnostic guidance.

What is the best way to diagnose server migration problems using JSONL logs?

Diagnosing server migration problems using JSONL logs involves inspecting the log file to detect repeated migration events or missing checkpoints. Analyzing these specific event patterns reveals data inconsistencies and migration failures for guided investigation.

Can I use this approach to analyze session traces and hydration events?

Yes, you can analyze session traces and hydration events by reading the JSONL log format and identifying specific event types like hydration and checkpoint. This surfaces unexpected user-session events and provides step-by-step diagnostic guidance.

What command patterns help filter long-running operations in server logs?

Command patterns to filter long-running operations in server logs include using grep with jq to select JSON entries where durationMs exceeds a threshold, such as filtering for values greater than 100. This isolates slow operations for performance tuning and incident response.

Do I need a specific log format to diagnose server-side issues?

Yes, you need server components to generate logs in JSONL format, specifically stored at data/logs/server.jsonl. The diagnostic process relies on reading this structured file format to identify events like api_call, patch_save, and checkpoint for incident response.