weekly-retro

Name: weekly-retro
Availability: InStock
Author: 0xursanomics

Aggregate system logs, git history, and scheduler data into a weekly retrospective report.

2|Updated Jul 22, 2026

Search Tags:#automation #logs #retrospective #reporting #telemetry #system-health

Ready to run

npx skills add https://github.com/0xUrsanomics/utopia-os --skill weekly-retro-0xursanomics

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: weekly-retro
Source: https://github.com/0xUrsanomics/utopia-os/tree/main/skills/weekly-retro
Command: npx skills add https://github.com/0xUrsanomics/utopia-os --skill weekly-retro-0xursanomics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of fragmented operational visibility by aggregating logs, git history, and scheduler data into a cohesive weekly performance report.

Core Features & Use Cases

Automated Telemetry: Synthesizes data from session logs, error logs, and git history to identify trends.
Operational Insights: Categorizes activity into Shipped, Broke, Improved, Patterns, and Next Week to drive continuous improvement.
Use Case: Use this on Sunday mornings to generate a concise summary of the past week's agent activity, error rates, and system health without manual data gathering.

Quick Start

Run the weekly retro skill to generate a performance report for the past seven days.

Frequently Asked Questions about weekly-retro

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

FAQPage Schema

How do I automate a weekly retrospective report from system logs and git history?▼

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.

What is the best way to monitor agent system health and performance weekly?▼

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.

Can I generate a performance summary from session logs and error logs?▼

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.

How do I track error patterns and operational friction in my agent environment?▼

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.

Does this weekly reporting approach work without manual data gathering?▼

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.

What access do I need to generate automated weekly performance reports?▼

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.