weekly-retro

You can automate a weekly retrospective report by aggregating system logs, git history, and scheduler execution data. This skill synthesizes internal telemetry to identify operational friction, error patterns, and productivity trends across your environment.

Monitoring system health weekly involves categorizing telemetry data into Shipped, Broke, Improved, Patterns, and Next Week sections. This structured approach drives continuous improvement by identifying error rates and operational friction without manual data gathering.

Yes, you can generate a performance summary from session and error logs. The skill requires read access to these logs alongside output directories to produce data-grounded reporting on agent activity and system health.

Tracking error patterns and operational friction requires synthesizing data from session logs, error logs, and git history. The skill processes this internal telemetry to identify recurring error patterns and productivity trends over a seven-day period.

Yes, this automated telemetry approach works without manual data gathering. It operates on internal telemetry by reading session logs and output directories to produce a structured weekly performance report automatically.

To generate automated weekly performance reports, you need read access to session logs, error logs, and output directories. The skill uses this access to aggregate git history and scheduler execution data for data-grounded reporting.