Menú
Use when starting ReMe over HTTP or MCP, or when embedding ReMeApp directly into an application without changing memory-type semantics.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Use when an agent needs a file-first ReMe workspace as the source of durable setup facts, stable preferences, or reusable daily decision records.
Use when an agent needs a file-first ReMe workspace as the source of durable setup facts, stable preferences, or reusable daily decision records.
Use when you need vector-backed personal memory in ReMe, including preference extraction, personal-memory retrieval, or PersonalMemoryService and ReMeApp integration.
Use when integrating ReMeLight into an agent loop and you need file-based context checks, compaction, tool-result offload, semantic search, or session memory.
Use when you need ReMe to learn from prior task trajectories, extract reusable success or failure patterns, or retrieve procedural memory for similar tasks.
Use when many tools look similar and you need ReMe to learn historical tool quality, parameter patterns, or retrieval guidance for future tool selection.
| name | reme-service |
| description | Use when starting ReMe over HTTP or MCP, or when embedding ReMeApp directly into an application without changing memory-type semantics. |
Use this skill for ReMe service startup and application integration surfaces.
Use this skill when you need to:
ReMeApp directly through Python importDo not use this skill to decide personal/task/tool memory policy or file-first workspace rules.
backend=httpbackend=mcpfrom reme_ai import ReMeAppChoose one integration surface:
ReMeApp import when Python code should call ReMe in-processworkspace_id convention per integration