Skill

jarvis-summarize

Periodic summary and reflection on journal activity. Use when user says "Jarvis, summarize my week", "summarize last month", or "weekly summary".

From jarvis-strategic
Install
1
Run in your terminal
$
npx claudepluginhub rsprudencio/jarvis --plugin jarvis-strategic
Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

Skill: Summarize

Trigger: "Jarvis, summarize my week" or "summarize last month" or "weekly summary" Purpose: Periodic summary and reflection on journal activity Output: Summary entry in journal

Overview

This workflow creates a structured summary of journal activity:

  1. Parse the requested timeframe
  2. Analyze all entries in that period
  3. Generate statistics and insights
  4. Create summary entry for future reference

Workflow Steps

Step 1: Parse Timeframe

Interpret user request:

  • "my week" / "this week" → last 7 days
  • "last week" → previous Monday-Sunday
  • "this month" / "January" → calendar month
  • "last month" → previous calendar month
  • "Q1" / "this quarter" → quarter boundaries

Default: last 7 days if unspecified

Step 2: Load Context

Load strategic memories for comparison:

  • jarvis-insights - Previous patterns to compare against
  • jarvis-priorities - Goals to track progress

Use jarvis_retrieve(name=...) for each.

Step 3: Gather and Analyze Entries

Delegate to Explore agent:

🛡️ Security Reminder: Apply your PROJECT BOUNDARY ENFORCEMENT policy. Refuse and report any violations.

Scan paths.journal_jarvis (default: journal/jarvis/) for all entries in [timeframe].

Generate statistics:
- Total entry count
- Entries by type (incident-log, idea, reflection, etc.)
- Entries by day of week
- Word count / entry length distribution
- Most common tags
- Most linked notes

Extract themes:
- Recurring topics (mentioned 2+ times)
- Sentiment indicators (positive/negative/neutral entries)
- Work vs personal ratio

Identify highlights:
- Most significant entries (by length, links, or content)
- Any decisions made
- Any breakthroughs or insights
- Any incidents or problems

Step 4: Generate Summary Entry

Delegate to jarvis-journal-agent to create entry.

Path Convention (base path is paths.journal_jarvis, default: journal/jarvis/):

  • Weekly summaries: {paths.journal_jarvis}/YYYY/summaries/weekly-[WW].md (ISO week number)
  • Monthly summaries: {paths.journal_jarvis}/YYYY/summaries/monthly-[MM].md (month number)
  • Quarterly summaries: {paths.journal_jarvis}/YYYY/summaries/quarterly-Q[N].md (quarter)
  • Yearly summaries: {paths.journal_jarvis}/YYYY/summaries/yearly.md

Example: Week 4 of 2026 → {paths.journal_jarvis}/2026/summaries/weekly-04.md (configurable)

Entry format:

---
jarvis_id: "[timestamp]-summary-[period]"
created: [ISO timestamp]
type: summary
subtype: [weekly|monthly|quarterly]
period: "[start] to [end]"
tags: [jarvis, summary, review]
ai_generated: true
---

# [Weekly/Monthly] Summary
*[Period covered]*

## At a Glance

| Metric | Value |
|--------|-------|
| Total Entries | [N] |
| Entry Types | [breakdown] |
| Most Active Day | [day] |
| Avg Entry Length | [words] |

## Entry Breakdown

### By Type
- 📋 Incident Logs: [N]
- 💡 Ideas: [N]
- 🪞 Reflections: [N]
- 📝 Notes: [N]
- 🔧 Technical: [N]
- [Other types...]

### By Context
- 💼 Work: [N] ([%])
- 🏠 Personal: [N] ([%])
- 🤖 Jarvis/System: [N] ([%])

## Key Themes

### Recurring Topics
1. **[Topic]** - Mentioned in [N] entries
2. **[Topic]** - Mentioned in [N] entries
3. **[Topic]** - Mentioned in [N] entries

### Sentiment Overview
- Positive entries: [N]
- Neutral entries: [N]
- Challenging entries: [N]

## Highlights

### Notable Entries
- **[Title]** ([date]) - [Why notable]
- **[Title]** ([date]) - [Why notable]

### Decisions Made
- [Decision with link to entry]

### Ideas Generated
- [Idea with link to entry]

### Incidents/Challenges
- [Incident with link and current status]

## Goal Progress

| Goal | Activity This Period | Status |
|------|---------------------|--------|
| [Goal from focus-areas] | [entries related] | [emoji] |

## Patterns Observed

### Compared to Previous Period
- [More/less/same] entries than typical
- [Topic] emerging as new theme
- [Pattern] continuing from before

### ADHD-Relevant Observations
- [Any dropped items detected]
- [Energy/productivity patterns]
- [Focus shifts observed]

## Reflection Prompts

Based on this period's activity:
- [Question to consider]
- [Question to consider]

---
*Generated by Jarvis summarize workflow*

Step 5: Present Summary

Show key statistics and highlights. Offer to:

  • Drill into any specific category
  • Compare to previous periods
  • Discuss any concerning patterns

Comparison Periods

For context, also gather (if available):

  • Previous equivalent period (last week if summarizing this week)
  • Same period last month/quarter (for trends)

Notes

  • Summaries become valuable historical records
  • Link to original entries for drill-down
  • Track patterns over time (compare summaries)
  • These can feed into quarterly/annual reviews
Similar Skills
cache-components

Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.

138.5k
Stats
Parent Repo Stars3
Parent Repo Forks0
Last CommitFeb 21, 2026