dev-session-debug

Diagnose and repair inconsistencies in Capsem session telemetry data.

68|10|Updated Sep 26, 2025
One-click install
npx skills add https://github.com/google/capsem --skill dev-session-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-session-debug
Source: https://github.com/google/capsem/tree/main/skills/dev-session-debug
Command: npx skills add https://github.com/google/capsem --skill dev-session-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The session telemetry debugging workflow identifies and diagnoses inconsistencies in Capsem's session databases, helping ensure data integrity across session.db and main.db rollups.

Core Features & Use Cases

  • Validate table existence, row counts, and cross-table relationships within telemetry data (net_events, model_calls, tool_calls, mcp_calls, fs_events).
  • Detect orphaned records, correlation mismatches, and data quality issues to support QA, auditing, and incident response.
  • Use cases include investigating missing or mismatched entries across sessions, tracing tool call lifecycles, and ensuring per-session telemetry reliability.

Quick Start

Inspect the most recent Capsem session database to diagnose telemetry integrity.

Frequently Asked Questions about dev-session-debug

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

FAQPage Schema
How do I debug inconsistencies in Capsem session telemetry databases?

You can trace tool call lifecycles by correlating model_calls with net_events and mcp_calls, verifying correct MCP-tool linkage and data consistency to ensure per-session telemetry reliability during QA and incident response.

What causes orphaned records and correlation mismatches in SQLite telemetry data?

Orphaned records and correlation mismatches in SQLite telemetry data occur when cross-table relationships between net_events, model_calls, tool_calls, and mcp_calls break, which you can detect by validating row counts and table existence during debugging.

How do I verify row counts and table existence across session.db and main.db rollups?

Verify row counts and table existence across session.db and main.db rollups by inspecting the most recent Capsem session database, diagnosing telemetry integrity to generate actionable findings and recommended fixes for any missing entries.

Can I use session telemetry debugging for QA auditing and incident response?

Yes, session telemetry debugging supports QA, auditing, and incident response by detecting orphaned records, tracing tool call lifecycles, and ensuring per-session telemetry reliability across SQLite session and main database rollups.

Why does my MCP tool call linkage show mismatched entries across sessions?

MCP tool call linkage shows mismatched entries across sessions due to broken correlations between mcp_calls and model_calls, requiring a debugging workflow to correlate these tables and ensure correct MCP-tool linkage with actionable findings.