neotoma

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.

Begin a Neotoma working session — open a conversation and record the opening interaction.

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.

Pull everything the agent needs to know about a topic (person, company, project, decision) before doing the work. Resolves the target, fetches the entity snapshot, the observation history, linked tasks, recent communication, and walks one hop of the relationship graph. Synthesizes a brief rather than dumping data.

Open every work session with a deterministic context pull. Verifies the state layer is reachable, surfaces today's calendar, scans recent inbound (email and DMs), lists open tasks, pre-resolves entity context for anyone on today's schedule, and reports a strategic snapshot before waiting for direction.

Prepare a GitHub + npm + sandbox release with preview. Covers preflight, changelog preview, RC branch + PR for public review, version bump, tag, GitHub Release creation, npm publish, and sandbox.neotoma.io deployment.

Process PRs

audit

Code review skill for PRs, branches, or uncommitted changes. Loads the appropriate subset of architecture/subsystem docs based on what changed, walks the change_guardrails_rules pre-PR checklist, and emits structured findings (blocking / advisory / nit) with a verdict.

Install Neotoma, configure MCP for your harness, and verify connectivity. Prerequisite for all memory skills.

File, maintain, and close security advisories. Keeps docs/security/advisories/, docs/security/practices.md, and GitHub Security Advisories (GHSA) in sync. Two modes — new (file advisory) and close (mark fixed).

Audit a Neotoma database for graph-health issues (duplicate or redundant entity types, misused types, excessive raw_fragments, non-humanreadable canonical names, orphans, cycles, schema drift). Runs deterministic checks first; LLM-assisted checks are opt-in. Detection separate from repair — emits structured remediation hints pointing at existing tools (merge_entities, correct, register_schema, split_entity, delete_entity).

Release

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.

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.

Open a high-quality pull request with a standardized description (Problems / Solutions / UX improvements / Documentation / Test plan / Breaking changes), the change_guardrails_rules.md pre-PR checklist enforced, and thorough functional-change documentation under docs/ surfaced via the docs server and docs site. Use this whenever a PR is about to be opened — directly via /create_pr or as a sub-step of /process_issues, /process_prs, /release, /fix_feature_bug.

Analyze Project

commit

Create New Plan

Create Prototype

Create New Release

Create Rule

Debug Command

Blog Post Visual Style (Cross-Repo)

Final Review

Fix Feature Bug

Manage Error Debugging Automation

publish-plan

publish

pull

push

Report Error Command

Report Error Command

Run Feature Workflow

Setup Commands (Legacy)

Setup Foundation Cursor Copies