Openclaw-skills session-summary

Summarize the current session's key decisions, changes, findings, and next steps into a structured markdown note. Use at the end of a work session, after completing complex tasks, or when the conversation has been long. Triggers on "summarize session", "wrap up", "session notes", "what did we do", "save progress", "end of session".

install

source · Clone the upstream repo

git clone https://github.com/EasyJoy-Technologies/openclaw-skills

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/EasyJoy-Technologies/openclaw-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/session-summary" ~/.claude/skills/easyjoy-technologies-openclaw-skills-session-summary && rm -rf "$T"

OpenClaw · Install into ~/.openclaw/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/EasyJoy-Technologies/openclaw-skills "$T" && mkdir -p ~/.openclaw/skills && cp -r "$T/skills/session-summary" ~/.openclaw/skills/easyjoy-technologies-openclaw-skills-session-summary && rm -rf "$T"

manifest: skills/session-summary/SKILL.md

source content

Session Summary — Capture Session Progress

Analyze the current conversation and produce a structured summary.

Process

Step 1: Scan the Conversation

Review for:

Decisions made — architectural choices, tool selections, approach decisions
Changes applied — files modified, configs changed, services restarted
Problems solved — what was broken, root cause, fix
Open items — deferred work, unanswered questions, next steps
Facts learned — new environment/codebase/domain information
Rules established — new conventions, safety rules, policies

Step 2: Write the Summary

Write to

memory/YYYY-MM-DD.md

(today's date). If file exists, append with timestamp header.

## Session: HH:MM — Brief Topic

### Decisions
- Decision: rationale

### Changes
- `path/to/file`: what and why

### Issues
- Issue → resolution (or "OPEN")

### Key Facts
- Fact worth remembering

### Next Steps
- [ ] Action item

### Rules Established
- New rule: description (promote to MEMORY.md if durable)

Step 3: Promote Durable Facts

If any facts/rules will matter beyond today:

Check MEMORY.md for duplicates
Propose additions, wait for confirmation before writing

Rules

Bullet points, not paragraphs
Include file paths for changes
ISO dates (YYYY-MM-DD), 24h time
Omit empty sections
If session was trivial, say so instead of generating empty template