Ensure Neotoma
Install Neotoma, configure MCP for your harness, and verify connectivity. Prerequisite for all memory skills.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Ensure Neotoma when an AI agent needs a reusable SKILL.md workflow for this job: Install Neotoma, configure MCP for your harness, and verify connectivity. Prerequisite for all memory skills.
When not to use it
Skip Ensure Neotoma when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/ensure-neotoma # Save SKILL.md to ~/.claude/skills/ensure-neotoma/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/ensure-neotoma/SKILL.md. For a shared project, commit the folder at .claude/skills/ensure-neotoma/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Ensure Neotoma skill for this task: Before running any remember- skill for the first time. Confirm any required inputs or files before making changes.
What supports this recommendation?
78/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 81/100
- Practical detail
- 92/100
- Source evidence
- 56/100
- Source signals
- 72/100
Model compatibility evidence
- claudeinferred
The skill text mentions Claude or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Ensure Neotoma
Meta skill that installs and configures Neotoma so other memory skills can run. Every `remember-*` skill references this as a prerequisite.
## When to use
- Before running any `remember-*` skill for the first time. - When the user says "install neotoma", "set up memory", or similar. - When another skill fails because Neotoma MCP is not connected.
## Workflow
### Phase 1: Check if Neotoma CLI is available
```bash npx neotoma status --output json ```
If `neotoma` is not found or `status` reports `installed: false`:
1. Guide installation: ```bash npm install -g neotoma ``` 2. Verify the install succeeded: ```bash neotoma --version ```
### Phase 2: Run setup
Run the composite setup command to configure MCP, CLI instructions, hooks, permissions, and skills for the current harness:
```bash neotoma setup --yes ```
If the user wants to target a specific harness, pass `--tool`:
```bash 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.
### Phase 3: Verify MCP connectivity
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.
### Phase 4: Confirm readiness
Report the result: - Neotoma version installed - Harness detected and configured - MCP connectivity status - Attribution tier
State that the user can now run any `remember-*` skill, and that ordinary storage and retrieval (store, query, recall) work directly through the live MCP tool instructions without loading a separate skill.
## Do not
- 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.
Intended uses
- Before running any remember- skill for the first time.
- When the user says "install neotoma", "set up memory", or similar.
- When another skill fails because Neotoma MCP is not connected.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.