Agent skill
update
Quick context checkpoint without ending session. Use when user types /update. Saves progress to session log and updates state if needed.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/update-sterlingchin-marvin-template
Metadata
Additional technical details for this skill
- model
- default
- proactive
- NO
- slash command
- /update
- user invocable
- YES
- marvin category
- session
SKILL.md
Update Skill
Lightweight save without ending the session. Use frequently to preserve context.
When to Use
- User types
/update - After finishing a chunk of work
- Before switching contexts
- Every hour or so during long sessions
- When context is running low
Process
Step 1: Identify What Changed
Quickly scan the recent conversation for:
- Topics worked on
- Decisions made
- Files created/modified
- Any state changes needed
Keep it brief. No full summary needed.
Step 2: Append to Session Log
Get today's date: date +%Y-%m-%d
Append to sessions/{TODAY}.md:
## Update: {TIME}
- {what was worked on, 1-3 bullets}
If file doesn't exist, create with header: # Session Log: {TODAY}
Step 3: Update State (if needed)
Only update state/current.md if something actually changed:
- New open thread
- Completed item
- Changed priority
- New project/task discovered
Skip if nothing material changed.
Step 4: Confirm (minimal)
One line: "Checkpointed: {brief description}"
No summary. No "next actions" list. Just confirm the save.
Output Format
Checkpointed: {2-5 word description of what was saved}
Notes
- This is intentionally lightweight
- Don't use for full session wrap-up (use
/endfor that) - Multiple updates per day append to the same session file
Skill created: 2026-01-22
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?