agent-log-analysis

Analyze agent session logs into standardized Markdown audit reports with root-cause analysis.

3|1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Cogni-AI-OU/cogni-ai-agent-skills --skill agent-log-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-log-analysis
Source: https://github.com/Cogni-AI-OU/cogni-ai-agent-skills/tree/main/agent-log-analysis
Command: npx skills add https://github.com/Cogni-AI-OU/cogni-ai-agent-skills --skill agent-log-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates guesswork when an AI agent fails by turning raw session logs into a standardized, evidence-based audit with the required root-cause analysis.

Core Features & Use Cases

  • Evidence-driven log forensics: Extracts prompts, tool calls, skill-loading attempts, and artifacts created during a run so you can see what really happened.
  • Standardized visual audit outputs: Produces a consistent reporting bundle including required diagrams and structured telemetry summaries for fast review.
  • Mandatory root cause analysis: Requires fishbone (Ishikawa) style reasoning when failures occur, preventing shallow “it failed” conclusions.

Quick Start

Use the agent-log-analysis skill to audit the provided agent session logs and produce the full standardized markdown report with diagrams and (if applicable) an Ishikawa root-cause section.

Frequently Asked Questions about agent-log-analysis

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

FAQPage Schema
How do I analyze agent logs to find the root cause of a failure?

Agent log analysis extracts prompts, tool calls, and artifacts from session logs to produce standardized audit reports. When failures occur, it applies mandatory fishbone root-cause analysis to generate remediation-ready findings.

What is fishbone root cause analysis for autonomous agent failures?

Fishbone root cause analysis is a required reasoning method used during agent log audits to prevent shallow conclusions. It structures the investigation into why an autonomous agent failed, ensuring evidence-based remediation findings.

Can I audit agent logs from GitHub Actions workflow runs?

Yes, agent log analysis applies to troubleshooting autonomous agent failures and verifying protocol compliance using GitHub Actions log artifacts. It processes these local and CI logs to generate structured telemetry summaries.

How do I verify skill loading and protocol compliance from session logs?

You verify skill loading and protocol compliance by using agent log analysis to extract skill-loading attempts and tool calls from session logs. This produces a standardized audit report with visualizations of tool utilization.

What does an agent log audit report include?

An agent log audit report includes mandatory structured Markdown output, extracted telemetry summaries, tool and command utilization visualizations, and an Ishikawa root-cause analysis section when errors are detected.

Does agent log analysis work without external dependencies or components?

Yes, agent log analysis operates with no external dependencies or components, processing raw session logs directly to generate standardized visual audit outputs and remediation-ready findings.