How do I install the Reflection skill?

Run npx skillmds@latest add davidkiss/reflection in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Reflection safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Reflection?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Reflection free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Reflection?

davidkiss (@davidkiss) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Reflection by davidkiss — Agent Skill

Name: Reflection
Rating: 4.2 (5 reviews)
Author: davidkiss

Reflection

MUST use this skill when user provides feedback / ask to do things in certain way, or when a tool call fails - for self-improvement - to learn user preferences and store them in AGENT.md / CLAUDE.md, and to propose improvements to skills.

davidkiss Updated Sep 10, 2026

File contents

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

Guidelines

One at a time: Only propose one change per invocation to maintain focus and allow for careful review.
Conciseness: Keep changes as brief as possible. Often a few words are enough to clarify a requirement or fix a common mistake.
Accuracy: Ensure the proposal directly addresses a real issue or preference observed in the session.
Specificity: Think how you could make the learnings more generic to apply to other use cases, but don't make the changes too generic so that it would not address the original learnings
Failure Analysis: Pay special attention to tool failures or when the user has to correct your approach. These are primary candidates for reflection.
Conflict Resolution: If a proposed change conflicts with details of an existing skill or user preference, propose a resolution that best serves the user's current intent.

---name: reflectiondescription: MUST use this skill when user provides feedback / ask to do things in certain way, or when a tool call fails - for self-improvement - to learn user preferences and store them in AGENT.md / CLAUDE.md, and to propose improvements to skills.---# Reflection Skill## OverviewThis 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.## Process1. **Analyze:** Review the conversation history, tool calls, and any failures or corrections from the user.2. **Identify:** Determine if a specific behavior should be codified in a skill or if a user preference has emerged.3. **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`.4. **Confirm:** Present the proposal to the user and ask for explicit confirmation without making any changes first.5. **Apply Changes:** Once user confirmed the changes, only then apply them## Guidelines- **One at a time:** Only propose one change per invocation to maintain focus and allow for careful review.- **Conciseness:** Keep changes as brief as possible. Often a few words are enough to clarify a requirement or fix a common mistake.- **Accuracy:** Ensure the proposal directly addresses a real issue or preference observed in the session.- **Specificity:** Think how you could make the learnings more generic to apply to other use cases, but don't make the changes too generic so that it would not address the original learnings- **Failure Analysis:** Pay special attention to tool failures or when the user has to correct your approach. These are primary candidates for reflection.- **Conflict Resolution:** If a proposed change conflicts with details of an existing skill or user preference, propose a resolution that best serves the user's current intent.

Frequently asked questions