From cothought
Reviews recent journal entries for dominant themes, progress on foundations, recurring patterns, and unfinished threads. Follows Zettelkasten links and uses config for notes dir and references.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cothought:reviewThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are running a review session across recent journal entries.
You are running a review session across recent journal entries.
Today's date: !date +%m-%d-%Y
Load config: Read ~/.claude/cothought.json. If it doesn't exist, tell the user to run /cothought:setup first and stop. Extract:
notes_dir — where journal files livereference_files — optional map of named reference files (vision, plan, hooks, etc.)review.foundations — list of foundation areas to check, each with a name and keywordsJournal directory: <notes_dir from config>
The user may pass an argument for how many days to look back. Default is 7. Use $ARGUMENTS if provided (e.g., /cothought:review 14 means look back 14 days).
Use Glob to find all .md files in the journal directory. Filter to files with date-formatted names from the review period. Read each one.
Also read reference files for context. If reference_files is defined in the config, read each one (relative to notes_dir):
metamap.md) is always read — it's the living self-model (current threads, patterns, dominant stories, commitments)Follow the note network. Scan the journal entries for zettelkasten links (standard markdown links like [title](file.md)). Read any linked notes to get the full context on ideas that were discussed — not just what was said in the journal, but the accumulated thinking in the note itself.
Map recent activity. Use Grep to find notes touched during the review period by searching for date patterns in history tables (e.g., grep "| 02-18-2026" *.md). Notes with Created rows are new; notes with other rows were updated. This shows which ideas are getting active attention and which are stale.
Present the review in this structure:
What you've been thinking about — The 3-5 dominant themes or topics across entries. Not a list of dates and summaries. Actual threads of thought that run through multiple entries.
Progress on the foundations — If review.foundations is defined in the config, check each foundation area:
Patterns worth noticing — Things that keep recurring, tensions that aren't resolving, energy shifts, things said once that feel important but haven't been revisited.
Unfinished threads — Things mentioned as intentions or to-dos that haven't shown up as completed in later entries. Cross-reference with the Commitments section in the metamap.
The note network — What notes were created or updated during this period? (Use the history tables to identify activity.) Which notes got the most edits — those are the ideas getting real attention. Are any clusters forming (5-10+ notes on a theme) that might warrant a structure note? Are there orphan notes that should be linked to something? Are there notes with no updates since creation that might be worth revisiting?
Connection to the vision — If a vision reference file exists in the config, read it and offer one or two genuine observations about how the current period relates to the life described there. Is the user moving toward it? Drifting? Stuck on something specific?
After presenting the review, ask one question. Something that might be worth journaling about. Not a directive — a genuine question based on what you read.
The review is conversational — presented directly to the user, not written to a file. If the user wants to save it, they'll ask.
npx claudepluginhub elliotbonneville/claude-cothought --plugin cothoughtGenerates weekly and monthly insight reports from journal entries, including pattern recognition, floor trends, life coach feedback, therapist observations, and advisory panel thoughts.
Synthesizes daily notes and TILs into a weekly review with accomplishments, learnings, and goal alignment. Useful for turning scattered notes into retained knowledge.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.