session-analyzer

Validate Claude Code session execution against SKILL.md definitions from debug logs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the post-hoc analysis of Claude Code sessions, ensuring that skills and agents behave as defined in their SKILL.md specifications and identifying any deviations or bugs.

Core Features & Use Cases

  • Behavior Validation: Compares actual session execution against expected behavior defined in SKILL.md.
  • Component Verification: Checks SubAgent invocations, Hook execution, and Tool usage.
  • Artifact Auditing: Verifies the creation and deletion of expected files.
  • Bug Detection: Identifies errors, unexpected deviations, and potential issues.
  • Use Case: After a complex multi-agent session, use this Skill to automatically generate a report confirming that all steps were executed correctly, all hooks fired as expected, and the final output matches the SKILL.md requirements.

Quick Start

Analyze session 'a1b2c3d4-e5f6-7890-1234-567890abcdef' against the skill definition at '.claude/skills/my-skill/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 validate Claude Code agent behavior against a SKILL.md definition?

To validate Claude Code agent behavior, this Skill parses debug logs to compare actual session execution against expected outcomes defined in SKILL.md. It checks SubAgent calls, hook events, tool usage, and artifact creation to detect deviations.

What is the best way to debug unexpected SubAgent calls and hook events in a session log?

Debugging unexpected SubAgent calls and hook events involves analyzing session debug logs to verify component behavior. This Skill automatically parses logs to identify execution deviations and unexpected hook firing during the session.

Can I audit file artifact creation and deletion after a complex multi-agent session?

Yes, you can audit artifact creation and deletion. This Skill verifies expected file operations by parsing session debug logs and comparing actual artifact behavior against the requirements defined in your SKILL.md specification.

What do I need to generate a session analysis report for skill validation?

To generate a session analysis report for skill validation, you need access to the session debug logs and the target SKILL.md file. The Skill uses these inputs to compare actual execution against defined expectations.

Why does my Claude Code session deviate from the expected tool usage defined in my skill?

Session deviations from expected tool usage occur when actual execution mismatches the SKILL.md specification. This Skill detects these bugs by parsing debug logs to identify unexpected tool invocations and component behavior.

Are there limitations when analyzing multi-agent session logs for component verification?

Analyzing multi-agent session logs requires complete debug log access and a defined SKILL.md file. The analysis is limited to verifying SubAgent invocations, hook execution, tool usage, and artifact operations recorded in the provided logs.