end
Skill38 starsChanged 2 months agoMITView on GitHub
Session-end audit. Surfaces remaining work to complete or track, verifies all data intended for Neotoma storage from this session is actually stored, and offers to file what's missing. Invoke at the natural close of a working session, before context is lost.
11 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
Used with
Projects with it also use update.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AnthropicSkillupdate
Sync tasks and refresh memory from your current activity. Use when pulling new assignments from your project tracker into TASKS.md, triaging stale or overdue tasks, filling memory gaps for unknown people or projects, or running a comprehensive scan to catch todos buried in chat and email.
Also in 3 projects that use this
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- jantichy/claude★ 52same name
- conorbronsdon/agent-context-os★ 30same name
- pche-broken-artist/forge-of-thought★ 14same name
- onblueroses/strata★ 3same name
- aalishan001/opencockpit★ 2same name
- bastndev/skills★ 2same name
- conorbronsdon/agent-workspace★ 2same name
- alectivism/maven-template★ 1same name
- princessing/claude-skills★ 1same name
- chris-peterson/tack★ 0same name
1 more not listed
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 repository101 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- .cursor/rules/autonomous_execution.mdcCursor rule
- .cursor/rules/cursor_rules_editing.mdcCursor rule
- .cursor/rules/cursor_rules_sync.mdcCursor rule
- .cursor/rules/cursor_rules_sync_requirement.mdcCursor rule
- site_pages/llms.txtllms.txt
- advisorySkill
- analyzeSkill
- auditSkill
- commitSkill
- create-planSkill
- create_planSkill
- create-prototypeSkill
- create_prototypeSkill
- create_prSkill
- create-releaseSkill
- create_releaseSkill
- create-ruleSkill
- create_ruleSkill
- debugSkill
- draft-illustrationSkill
- draft_illustrationSkill
- evaluate_positioningSkill
- final-reviewSkill
- final_reviewSkill
- fix-feature-bugSkill
- fix_feature_bugSkill
- learnSkill
- manage-error-debuggingSkill
- manage_error_debuggingSkill
- neversight_learn_skills.dev_obviously_awesomeSkill
- process_issuesSkill
- process_prsSkill
- publish-planSkill
- publish_planSkill
- publishSkill
- pullSkill
- pushSkill
- recover_sqlite_databaseSkill
- releaseSkill
- report-errorSkill
- report_errorSkill
- reportSkill
- reviewSkill
- run-feature-workflowSkill
- run_feature_workflowSkill
- setup-commandsSkill
- setup_commandsSkill
- setup-cursor-copiesSkill
- setup_cursor_copiesSkill
- store-neotomaSkill
- store_neotomaSkill
- sync-env-from-1passwordSkill
- sync_env_from_1passwordSkill
- analyzeSkill
- auditSkill
- commitSkill
- create-planSkill
- create-prototypeSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 3 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 56
If the conversation itself has not been persisted as a conversation + dual conversation_message shape end-to-end, invoke store-neotoma to …
- Very specific: line 57
Write any memory files per the auto-memory protocol and update MEMORY.md index.
- Very specific: line 58
If do-now items exist and the user requested execution, perform them inline.
- Distinctive: line 80
MUST NOT execute storage or task filing without user confirmation of the Phase 3 plan.
- Distinctive: line 81
MUST NOT skip the storage audit even if the user only asks about remaining work, and vice versa.
- Distinctive: line 82
MUST classify every surfaced item.
- Very specific: line 83
MUST check existing Neotoma state via retrieval before declaring an item "not stored."
- Very specific: line 84
MUST defer chat-transcript storage to store-neotoma, not re-implement it.
- Very specific: line 85
MUST strip PII from any filed issues per feedback_pii_in_issues memory.
“Common” is measured: kept by at least 6 in 10 of the 10 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
end
Purpose
Run a session-close audit so nothing intended for follow-up or for Neotoma storage falls through the cracks. Distinct from the primitive store MCP tool call (single per-record persistence) and /store-neotoma (full chat-transcript persistence): /end is the meta-step that decides which of those to invoke, and what remaining tasks need to be tracked.
Scope
Applies once per session, at user request. Does not modify code. Does file Neotoma entities (tasks, issues, plan updates) and may delegate to store-neotoma for chat persistence.
Phase 1: Remaining-work audit
Scan the current conversation and produce a structured list under these headings. List items only; do not write to disk yet.
- Open work — TODOs the assistant introduced, partial implementations, files modified but not verified, tests not run, lint/type-check skipped, PRs/commits not made.
- Decisions or proposals not acted on — recommendations the user accepted that have not been executed; designs sketched but not implemented.
- Trackable follow-ups — bugs noticed in passing, refactors deferred, documentation drift spotted, dependencies needing updates.
- External obligations — anything waiting on CI, a remote agent, a scheduled task, or a third party.
- User feedback or preferences expressed this session — candidates for memory (
feedback/user/project/reference).
For each item, classify: do-now (small enough to finish in this session), track (file as task/issue/plan entry), or drop (acknowledged, no action).
Phase 2: Neotoma storage audit
Determine what should be in Neotoma from this session and what already is.
- Per-turn lifecycle compliance — confirm each turn this session followed the Neotoma turn lifecycle (user message + assistant message stored, PART_OF + REFERS_TO edges). If any turn was skipped (which is forbidden), list it.
- Substantive entities surfaced — list every concrete entity discussed or produced this session: plans, decisions, skills, rules, bugs, contacts, transactions, events, code artifacts, etc. For each, check via
retrieve_entity_by_identifierorretrieve_entitieswhether it is already stored. - Files or attachments — any files the user pasted, screenshots, transcripts, or external URLs fetched. Check whether each has a corresponding
source_id/ content-addressed source row. - Memory-worthy facts — items that should be written to the auto-memory directory (
~/.claude/projects/.../memory/) per the auto-memory protocol.
Produce a table with columns: item, kind (entity / source / memory), stored? (yes/no/partial), action (store via the store MCP tool / store via store-neotoma / write memory file / skip).
Phase 3: Confirmation and execution
Present Phases 1 and 2 to the user as a single end-of-session report with two sections: "Remaining work" and "Storage gaps." End with:
- A concrete list of proposed actions (e.g., "file 3 tasks, store 2 entities, invoke /store-neotoma, write 1 memory file").
- Request confirmation, or accept revisions.
On confirmation:
- File
taskentities for eachtrackitem from Phase 1 via thestoreMCP tool with appropriate REFERS_TO edges to relevant entities. - Store missing entities or sources flagged in Phase 2 via the
storeMCP tool directly. - If the conversation itself has not been persisted as a
conversation+ dualconversation_messageshape end-to-end, invokestore-neotomato do the full transcript sweep. - Write any memory files per the auto-memory protocol and update
MEMORY.mdindex. - If
do-nowitems exist and the user requested execution, perform them inline; otherwise file them as tasks.
Phase 4: Final summary
Report:
- Remaining-work items filed (with task entity IDs).
- Entities/sources stored (with entity IDs).
- Memory files written.
- Anything dropped or deferred, with one-line reason.
- Whether
store-neotomawas invoked.
Render the mandatory 🧠 Neotoma turn report covering all entities created in Phases 3–4.
Relationship to other skills
store(MCP tool) — per-entity/per-file store primitive./endcalls it directly for each gap identified in Phase 2.store-neotoma— full chat-transcript persistence with preview/confirm./enddelegates to it when the conversation as a whole is not yet stored.- Redundancy note: the primitive
storeMCP tool andstore-neotomaare not redundant — directstorecalls are per-record and per-call;store-neotomais the bulk session-end transcript sweep with preview.
Constraints
- MUST NOT execute storage or task filing without user confirmation of the Phase 3 plan.
- MUST NOT skip the storage audit even if the user only asks about remaining work, and vice versa.
- MUST classify every surfaced item; no unclassified entries.
- MUST check existing Neotoma state via retrieval before declaring an item "not stored."
- MUST defer chat-transcript storage to
store-neotoma, not re-implement it. - MUST strip PII from any filed issues per
feedback_pii_in_issuesmemory.
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.

