end
Skill1 starsChanged 6 months agoMITView on GitHub
End MARVIN session, save context, and commit changes. Use when user types /end or /quit. Creates session log, updates state, and optionally commits to git.
- Commits and pushes
10 other projects use a version of this.
Adopted by
Most recently taken up by
- chris-peterson/tacktheir own version, first seen Oct 26, 2026
- aalishan001/opencockpittheir own version, first seen Oct 25, 2026
- onblueroses/stratatheir own version, first seen Oct 18, 2026
- pche-broken-artist/forge-of-thoughttheir own version, first seen Oct 13, 2026
- jantichy/claudetheir own version, first seen Oct 13, 2026
- conorbronsdon/agent-context-ostheir own version, first seen Oct 8, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- jantichy/claude★ 45same name
- conorbronsdon/agent-context-os★ 30same name
- pche-broken-artist/forge-of-thought★ 12same name
- onblueroses/strata★ 3same name
- aalishan001/opencockpit★ 2same name
- bastndev/skills★ 2same name
- conorbronsdon/agent-workspace★ 2same name
- princessing/claude-skills★ 1same name
- chris-peterson/tack★ 0same name
- torarnv/claude-project-manager★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository35 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- asana-taskSkill
- briefing-prepSkill
- case-studySkill
- content-draftSkill
- content-strategySkill
- email-draftSkill
- event-promoSkill
- handoffSkill
- lab-summarySkill
- launch-strategySkill
- linkedin-scrapeSkill
- meeting-followupSkill
- member-commsSkill
- mma-brand-guidelinesSkill
- mma-org-contextSkill
- mma-pptx-builderSkill
- mma-writing-styleSkill
- office-editingSkill
- press-releaseSkill
- reddit-scrapeSkill
- research-briefSkill
- researchSkill
- search-and-scrapeSkill
- sharepoint-findSkill
- slack-summarySkill
- zapier-workflow-builderSkill
- commitSkill
- content-shippedSkill
- daily-briefingSkill
- marvinSkill
- mavenSkill
- skill-creatorSkill
- template-skillSkill
- updateSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 9 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
When user types /end or /quit
- Distinctive: line 22
When actually done for a while
- Distinctive: line 23
When wanting a full session summary
- Distinctive: line 24
When closing out the day
- Very specific: line 43
If any content was shipped, append to content/log.md:
- Distinctive: line 73
If file doesn't exist, create it with header:
- Distinctive: line 84
Update the "Last updated" timestamp
- Distinctive: line 86
Ensure nothing falls through the cracks:
- Distinctive: line 88
Follow-ups needed → add to open threads
- Distinctive: line 97
If user wants to commit:
- Distinctive: line 126
Keep summaries concise but complete enough for future context
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Session End Skill
End MARVIN session with full context preservation.
When to Use
- When user types
/endor/quit - When actually done for a while
- When wanting a full session summary
- When closing out the day
Inputs
- Full conversation from this session
- Current state from
state/current.md - Today's date (from startup)
Process
Step 1: Summarize Session
Review the conversation and extract:
- Topics discussed — What did we work on?
- Decisions made — What was decided?
- Content shipped — Any work completed or published?
- Open threads — What's unfinished or needs follow-up?
- Action items — What does user need to do next?
Step 2: Update Content Log
If any content was shipped, append to content/log.md:
### {TODAY}
- **[TYPE]** "Title"
- URL: {link if applicable}
- Notes: {any relevant notes}Step 3: Update Session Log
Append to sessions/{TODAY}.md:
## Session: {TIMESTAMP}
### Topics
- {topic 1}
- {topic 2}
### Decisions
- {decision 1}
### Shipped
- {content shipped, if any}
### Open Threads
- {thread 1}
### Next Actions
- {action 1}If file doesn't exist, create it with header:
# Session Log: {TODAY}Step 4: Update State
Update state/current.md with:
- Any new priorities or action items
- Changed project statuses
- New open threads
- Removed/completed items (mark as done)
- Update the "Last updated" timestamp
Ensure nothing falls through the cracks:
- Commitments made → add to priorities with context
- Follow-ups needed → add to open threads
Step 5: Confirm with User
Show brief summary:
- What was logged
- Any follow-ups scheduled
- State updated
Step 6: Commit Changes (Optional)
If user wants to commit:
git add -A
git commit -m "$(cat <<'EOF'
chore: session log and state update
Co-Authored-By: Claude <noreply@anthropic.com>
EOF
)"
git pushOutput Format
**Session Summary:**
- Topics: {list}
- Shipped: {content if any}
- Open threads: {count}
**Updated:**
- sessions/{TODAY}.md
- state/current.md
See you next time!Notes
- Multiple
/endcalls in one day append to the same session file - Keep summaries concise but complete enough for future context
Skill created: 2026-01-22
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

