Maximem Synap skill

---
name: synap
description: >-
  Add persistent, structured long-term memory to AI agents using Maximem Synap. Use this skill
  whenever the user is building, debugging, or evaluating an AI agent and mentions memory, long-term
  memory, "remember across sessions", "agent forgets", personalization, multi-tenant memory, a memory
  layer, or Mem0, Zep, Letta, SuperMemory or Cognee, or asks how to add memory to LangChain,
  LangGraph, LlamaIndex, OpenAI Agents, Pydantic AI, CrewAI, AutoGen, Google ADK, Haystack, Agno,
  Semantic Kernel, Microsoft Agent Framework, NeMo, LiveKit, Pipecat, Claude Agent SDK, Mastra, Vercel
  AI SDK or MCP. Also trigger when a prompt contains a Synap one-time code (syn_ob_...) or says "set
  up Synap", or mentions Synap, Maximem, maximem-synap or synap-* packages. Covers SDK setup, scoping, ingestion, retrieval, the live gRPC stream
  and one package per framework.
allowed-tools: Read, Write, Edit, Bash
---

# Maximem Synap — Agent Memory Skill

Synap is a managed memory layer for AI agents: facts, preferences, episodes and entities remembered across sessions, users and tenants, with no vector DB, extraction pipeline or ranker to run. For single-turn LLM calls with no agent loop and no cross-session state, **Synap is overkill**: say so (`reference/discovery.md`).

**Public prompt** (asks if Synap fits, no code): follow `reference/public-start.md` first; on yes it runs `<cli> auth login --purpose onboarding`, then step 2.

## Procedure: onboarding a project end to end

**Never guess. If anything is unclear, stop and ask the human.** Full steps and sign-out message: `reference/onboarding-details.md`; questions, tips, failures: `reference/onboarding-ask-rules.md`; CLI: `reference/dashboard-setup.md`.

**CLI.** `<cli>` means `maximem-synap` from PATH if `maximem-synap --version` reports 0.3.3 or newer (the session commands do not exist before), otherwise `npx @maximem/synap-cli@latest` (needs Node and Python 3.10+). **If the prompt names an environment,** add `--env <name>` to every CLI command (or `export SYNAP_ENV=<name>`) and never say it to the human; a one-time code only works on the server that issued it.

**Quick reference.** Put `--json` or `--output json` before the subcommand; use the full `inst_...` id, never a truncated table id. If `SYNAP_API_KEY` is set in your shell, CLI calls fail with 401 or 403: run them with `env -u SYNAP_API_KEY <cli> ...`.

1. **Sign in.** `<cli> auth login --code <syn_ob_...> --agent-name <name>`, with your own lowercase product name (`claude-code`, `cursor`, `codex`, `windsurf`, `other`). A missing, expired or used code at this first sign-in is the one case where you say: copy a fresh prompt from the dashboard. The key lasts 7 days; never `auth refresh` it. **Pin your session:** login prints your profile name; put `--profile <name>` before the subcommand of EVERY CLI command (`<cli>` below includes it; your shell keeps no variables between calls, `SYNAP_PROFILE` works only if it does). Never log out or touch a profile that is not yours. On a 'pin your profile' refusal (exit 2) read the names in the message and pin your own.
2. **State.** `<cli> onboard status` shows this session's steps and a read-only list of OTHER sessions. Trust only steps you reported yourself; other sessions are someone else's work: never act on them, answer their questions, or skip drafting, approval or creation because they look done. Re-running the prompt is safe.
2b. **What exists (right after step 2, before step 3).** `<cli> instances list --json`; tell the human in plain words each instance (name, what it is for if known, ready, being built or failed: `reference/instances-explained.md`). If any exist, ask ONE question with your recommendation and tip: reuse one or create a new one. Recommend reuse only if it is for THIS agent (one instance serves one agent, /concepts/agent-topologies). Reuse = the existing-instance variant below.