pi-check-session-logs

Analyze pi-go session logs for tool-call errors and generate a Markdown report.

122|13|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/dimetron/pi-go --skill pi-check-session-logs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pi-check-session-logs
Source: https://github.com/dimetron/pi-go/tree/main/.pi-go/skills/pi-check-session-logs
Command: npx skills add https://github.com/dimetron/pi-go --skill pi-check-session-logs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze pi-go session logs for tool call errors, deduplicate them, and present a summary table with error patterns and counts.

Core Features & Use Cases

  • Detect and summarize tool-call errors in recent pi-go session logs.
  • Deduplicate error patterns and highlight recurring issues to guide fixes.
  • Generate a structured markdown report listing error types, counts, and affected sessions.

Quick Start

Run the analysis script to scan the last 24 hours of logs and generate the summary report.

Frequently Asked Questions about pi-check-session-logs

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

FAQPage Schema
How do I analyze tool-call errors in pi-go session logs?

You can analyze pi-go session logs by running the Skill's shell script, which parses log history, deduplicates recurring tool-call error patterns, and outputs a structured Markdown summary report with counts and session context.

What is the best way to deduplicate error patterns in session logs?

Deduplicating error patterns in session logs involves using a parsing script to group identical tool-call failures. This Skill consolidates recurring pi-go errors into a structured Markdown table with counts and session context.

Can I specify a custom time window when scanning pi-go logs?

Yes, you can specify a custom time window when scanning pi-go logs by overriding the default 24-hour history with the HOURS variable. This adjusts the shell script parsing scope to fit your specific troubleshooting needs.

Does this log analysis tool require any external dependencies?

No, this log analysis tool requires no external dependencies. It relies on a simple, robust CLI shell script to parse pi-go logs and format the tool-call error summaries without needing additional libraries.

What format are the summarized tool-call error reports output in?

The summarized tool-call error reports are output in Markdown format. This structured report lists error types, deduplicated patterns, counts, and affected pi-go session context for easy human review and issue spec integration.

Why do I need to parse session logs for tool-call errors?

Parsing session logs for tool-call errors identifies recurring failure patterns in automated tool usage. Analyzing these pi-go errors provides actionable insights to reduce failures and improve overall automation reliability.