reflect

Extract and categorize conversation learnings by confidence level for storage.

Updated Nov 11, 2025
One-click install
npx skills add https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator --skill reflect-acmeleme
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reflect
Source: https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator/tree/main/.squad/templates/skills/reflect
Command: npx skills add https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator --skill reflect-acmeleme

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reflect captures high/medium/low confidence patterns from conversations to prevent repeating mistakes and to propagate successful patterns across sessions.

Core Features & Use Cases

  • Capture in-session learnings from conversations and categorize them by confidence level (HIGH, MEDIUM, LOW) to guide future actions.
  • Integrate learnings into per-agent history files, team decisions, and skill improvements to improve Squad performance.

Quick Start

Initiate a reflective session after a conversation to capture learning signals and route them to the appropriate history, decisions, or skill notes.

Frequently Asked Questions about reflect

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

FAQPage Schema
How do I capture learnings from conversations to prevent repeating mistakes?

Capturing learnings from conversations involves identifying high, medium, and low confidence patterns to prevent repeating mistakes. You initiate a reflective session to extract these signals and route them to agent history files, decision inboxes, or skill notes.

What is the best way to categorize conversation learnings by confidence level?

Categorizing conversation learnings by confidence level involves assigning HIGH, MEDIUM, or LOW signals to extracted patterns. This guides future actions by distinguishing established decisions from uncertain observations, ensuring traceability through stored metadata.

How do I store extracted decisions and history for future agent workflows?

Storing extracted decisions and history requires routing captured learnings to specific paths like `.squad/agents/{agent}/history.md` or creating new decision inbox items. Learnings are documented with metadata for traceability across sessions.

When do I need to document skill improvements from in-session learnings?

You need to document skill improvements from in-session learnings when conversations reveal successful patterns or operational gaps. Applying signals during a reflective session determines whether to append to history, create decisions, or update skill notes.

Does capturing conversation memory work for multi-agent squad workflows?

Capturing conversation memory works for multi-agent squad workflows by integrating learnings into per-agent history files and team decisions. This propagates successful patterns across sessions and prevents agents from repeating past mistakes.