Analyze dlab session runs

Analyze dlab session directories, logs, and outputs to interpret run outcomes.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/benmaier/decision-agent-placeholder --skill analyze-dlab-session-runs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Analyze dlab session runs
Source: https://github.com/benmaier/decision-agent-placeholder/tree/main/.claude/skills/run-analyzer
Command: npx skills add https://github.com/benmaier/decision-agent-placeholder --skill analyze-dlab-session-runs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Navigate and analyze completed dlab session directories to understand what happened during a run — explore logs, outputs, parallel agent results, and the skills/prompts that shaped the analysis.

Core Features & Use Cases

  • Guided exploration of a dlab session: from state.json to orchestrator and parallel run outputs.
  • Inspect _opencode_logs and summary files to evaluate performance, diagnoses, and uncertainty handling.
  • Use for audits, debugging, and capacity planning of decision packs.

Quick Start

Open the session directory and review main.log, _opencode_logs, and parallel run summaries to assess agent behavior and results.

Frequently Asked Questions about Analyze dlab session runs

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

FAQPage Schema
How do I analyze dlab session logs to debug orchestrator behavior?

To analyze dlab session logs, open the session directory and examine main.log and _opencode_logs to trace orchestrator behavior, verify parallel agent results, and identify execution issues across runs.

What is the best way to audit parallel agent results in a completed dlab session?

Auditing parallel agent results involves inspecting the session's state.json and parallel run summary files to evaluate performance, diagnoses, and how well prompts and domain skills aligned with outcomes.

Can I use this approach to review decision-pack performance across multiple dlab runs?

Yes, you can review decision-pack performance by navigating completed session directories to compare outputs, assess uncertainty handling, and conduct capacity planning based on orchestrator and parallel run summaries.

How do I check uncertainty handling and diagnoses from dlab parallel run outputs?

Check uncertainty handling and diagnoses by inspecting the _opencode_logs and summary files within the session directory to evaluate how parallel agents processed diagnoses and managed uncertain outcomes.

What files do I need to inspect to verify dlab orchestrator behavior and session state?

You need to inspect the session directory's state.json, main.log, and _opencode_logs to verify orchestrator behavior, trace execution flow, and validate the alignment of prompts with results.