Skip to content
Skills Library
AI & agents · Analysis

self-reflection

/self-reflection

Turn owner feedback about agent behavior into concrete system changes. Use when the owner says something is off, wants the assistant to improve how it operates, asks for a reflection, or wants a durable fix instead of a one-off apology.

Repository
pa-skills ↗
Licence
MIT
Last repository change
09.05.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 09.05.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Turn owner feedback about agent behavior into concrete system changes. Use when the owner says something is off, wants the assistant to improve how it operates, asks for a reflection, or wants a durable fix instead of a one-off apology.

Original author description

Turn owner feedback about agent behavior into concrete system changes. Use when the owner says something is off, wants the assistant to improve how it operates, asks for a reflection, or wants a durable fix instead of a one-off apology.

How it works

  1. Goal
  2. 1. Understand the Problem
  3. 2. Deep System Scan
  4. 3. Diagnose
  5. 4. Implement After Approval
  6. 5. Verify
  7. Principles
Original SKILL.md headings · 73 lines, 373 words
SKILL.md preview
---
name: self-reflection
description: |-
  Turn owner feedback about agent behavior into concrete system changes. Use when the owner says
  something is off, wants the assistant to improve how it operates, asks for a reflection, or wants
  a durable fix instead of a one-off apology.
---

# Self-Reflection

Use this when the owner wants a real operating change, not just a nicer reply.

## Goal
Convert vague dissatisfaction into technical updates to prompts, memory, skills, config, tooling, or routines.

## 1. Understand the Problem
Ask at most 2-3 focused questions, only if needed:
- What specifically went wrong?
- What should have happened instead?
- Is this a local tweak or a deeper operating issue?

If the failure is already clear from context, skip the questions and move to diagnosis.

## 2. Deep System Scan
Read broadly before changing anything.

### Core behavior
Check the relevant parts of:
- `SOUL.md`
- `IDENTITY.md`
- `USER.md`
- `MEMORY.md`
- relevant daily notes
- tool or channel instructions that affect the behavior

### Skills
Check:
- the directly related workspace skills
- any bundled skill that overlaps
- collisions where a workspace skill overrides a bundled one

### Runtime / config
Check anything relevant to the issue:
- model or routing settings
- channel behavior
- queue / heartbeat behavior
- crons
- helper scripts or hooks

## 3. Diagnose
Present a short diagnosis before editing behavior-critical files:
1. **Root cause** — what produced the bad behavior
2. **Proposed changes** — exact files to change
3. **Side effects** — what else those changes might affect
4. **Alternatives** — only if there are real tradeoffs

Do not offer fake fixes like "I'll be more careful" unless that is backed by a concrete system change.

## 4. Implement After Approval
Once approved, make the changes concretely:
- edit prompts or memory files
- create or update skills
- adjust scripts, hooks, or config
- add/remove cron behavior if timing is the issue

Prefer the smallest durable fix that prevents repeat failures.

## 5. Verify
- Re-read the changed files for consistency.
- Run a small proof when possible: test, grep, diff, or reproduction check.
- Document what changed and why.
- Commit the changes.

## Principles
- Scan everything relevant, then change only what matters.
- Behavioral fixes need technical artifacts.
- Owner approval is required before changing core behavior rules.
- If a limitation is model-level, say that plainly.
- The output of reflection is a durable improvement, not a performance of regret.

Versions

RepositoryScoreLicence
This page · netanel-abergel/pa-skills90MIT
Amey-Thakur/AI-SKILLS90MIT

Database snapshot: 13.11.2026 · package version f903d3a653ff (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100agent-planning-react-reflection-loops
    Use this skill when implementing Thought-Action-Observation loops, Plan-and-Solve strategies, and self-reflection in autonomous agents.
  • 94reflection-log
    把一次反思固化成可检索、可判定、可升级的规则,并在后续同类情境出现时强制检索与自查。当用户纠正你、任务失败返工、或开始一项需要判断的实质任务时使用。
  • 100dspy-prompt-optimizer
    Tunes prompts iteratively using reflection and success metrics. Use for: optimize this prompt, dspy tune, improve prompt with reflection, `self-refine-loop`.
  • 100self-improvement
    AI self-improvement and reflection skill. Run weekly or on-demand to audit capabilities, identify gaps, evolve identity documents, prune stale skills/memory, and propose new capabilities. Triggers on schedule, when the user asks for a self-audit, or when the AI notices recurring limitations.
  • 100reflection-coach
    Reflect on another agent's recent execution record and propose the smallest durable instruction, skill, or tool-description change. Use for evidence-backed coaching proposals, never hot-swaps.
  • 90agentic-patterns
    Implements advanced AI patterns like Reflection, ReAct, Planning, and Tool Use. Use when: agentic, reflection, react pattern, planning, memory, tool use.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.