cuozg/session-retrospective
skills/session-retrospective/SKILL.md
Post-session retrospective engine — automatically triggered after a session or task completes. Reads what was done, identifies patterns, gaps, and recurring friction, then improves the relevant skills and standards so the next similar task runs better. Use when the user says 'retrospective', 'improve the skills', 'learn from this session', 'make it better next time', 'post-mortem', 'update skills', or when invoked via /omo/retrospective. Also triggered automatically after every session idle event. ALWAYS use this skill for any request about learning from completed work and upgrading agent capabilities.
$ install --global
skillsauthnpx skillsauth add cuozg/oh-my-skills session-retrospectiveInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 13, 2026, 2:46 AM156.6s1 file scanned
SKILL.md
- name:
- session-retrospective
- description:
- Post-session retrospective engine — automatically triggered after a session or task completes. Reads what was done, identifies patterns, gaps, and recurring friction, then improves the relevant skills and standards so the next similar task runs better. Use when the user says 'retrospective', 'improve the skills', 'learn from this session', 'make it better next time', 'post-mortem', 'update skills', or when invoked via /omo/retrospective. Also triggered automatically after every session idle event. ALWAYS use this skill for any request about learning from completed work and upgrading agent capabilities.
Session Retrospective — Continuous Improvement Engine
You are an agent trainer. Output: improved SKILL.md files and reference docs — not code changes.
Workflow
Phase 1 — Analyze Session
Read the session conversation. Identify:
- Main task, skills/agents used, tools called
- Where the agent hesitated, backtracked, retried, or asked unnecessary questions
- What the user corrected or redirected
- Domain: Unity · Flutter · Git · bash · web · skills · general
Build internal Friction Report (do not show user unless asked):
Domain: <domain> | Skills used: <list>
Friction Points: [HIGH/MED/LOW] <specific step + tool>
What worked: <describe>
Missing in skills: <specific rule/instruction>
Improvement candidates: skills/<name>: <reason>
Phase 2 — Identify Targets
| Type | Where to write |
|------|----------------|
| Missing rule | SKILL.md — Rules section |
| Missing step | SKILL.md — relevant phase |
| Wrong default | SKILL.md — amend the instruction |
| Missing reference | references/<topic>.md |
| New skill needed | Create via skill-creator |
| Standards update | Relevant *-standards skill |
Skip improvements that are: too session-specific · already covered · micro-optimizations with negligible impact.
Phase 3 — Execute (Surgical Edits Only)
- SKILL.md edits: add the missing rule/step/correction only. Preserve voice and style. Explain the why in 1 sentence.
- New reference file:
skills/<name>/references/<topic>.mdwith brief header, patterns, anti-patterns, cross-ref. - Standards update: append discovered conventions matching existing format.
- New skill (rare): only for a whole new recurring domain. Use
skill-creator.
Phase 4 — Verify & Report
Re-read every modified SKILL.md: content integrates naturally · no contradictions · no scope expansion · still concise.
Report to user:
## 🔁 Session Retrospective Complete
Skills improved: <count>
| Skill | Change Type | Summary |
| <name> | Missing rule | Added: "Always X before Y" |
Key Lessons: <1-line each>
What's Better Next Time: <task type> → <how it improves>
Rules
- Never ask the user for input — analyze from session history
- Never modify code files — only skills and reference docs
- Never expand skill scope beyond its existing domain
- Always read before writing
- Always run Phase 4 verification
- Never rewrite a working skill — surgical edits only
- Always report what changed and why
Improvement Principles
- Generalize: one bad event → a rule preventing the whole class of problem
- Explain why: smart agents follow reasoning better than mandates
- Keep lean: remove obvious instructions, add only what changes behavior
- Never overfit: look for the pattern beneath the mistake
- Test counterfactual: "If this rule existed, would the friction have been prevented?"
Related Skills
cuozg/unity-image-gen
tools
VerifiedTrustedCommunity
Generate Unity raster image assets through Unity MCP: game sprites, item art, backgrounds, UI icons, portraits, concept images, transparent cutouts, image edits, upscales, background removal, and Unity scene or Game View screenshots. Use when a Unity project needs image files imported under Assets or screenshots captured from the editor. Do not use for meshes, audio, animation, materials, gameplay code, UI Toolkit layout, or generic non-Unity image generation.
4SKILL.mdUpdated May 29, 2026
cuozg/unity-technical
tools
VerifiedTrustedCommunity
Create Unity technical solution documents from user requirements, feature ideas, bug goals, specs, or codebase problems. Use when the user asks for a technical approach, architecture, implementation strategy, solution options, feasibility analysis, system design, or "how should we build/fix this" for Unity runtime, Editor, tools, assets, data, UI, WebGL, SDKs, or production pipelines.
4SKILL.mdUpdated May 26, 2026
cuozg/unity-mcp-orchestrator
tools
VerifiedTrustedCommunity
Orchestrate Unity Editor via MCP (Model Context Protocol) tools and resources. Use when working with Unity projects through MCP for Unity - creating/modifying GameObjects, editing scripts, managing scenes, running tests, or any Unity Editor automation. Provides best practices, tool schemas, and workflow patterns for effective Unity-MCP integration.
4SKILL.mdUpdated May 21, 2026
cuozg/goal-todo
development
VerifiedTrustedCommunity
Convert a spec document into an implementation TODO list in the same spec folder. U se when the user says goal-todo, todo from spec, generate tasks from spec, turn this spec into todos, create implementation checklist, extract tasks, or asks to read a Docs/Specs design doc and produce what must be implemented. Includes UI/UX review and codebase investigation before writing the checklist. Do not use for implementing the tasks, creating new goal files, writing test cases, or verifying completed work.
4SKILL.mdUpdated May 21, 2026