session-recap

Propagates session notes into recap files, hot.md updates, and situation file changes across a campaign wiki.

Updated May 29, 2026
One-click install
npx skills add https://github.com/Thedougler/shattered-sea-wiki --skill session-recap-thedougler
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-recap
Source: https://github.com/Thedougler/shattered-sea-wiki/tree/main/.claude/skills/session-recap
Command: npx skills add https://github.com/Thedougler/shattered-sea-wiki --skill session-recap-thedougler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a tabletop RPG session, updates are scattered across many files — session recaps, the current-state hot.md, situation trackers, faction clocks, and the CLAUDE.md party block — making it easy to miss one and let the campaign wiki drift out of sync. ## Core Features & Use Cases - Session Recap Generation: Writes a player-facing recap file with proper frontmatter, wikilinks, and optional scene art for major narrative beats. - World-State Cascade: Updates hot.md sections (current arc, open threads, faction clocks, live situations, predictions, spotlight tracking) plus situation files and the CLAUDE.md party block. - Entity Stub Creation: Creates stub pages for newly introduced NPCs, locations, and items, then commits all changes with a standardized message. - Use Case: After running session 4, paste your DM notes and ask the agent to process them — it produces the recap, refreshes every state-tracking file, and commits the result. ## Quick Start Process my session 4 notes from the Inbox and cascade all updates across the wiki.

Frequently Asked Questions about session-recap

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update my D&D campaign wiki after a session?▼

Provide raw session notes from the Inbox folder or paste them into the conversation, then invoke the recap workflow. It writes a player-facing recap, updates hot.md and situation files, refreshes the CLAUDE.md party block, and commits everything.

What inputs does the session recap workflow accept?▼

It accepts a notes file in the Inbox directory, pasted text of the DM's session notes, or a request like "process session 4" which locates the most recent unprocessed Inbox file. If no notes exist, it asks for them.

Does it work with Obsidian vaults and wikilinks?▼

Yes, the workflow is built for an Obsidian vault. It wikilinks every named entity on first mention in the recap and creates stub entity pages with proper frontmatter for new NPCs, locations, and items.

What files get changed during the post-session cascade?▼

It creates a session recap under wiki/sessions/, updates hot.md sections, modifies active situation files, moves resolved situations, updates the CLAUDE.md arc and faction table, and creates entity stubs before committing.

What happens if session notes are missing or incomplete?▼

If no notes are provided, the workflow stops and asks for them rather than guessing. It reads hot.md and the previous recap first to establish continuity and tone before writing anything.