skills.rest
demithras
demithrasCOMMUNITY
Explore all skills by this author →
GitHub

retro

Automate structured retrospectives by collecting session data and evaluating tooling usage.

1|1|Updated Jan 27, 2026
Search Tags:#automation#beads#retro#entity-extraction#agent-analysis#improvement-issues
One-click install
npx skills add https://github.com/demithras/ClearMeta --skill retro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/demithras/ClearMeta/tree/main/.claude/skills/retro
Command: npx skills add https://github.com/demithras/ClearMeta --skill retro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines post-session reflection by automatically collecting and analyzing conversation data to reveal how tools, skills, and agents performed, reducing manual logging and guesswork.

Core Features & Use Cases

  • Auto-collection: Extract skills invoked, agents spawned, and friction signals from the session to generate a structured retrospective.
  • Entity extraction & persistence: Persist extracted entities to Obsidian vault for knowledge graph building and future reference.
  • Improvement planning: Propose beads issues and refinement opportunities, including automation candidates and orchestration improvements.
  • Use Case: End-of-day reviews, bead-based projects with repeated patterns, or major tool changes that require evaluation and learning.

Quick Start

After a significant beads session, run /retro to generate a structured retrospective with auto-collected data and suggested improvements.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I automate a retrospective from conversation data?▼

Automated retrospectives parse session data to extract invoked skills, spawned agents, and friction signals, generating a structured review to reduce manual logging and guesswork.

Can I persist extracted entities to an Obsidian vault during a retrospective?▼

Entity extraction persists collected entities to an Obsidian vault during retrospectives, building a knowledge graph for future reference and structured post-session analysis.

What is the best way to identify tooling friction in repeated interaction patterns?▼

Evaluating tooling usage in repeated interaction patterns identifies friction signals and proposes optimization, enabling actionable improvements and automation candidates.

How do I generate improvement issues after a beads project session?▼

Improvement planning proposes beads issues and refinement opportunities after a beads session, evaluating tooling usage and suggesting orchestration improvements via the /skill-farm workflow.

Do I need any dependencies to run end-of-session reviews?▼

End-of-session reviews require no dependencies, operating independently to auto-collect session data and generate structured retrospectives with suggested improvements.

When should I not use automated retros?▼

Automated retros suit significant sessions and repeated patterns; trivial or isolated interactions may lack sufficient data for meaningful entity extraction and improvement planning.

Related Skills

Explore More Data & Analytics Skills→
pradyumnasagarpradyumnasagar
6

agent-handoff

Automate inter-skill data transfer and provenance capture via JSON Material Passports.

Community
Advanced
kirvinkirvin

retro

Analyze git log and beads closed-issue data to generate improvement issues.

Community
Advanced
ethan-rioethan-rio

extract-graph

Extract entity-relation triples from Obsidian notes into graph memory stores.

Community
Intermediate
Snowflake-LabsSnowflake-Labs
12

read-ors-configuration

A concise summary of your roleplay character: name,</name> personality, and/or behavior, formatted as a single string sentence. Typically不超过50字，此处省略

Official
Intermediate