Ensure Neotoma

SkillDocs & knowledge

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

Available today. Use it from your connected AI after setup.

No other account needed.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Ensure Neotoma skill

What this skill tells your AI

The instructions your AI receives, as published by markmhendrickson/neotoma in skills/ensure-neotoma/SKILL.md and read by ahel’s review.

Meta skill that installs and configures Neotoma so other memory skills can run. Every remember-* skill references this as a prerequisite.

npx neotoma status --output json

If neotoma is not found or status reports installed: false:

Run the composite setup command to configure MCP, CLI instructions, hooks, permissions, and skills for the current harness:

neotoma setup --yes

If the user wants to target a specific harness, pass --tool:

neotoma setup --tool cursor --yes
neotoma setup --tool claude-code --yes
neotoma setup --tool codex --yes

Review the setup report. Every step should show ok: true. If any step failed, report the failure reason and suggest remediation.

Use the Neotoma MCP get_session_identity tool to confirm the MCP connection is live:

If the tool is available and returns a response, Neotoma is configured.
Check attribution.tier — software or hardware means verified attribution; unverified_client is functional but unverified.
If the MCP tool is not available, check the harness MCP config file and guide the user through manual configuration.

Report the result:

State that the user can now run any remember-* skill or store-data / query-memory.

Skip verification — always confirm MCP connectivity before declaring success.
Assume the user has Node.js installed — check and guide if npm is not found.
Modify harness configuration files directly — use neotoma setup which handles all harness-specific logic.

Advanced