session-analyzer

Validate Claude Code session logs against SKILL.md specifications.

1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/mrsono0/lecture_factory --skill session-analyzer-mrsono0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-analyzer
Source: https://github.com/mrsono0/lecture_factory/tree/main/.claude/skills/session-analyzer
Command: npx skills add https://github.com/mrsono0/lecture_factory --skill session-analyzer-mrsono0

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you understand exactly how a previous AI session executed, allowing you to verify if it followed its intended logic and identify any unexpected behavior or errors.

Core Features & Use Cases

  • Post-hoc Analysis: Review past session logs to validate skill execution against specifications.
  • Component Verification: Check if sub-agents, hooks, and tools were called correctly and in the expected order.
  • Artifact Validation: Confirm that expected files were created or deleted as part of the session.
  • Bug Detection: Identify deviations from the defined workflow that might indicate bugs.
  • Use Case: After a complex coding session, use this Skill to confirm that the code-generator sub-agent was called before the reviewer agent, and that the final output file was created as specified in the SKILL.md.

Quick Start

Analyze session 3cc71c9f-d27a-4233-9dbc-c4f07ea6ec5b against .claude/skills/specify/SKILL.md.

Frequently Asked Questions about session-analyzer

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

FAQPage Schema
How do I verify if an AI session followed its execution specifications?

To analyze session logs for workflow adherence, provide a specific session ID and the target SKILL.md path. The tool validates component invocations, artifact creation, and execution order against the defined specifications to detect deviations.

How do I check if sub-agents and hooks were called in the correct order during a session?

You can check sub-agent and hook invocation order by running a post-hoc session analysis. This process reviews execution logs to confirm that tools and agents were called correctly and followed the expected sequence defined in the skill specifications.

What is post-hoc session log analysis used for in software troubleshooting?

Post-hoc session log analysis is used to review past AI coding sessions and validate skill execution. It confirms whether expected files were created and identifies deviations from the defined workflow that might indicate bugs or unexpected behavior.

Can I validate artifact creation and file generation from a previous coding session?

Yes, you can validate artifact creation by analyzing session logs against target specifications. This checks whether expected files were created or deleted as part of the session workflow, confirming that the execution produced the required artifacts.

What information do I need to start analyzing a Claude Code session log?

To start analyzing a Claude Code session log, you need a specific session ID and the file path of the target SKILL.md. These inputs allow the tool to perform post-hoc verification of skill, agent, and hook behavior.

Why does my AI session deviate from the defined workflow in SKILL.md?

Session deviations occur when component invocations or artifact creation do not match the SKILL.md specifications. By analyzing session logs, you can identify exactly where the execution diverged from the expected workflow and detect potential bugs.