Menu
Begin a Neotoma working session — open a conversation and record the opening interaction.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | start-session |
| description | Begin a Neotoma working session — open a conversation and record the opening interaction. |
| source | neotoma_bundle:core_workflows |
| requires_entity_types | ["interaction","conversation"] |
| triggers | ["start session","begin session","open conversation"] |
Opens a Neotoma working session at the top of a turn:
conversation entity for this thread.interaction capturing the user's first message.Ships from the core_workflows bundle (default install). See
docs/foundation/bundles.md.
Canonical turn protocol for agents writing to Neotoma. Bounded retrieval on the user message, store user message PART_OF conversation with REFERS_TO edges to retrieved entities, store assistant reply the same way. Use this skill in any agent loop that should persist conversation state to Neotoma.
Session-end audit. Files remaining work as task entities and lists them as bullets, verifies all data intended for Neotoma storage from this session is actually stored, and persists what's missing. Invoke at the natural close of a working session, before context is lost.
Mid-session status report. Summarizes what's been achieved so far this session and what work remains, in succinct qualitative prose and bullets with only light technical detail. Read-only — stores nothing, files nothing. Invoke any time to take stock without closing the session.
Close a Neotoma working session — store the assistant reply and a session-close summary.
Retrieve the bounded context for the current session — recent interactions and relevant entities.
Archive the working session at the end. Writes a session_close record to the state layer, logs every outbound interaction as a first-class row, writes task entities for follow-ups, and writes a project-level task ledger as a human-readable safety net. Run at the end of every working session to ensure nothing is lost.