agent-monitoring-retro

Generates retrospective reports from agent monitoring runs.jsonl and events.jsonl data.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/ttnhan18062000/rpg-based-simulation --skill agent-monitoring-retro-ttnhan18062000
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-monitoring-retro
Source: https://github.com/ttnhan18062000/rpg-based-simulation/tree/main/.agents/skills/agent-monitoring-retro
Command: npx skills add https://github.com/ttnhan18062000/rpg-based-simulation --skill agent-monitoring-retro-ttnhan18062000

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Accumulated agent run and event logs are hard to act on without aggregation; this Skill turns raw monitoring records into a structured weekly retro report so failures, slow phases, and prompt problems actually get identified and fixed. ## Core Features & Use Cases - Automated Report Generation: Runs make agent-monitoring-retro to produce RETRO-<week>.md from runs.jsonl and events.jsonl, updating the retro index automatically. - Guided Retrospective Analysis: Walks through run summary, gate failure breakdown, tier distribution, agent status, summary quality, and slow runs, then fills the Notes section with concrete findings and one action per issue. - Data Integrity Validation: Cross-checks with make agent-monitoring-validate so DONE log entries, run records, and events stay consistent before trusting the numbers. - Use Case: At the start of a sprint, run the retro to discover that a specific gate blocks most runs and that hotfix tickets are not taking the fast path, then commit the annotated report as institutional memory. ## Quick Start Ask the assistant to generate this week's agent monitoring retro report and summarize the findings that need action.

Frequently Asked Questions about agent-monitoring-retro

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

FAQPage Schema
How do I generate an agent monitoring retro report?

Run `make agent-monitoring-retro` to generate the report for the current ISO week. It invokes tools/agent-monitoring/generate_retro.py, writes agent-monitoring/retro/RETRO-<week>.md, and updates the retro index automatically.

How to generate a retro report for a specific week or time range?

Call the generator directly with a window flag: `python3 tools/agent-monitoring/generate_retro.py --week 2026-W23` for a specific week, `--days 30` for a rolling window, or `--all` for all recorded data.

When should I run the agent monitoring retrospective?

Run it weekly, at the start of a new sprint, after every 5 or more completed tickets, or before changing any agent prompt, workflow phase, or tier routing rule. A PostToolUse hook nudges you automatically once 5+ runs complete.

How do I verify agent monitoring data integrity before trusting the report?

Run `make agent-monitoring-validate` before reading the numbers. It checks that every DONE working_log.csv entry has a matching run record, every run has at least one event, and no crashed run is silently treated as complete.

What metrics does the agent retro report include?

The report covers run summary (DONE rate, average duration), gate failure breakdown, tier distribution, agent status distribution, summary quality, and slow runs over 30 minutes with the phase that caused them.