How do I install the Session Self Analysis skill?

Run npx skillmds@latest add zrozoom/session-self-analysis 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 Session Self Analysis safe to use?

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

Which AI agents work with Session Self Analysis?

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 Session Self Analysis free to use?

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

Who published Session Self Analysis?

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

Session Self Analysis by zrozoom — Agent Skill

Name: Session Self Analysis
Author: ZroZoom

Session Self Analysis

Agent session self-analysis workflow. Use at the end of a session or after user feedback to identify process failures, perform 5 Whys, and record durable learnings without duplicates. Trigger when: /self-analysis, self analysis, session retrospective, session learnings.

ZroZoom cb3ceb0 2.8 KB Updated Sep 17, 2026

File contents

Session Self-Analysis Skill

Analyze the current agent session and record durable lessons when needed.

Contract

Input: current session context and optional user feedback.
Output: concise self-analysis and any memory/skill updates.
Side effects: may edit .claude/memory/, a project session-learnings file (if one exists), or a relevant .agent/skills/*/SKILL.md after deduplication.

Workflow

1. Review Signals

Look for:

user had to clarify the request
user asked for format/style changes
factual correction was needed
repeated instructions were missed
CI/review bots caught issues from this session
repo rules were missed or applied late

If no friction occurred, say so briefly and stop.

2. Categorize

Use:

Format: structure, length, style
Substance: factual error or missed repo pattern
Tone: too formal/casual or wrong language
Logic: flawed reasoning or missed instruction
Process: wrong tool order, missing pre-flight, bad Git/PR flow

3. 5 Whys

For the most important issue, ask why until the root cause is specific and actionable. Three to five steps are enough.

4. Formulate Rule

Good rule format:

[Trigger/context] -> [Expected behavior]

Rules must be concrete and testable. Avoid vague rules like "be more careful".

5. Deduplicate Before Writing

Search:

ls .claude/memory
rg -n "keyword|concept" .claude/memory .agent/skills

Destination:

Type	Destination
process/workflow feedback	`.claude/memory/feedback_*.md`
code-level gotcha	project session-learnings file (if maintained)
domain-specific rule	relevant `.agent/skills/*/SKILL.md`

If an existing file covers the concept, update it rather than creating a duplicate.

6. Memory File Format

---
name: short-rule-name
description: One-line description
type: feedback
---

Rule statement.

**Why:** Incident that caused this rule.

**How to apply:** Trigger and concrete behavior.

After creating a memory file, add a one-line pointer to .claude/memory/MEMORY.md (or the equivalent index in your project).

Rules

Use bullet points, not numbered lists, inside memory files.
Do not create root-level docs.
Do not record generic preferences that are already covered by the repo's AGENTS.md / CLAUDE.md.
Memory recorded in .claude/memory/ is the repo SSOT shared across Claude / Codex / Copilot sessions. Per-machine user memory (~/.claude/projects/.../memory/ for Claude Code) is invisible to other agents — only sync rules worth sharing.

---name: session-self-analysisdescription: Agent session self-analysis workflow. Use at the end of a session or after user feedback to identify process failures, perform 5 Whys, and record durable learnings without duplicates. Trigger when: /self-analysis, self analysis, session retrospective, session learnings.---# Session Self-Analysis SkillAnalyze the current agent session and record durable lessons when needed.## Contract- Input: current session context and optional user feedback.- Output: concise self-analysis and any memory/skill updates.- Side effects: may edit `.claude/memory/`, a project session-learnings file (if one exists), or a relevant `.agent/skills/*/SKILL.md` after deduplication.## Workflow### 1. Review SignalsLook for:- user had to clarify the request- user asked for format/style changes- factual correction was needed- repeated instructions were missed- CI/review bots caught issues from this session- repo rules were missed or applied lateIf no friction occurred, say so briefly and stop.### 2. CategorizeUse:- Format: structure, length, style- Substance: factual error or missed repo pattern- Tone: too formal/casual or wrong language- Logic: flawed reasoning or missed instruction- Process: wrong tool order, missing pre-flight, bad Git/PR flow### 3. 5 WhysFor the most important issue, ask why until the root cause is specific andactionable. Three to five steps are enough.### 4. Formulate RuleGood rule format:```text[Trigger/context] -> [Expected behavior]```Rules must be concrete and testable. Avoid vague rules like "be morecareful".### 5. Deduplicate Before WritingSearch:```bashls .claude/memoryrg -n "keyword|concept" .claude/memory .agent/skills```Destination:| Type | Destination ||---|---|| process/workflow feedback | `.claude/memory/feedback_*.md` || code-level gotcha | project session-learnings file (if maintained) || domain-specific rule | relevant `.agent/skills/*/SKILL.md` |If an existing file covers the concept, update it rather than creating aduplicate.### 6. Memory File Format```markdown---name: short-rule-namedescription: One-line descriptiontype: feedback---Rule statement.**Why:** Incident that caused this rule.**How to apply:** Trigger and concrete behavior.```After creating a memory file, add a one-line pointer to`.claude/memory/MEMORY.md` (or the equivalent index in your project).## Rules- Use bullet points, not numbered lists, inside memory files.- Do not create root-level docs.- Do not record generic preferences that are already covered by the repo's `AGENTS.md` / `CLAUDE.md`.- Memory recorded in `.claude/memory/` is the **repo SSOT** shared across Claude / Codex / Copilot sessions. Per-machine user memory (`~/.claude/projects/.../memory/` for Claude Code) is invisible to other agents — only sync rules worth sharing.

Frequently asked questions