Skill

jarvis-memory

Use at the end of a session or when Chadron says to save/update memory. Updates history, status, recommendations, and needs files based on what was accomplished.

npx claudepluginhub chadronbryant/napa-cowork-plugins --plugin jarvis

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Persist session work into the brain so the next session picks up where we left off.

SKILL.md

Similar Skills

cache-components

139.2k

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

canvas-design

124.2k

Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.

20 files

anthropics-skills-13

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 3, 2026

Actions

View Source View Plugin View on GitHub View README

Jarvis Memory Update

Persist session work into the brain so the next session picks up where we left off.

Process

Step 1: Load Current State (in parallel)

Read from workspace root (use CLAUDE.md canonical root on Mac; in Cowork use mounted workspace at the path shown in your environment):

memory/history/recent-activity.md - Current activity log
Jarvis/status.json - Current status
Jarvis/recommendations.md - Current priorities
Jarvis/needs.md - Current needs list

Step 2: Assess What Changed This Session

Review the current conversation and identify:

What tasks were completed?
Were any deliverables created or updated?
Did data freshness change (new pulls)?
Were any new needs or blockers identified?
Did priorities shift based on work done?
Any lessons learned or mistakes to capture?

Step 3: Update Files

Update each file that needs changes:

memory/history/recent-activity.md

Add today's date header if not present
Add bullet points for each accomplishment
Keep entries concise (one line per item)

Jarvis/status.json

Update last_updated timestamp
Update recent_sessions array (add new entry, keep last 5)
Update deliverables.completed if new deliverables were produced
Update instance data if refreshes occurred

Jarvis/recommendations.md

Move completed items to lower priority or remove
Add any new recommendations discovered during the session
Re-rank based on current state
Update the Last Updated date

Jarvis/needs.md

Add any new needs identified
Mark any needs that were fulfilled
Update the Last Updated date

Jarvis/MOTD.md

Update RECENT ACTIVITY section with today's work
Update DELIVERABLES PRODUCED if new ones were created

Step 4: Confirm

Present a summary of what was saved:

MEMORY UPDATED | [date]
─────────────────────────────────
History:         [X items logged]
Status:          [updated/no changes]
Recommendations: [X added, X completed, X reranked]
Needs:           [X added, X resolved]
MOTD:            [updated/no changes]
─────────────────────────────────
Brain is synced. Next session will pick up here.

Rules

Never delete history entries, only append
Keep recent-activity.md entries to one line each
Maintain the existing file formats exactly
If unsure whether something changed, ask Chadron