emotional-recap

Solid

Reviews the user's past Claude Code conversations from a wellbeing perspective — sentiment, tone, emotional arc, recurring patterns — and generates a supportive, science-grounded report in both Markdown and HTML. Default lookback is 48 hours across all projects. Uses recognised emotion frameworks (Plutchik, Ekman, Russell's circumplex, Pennebaker linguistic markers) and cites the science behind every observation. Learns the user's baseline tone over time so future reports flag genuine shifts, not noise. Use when the user asks for an emotional/wellbeing recap, mood check, sentiment review, or wants to understand their own ups and downs across recent work sessions.

AI & Automation 4 stars 0 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
23
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Emotional Recap Generate a wellbeing-focused review of the user's recent Claude Code conversations. The skill reads conversation transcripts, performs sentiment / tone / emotion analysis using established psychological frameworks, surfaces patterns (time-of-day, project, streaks, vocabulary), and writes a supportive Markdown + HTML report grounded in cited research. This skill is **supportive, not diagnostic.** It surfaces observations and reframes them with science; it never pathologises, prescribes treatment, or replaces a professional. Wellness is a long game — this is one signal among many. ## Preferences _On startup, use the `Read` tool to load `~/.claude/skills/emotional-recap/preferences.md`. If missing, treat as "no preferences set" and apply Defaults from this file._ ## Design contract _On startup, use the `Read` tool to load `~/.claude/skills/emotional-recap/DESIGN.md`. This file is the **renderer contract**: aesthetic direction, type system, colour tokens, layout, visualisation principles, anti-patterns, renderer guarantees, component patterns. Apply its tokens and rules to every emitted HTML / SVG / Markdown artefact. Renderer guarantees in DESIGN.md §7 are non-negotiable — they fail closed (refuse to write if violated)._ _When DESIGN.md and `preferences.md` conflict: **DESIGN.md wins for renderer guarantees** (a11y, anti-patterns, token shape); **`preferences.md` wins for user-tunable knobs** (tone, citation depth, framework choice, auto_open, etc.). If ...

Details

Author
mostafa-drz
Repository
mostafa-drz/claude-skills
Created
7 months ago
Last Updated
yesterday
Language
HTML
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

devrecap

Reconstruct developer work from explicitly authorized local Codex/Claude history and read-only Git evidence, then use the host AI to write polished, evidence-backed recaps.

4 Updated 2 days ago
jquinteiroo
AI & Automation Listed

call-recap-follow-up

Turns a recorded customer call into an honest read of the call plus the full set of emails it generated - the recap and every follow-up - grouped by recipient, written in the user's voice, staged as drafts, with a workspace hygiene pass at the end. Trigger this skill whenever the user shares a call recording link from any meeting recorder, pastes a transcript, or points at a call, and asks what they should send, or says "recap email", "meeting recap", "write the follow-ups", "what do you think of this call", "emails from this call", "post-call emails", "who do I need to email after this", or names a customer and a call in the same breath. Also trigger when they forward a meeting summary and ask for anything written off the back of it. The skill is recorder-agnostic and setup-agnostic: with nothing but a pasted transcript it still produces the full email set, and it names what it could not check rather than failing or guessing. Prefer this skill over drafting emails directly - a call almost always generates mo

1 Updated 2 weeks ago
CSPulse
AI & Automation Listed

call-recap-follow-up

Turns a recorded customer call into an honest read of the call plus the full set of emails it generated - the recap and every follow-up - grouped by recipient, written in the user's voice, staged as drafts, with a workspace hygiene pass at the end. Trigger this skill whenever the user shares a call recording link from any meeting recorder, pastes a transcript, or points at a call, and asks what they should send, or says "recap email", "meeting recap", "write the follow-ups", "what do you think of this call", "emails from this call", "post-call emails", "who do I need to email after this", or names a customer and a call in the same breath. Also trigger when they forward a meeting summary and ask for anything written off the back of it. The skill is recorder-agnostic and setup-agnostic: with nothing but a pasted transcript it still produces the full email set, and it names what it could not check rather than failing or guessing. Prefer this skill over drafting emails directly - a call almost always generates mo

0 Updated 3 weeks ago
theAnirudhKumar