status
Report whether EverOS memory is working for Claude Code - server health, the identity used for capture and recall, effective configuration, and recent errors. Use when memory seems to be missing, when the user asks whether EverOS is on, or when setting the plugin up for the first time.
Datos de origen
- Repositorio
- EverMind-AI/Plugins
- Última actividad en el origen
- 16 de septiembre de 2026 a las 09:09
- Idioma detectado de SKILL.md
- inglés
- Estrellas
- 7
- Forks
- 6
Opciones de instalación
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Revisa los archivos de origen
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Mostrando SKILL.md
SKILL.md
Instrucciones de origen · Vista previa de solo lectura- name
- status
- description
- Report whether EverOS memory is working for Claude Code - server health, the identity used for capture and recall, effective configuration, and recent errors. Use when memory seems to be missing, when the user asks whether EverOS is on, or when setting the plugin up for the first time.
# EverOS status
Run the status script and show the user its output verbatim:
```bash
node "${CLAUDE_PLUGIN_ROOT}/scripts/status.js"
```
Then add one sentence of interpretation:
- Server reachable and `user_id` present: memory is working. Say so and stop.
- Server not reachable: the numbered checklist in the output is the fix. Point at the first step that is not satisfied rather than repeating the whole list.
- `user_id` MISSING: personal memory is off. Tell the user to set `EVEROS_CC_USER_ID`.
- `project_id` is not what the user expected: it comes from the `origin` remote name, then the git toplevel, then the directory name. `EVEROS_CC_PROJECT_ID` overrides it.
Do not guess at causes the script did not report, and do not offer to restart EverOS unless the user asks.
Ver en GitHub