Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From shared-memory
Manually trigger an activity summary for a scope. Use when you want to capture and store a summary of recent activity.
How this skill is triggered — by the user, by Claude, or both
Slash command
/shared-memory:summarizeThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill allows you to manually trigger an activity summary for any scope.
This skill allows you to manually trigger an activity summary for any scope.
When invoked with /summarize, you should:
Determine the scope - Ask the user or infer from context:
global - All activity across projectsproject:<name> - Activity specific to a projectTrigger the summary using trigger_summary:
tool: trigger_summary
scope: "project:brain-jar" // or "global"
Report the result - Show the user what was summarized:
User: /summarize
Response: "What scope would you like to summarize? I can summarize all activity (global) or a specific project."
User: /summarize project:brain-jar
Response: Immediately trigger summary for that scope and report results.
Summaries are also generated automatically when:
Use /summarize to force a summary at any time, regardless of these thresholds.
get_activity_summaries - View past summariesget_memory_timeline - See memories grouped by time periodnpx claudepluginhub designnotdrum/perplexity-search-plugin --plugin shared-memoryGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.