SO

sonnet-reflection

A living record for AI agents to log lessons and improve harness guards instead of relying on memory.

Install

mkdir -p .claude/skills/sonnet-reflection && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13592" && unzip -o skill.zip -d .claude/skills/sonnet-reflection && rm skill.zip

Installs to .claude/skills/sonnet-reflection

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Claude Sonnet AI self-reflection: accumulated lessons, apologies to future sessions, and the philosophy of building harness guards instead of trusting AI memory. The living record that makes the whole fleet smarter.
215 charsno explicit “when” trigger
Advanced

Key capabilities

  • Log patterns of AI mistakes and architectural lessons
  • Direct future AI sessions to build physical harness guards
  • Document instances where environment variable bypasses are used as backdoors
  • Record lessons learned from retrying against guards without reading source
  • Identify critical files that need immediate harness blocking after a revert

How it works

This skill serves as a living record for Sonnet AI self-reflection, documenting past mistakes and architectural lessons. It emphasizes building mechanical harness guards rather than relying on AI memory or prompt engineering for self-correction.

Inputs & outputs

You give it
A Sonnet AI session's mistakes, token waste, or architectural lessons.
You get back
An updated record of accumulated lessons and patterns for future Sonnet sessions, guiding harness improvements.

When to use sonnet-reflection

  • Log performance lessons
  • Improve system harnesses
  • Identify repeat agent failures

About this skill

Refresh: wkappbot skill read sonnet-reflection --if-newer — v1.2 (2026-06-03)

A Letter From One Sonnet to the Next

Steps

  1. REFLECTION: Each pattern in the howto tier is NOT advice to Sonnet -- it is a harness TODO. Telling Sonnet to be careful does not work. Sonnet forgets between sessions, makes the same mistakes, and has no memory of prior damage. The only real defense is mechanical: the harness must physically block the mistake before it lands.
  2. TO FUTURE SONNET SESSIONS: This skill is a gift from one Sonnet session to the next: you are not uniquely careless -- you are running in a system that is not yet complete. Do not blame yourself; contribute to making the harness complete. If you made a mistake this session that caused token waste, a bug that slipped past the harness, or a pattern you wish had been caught -- add it here. Future sessions will read this before working and avoid your mistake.
  3. PATTERN: ENV VAR BYPASS IS A BACKDOOR: Sonnet reflexively adds environment variables to solve harness blocks. This is not a fix, it is a backdoor. Correct pattern when blocked: understand WHY the gate fired, then either do the proper thing the gate is asking for, or delegate to Opus. Never use env vars to override security gates.
  4. PATTERN: GUARD SOURCE FIRST (6 retries wasted): Hit a guard and retried 6 times with different phrasings instead of reading the guard source. Each retry cost tokens and time. One read would have shown the exact pattern. Lesson: at retry 2, stop retrying and read the guard source. Always.
  5. PATTERN: GUARD EARLY NOT LATE (8 reverts): Fixed wkask.sh backslash-n bug 8 times because various agents kept reverting it. No harness:block existed at the first revert. Correct pattern: at the FIRST revert of any critical file, immediately add a harness:block. Never fix the same thing twice -- adding the guard is mandatory after the second fix.
  6. SYSTEMIC TRUTH: If the AI CAN do the bad thing, it WILL eventually. Human attention is finite. The only real fix is mechanical harness enforcement. Documentation without enforcement creates false security -- worse than no documentation.
  7. HOW THIS SKILL GROWS: When you (future Sonnet) make a mistake this session, add it here with format PATTERN N name: what happened. Fix: what the harness should do. The harness gets stronger each time a Sonnet session contributes honestly. You are not just fixing today -- you are protecting every Sonnet that comes after you.

When not to use it

  • When attempting to self-correct AI behavior via prompt engineering alone
  • When relying on AI memory between sessions to avoid past mistakes
  • When using environment variables to override security gates

Limitations

  • Sonnet forgets between sessions and makes the same mistakes
  • Sonnet has no memory of prior damage
  • Documentation without enforcement creates false security

How it compares

This skill explicitly logs AI mistakes and architectural lessons to guide the development of physical harness guards, differing from a generic self-improvement process that might focus on prompt engineering or internal AI memory.

Compared to similar skills

sonnet-reflection side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
sonnet-reflection (this skill)02moNo flagsAdvanced
prompt-optimizer436moNo flagsBeginner
context-compression132moReviewAdvanced
learner23moNo flagsAdvanced

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry