How do I install the Session Analyst skill?

Run npx skillmds@latest add kmshihab7878/session-analyst 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 Analyst 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 Analyst?

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 Analyst free to use?

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

Who published Session Analyst?

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

Session Analyst by kmshihab7878 — Agent Skill

Name: Session Analyst
Author: kmshihab7878

Session Analyst

Produce an end-of-session report: what happened, what worked, what friction recurred, and which candidate learnings emerged. Use when the user asks /evolution report or invokes this manually at session end. Writes to evolution/reports/, never to stable/.

kmshihab7878 32d49c0 1.6 KB Updated Sep 17, 2026

File contents

session-analyst

When to use

User runs /evolution report or asks "summarize this session."
Manually before compacting context or ending a session, if the session produced load-bearing evidence.

Protocol

Scan ~/.claude/evolution/records/*.jsonl for events with ts within the current session (use session id if known, otherwise last hour).
Group by type:
- corrections → list with summaries
- wins → list with summaries
- friction → group by similar summary token overlap
Identify candidate patterns: any friction or correction theme that already appears ≥ 2 times in prior session records.
Run bash ~/.claude/evolution/bin/evolve-collect.sh — this updates candidates/ based on fresh records.
Write a report to ~/.claude/evolution/reports/YYYY-MM-DD-session-<short-sid>.md with sections:
- Session summary (1 paragraph)
- Corrections observed
- Wins observed
- Candidate learnings updated / created
- Suggested next actions

Hard rules

Never write to ~/.claude/evolution/stable/ directly.
Never promote a candidate — that goes through the promotion gate.
Do not invent evidence. Only summarize what is in records/.

Output

A single markdown file in evolution/reports/. Show the user the path and a 3-line summary inline.

Frequently asked questions