retro-analysis

Generate team analytics retrospectives from notebooks, velocity, and reproducibility trends.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/tim-krausz/mlstack --skill retro-analysis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro-analysis
Source: https://github.com/tim-krausz/mlstack/tree/main/retro-analysis
Command: npx skills add https://github.com/tim-krausz/mlstack --skill retro-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analytics team retrospective. Analyzes analysis velocity, reproducibility rate, methodology quality, notebook production, and insight yield with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas for data skills.

Core Features & Use Cases

  • Generates a comprehensive analytics retrospective analyzing notebooks produced, methodology quality, reproducibility, and insight yield over time.
  • Breaks down per-person contributions, enabling peer praise and targeted growth planning.
  • Provides persistent history and trend tracking to monitor improvements across sprints or windows.

Quick Start

Use the /retro-analysis command to generate a retrospective for the current window.

Frequently Asked Questions about retro-analysis

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

FAQPage Schema
How do I run an analytics retrospective for my data science team?▼

To run an analytics retrospective, use the /retro-analysis command to generate a structured narrative and trend tables from your team's notebooks, velocity, and reproducibility data.

What metrics are analyzed in a data science team retrospective?▼

A data science team retrospective analyzes analysis velocity, reproducibility rate, methodology quality, notebook production, and insight yield, while tracking persistent trends over time.

Can I track per-person contributions during a sprint retrospective?▼

Yes, the retrospective breaks down per-person contributions to enable peer praise and targeted growth planning for data skills across sprints, weeks, or custom windows.

Do I need commit histories and analysis plans to generate a team analytics retrospective?▼

Yes, generating a retrospective requires access to commit histories, notebook inventories, and analysis plans to accurately track improvements and output trend tables.

How does tracking reproducibility rate improve team velocity?▼

Tracking reproducibility rate alongside velocity identifies methodology bottlenecks, enabling targeted process improvements that boost overall team velocity and insight yield over time.