reflection

SKILL.md

Analyzes conversation patterns and tool usage to propose targeted skill improvements or user preferences.

Reviews conversation history and tool failures to identify gaps in skill definitions or recurring user preferences

Proposes one change at a time (either a skill update shown as a diff or a preference addition to CLAUDE.md) for focused review

Requires explicit user confirmation before applying any changes to skills or preference files

Prioritizes failure analysis and user corrections as primary signals for improvement opportunities

Reflection Skill

Overview

This skill is used to learn from interaction with the user and failures in tool calls. It analyzes what worked, what didn't (tool failures), and identifies recurring patterns or explicit user preferences that should be formalized.

Objectives

Improve Skills: Identify gaps or inefficiencies in existing skill definitions and propose concise updates.

Store Preferences: Capture user preferences, project-specific rules, or recurring instructions in a AGENT.md or CLAUDE.md (when used in Claude Code) file.

Process

Analyze: Review the conversation history, tool calls, and any failures or corrections from the user.

Identify: Determine if a specific behavior should be codified in a skill or if a user preference has emerged.

Propose: Formulate a single, concise change.

If updating a skill, show a diff of the proposed change.

If adding a preference, show the proposed addition to CLAUDE.md.

Confirm: Present the proposal to the user and ask for explicit confirmation without making any changes first.

Apply Changes: Once user confirmed the changes, only then apply them