Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

memoria-recovery

Estrelas408

Forks53

Atualizado19 de março de 2026 às 00:37

Recover from accidental memory loss with snapshots and rollback. Triggers: "restore memory", "rollback memory", "undo deleted memory", "recover deleted memory", "take a memory snapshot".

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

matrixorigin

matrixorigin/Memoria

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Outras ocupações de informáticaInformática e Matemática·SOC 15-1299

SKILL.md

readonly

name	memoria-recovery
description	Recover from accidental memory loss with snapshots and rollback. Triggers: "restore memory", "rollback memory", "undo deleted memory", "recover deleted memory", "take a memory snapshot".

Memoria Recovery

Use Memoria snapshot tools when memory state needs a checkpoint or a rollback.

Before risky changes

If you are about to bulk-delete, purge, or rewrite memory, create a snapshot first with memory_snapshot.
Tell the user a checkpoint exists and can be restored.

After accidental deletion or corruption

Inspect available recovery points with memory_snapshots.
Choose the most recent good snapshot.
Restore with memory_rollback.
Verify recovery with memory_recall, memory_list, or memory_stats.

Rules

Prefer rollback over manually re-creating many deleted memories.
If the user wants a selective logical fix rather than full restore, use memory_correct or memory_forget instead.
After rollback, state what was restored and what you verified.

Mais deste repositório

mesmo repositório

thememoria

matrixorigin/Memoria

Use Memoria as OpenClaw's durable memory slot. Triggers: "remember this", "save to memory", "what do you remember", "continue from last time", "forget this", "correct memory", "take a snapshot", "rollback memory", "branch memory", "merge memory", "use long-term memory".

2026-04-21408

setup

matrixorigin/Memoria

Install Memoria and configure MCP for AI tools (Kiro, Cursor, Claude Code, Codex, Gemini CLI). Decision tree for Cloud vs self-hosted mode, database, embedding provider. Use when helping users set up Memoria.

2026-03-25408

deployment

matrixorigin/Memoria

Deploy Memoria with Docker Compose or Kubernetes. Environment variables, multi-instance setup, security. Use when deploying or configuring Memoria.

2026-03-23408

api-reference

matrixorigin/Memoria

Memoria REST API endpoints, request/response formats, auth, rate limits. Use when calling or implementing API endpoints.

2026-03-20408

architecture

matrixorigin/Memoria

Memoria codebase structure, workspace layout, key traits, database tables, config patterns, and testing conventions. Use when navigating or modifying Memoria code.

2026-03-20408

memoria-memory

matrixorigin/Memoria

Use Memoria for durable user/project memory in OpenClaw. Triggers: "remember this", "save to memory", "what do you remember", "forget this", "correct memory", "update memory", "use memoria".

2026-03-19408

name	memoria-recovery
description	Recover from accidental memory loss with snapshots and rollback. Triggers: "restore memory", "rollback memory", "undo deleted memory", "recover deleted memory", "take a memory snapshot".

Memoria Recovery

Use Memoria snapshot tools when memory state needs a checkpoint or a rollback.

Before risky changes

If you are about to bulk-delete, purge, or rewrite memory, create a snapshot first with memory_snapshot.
Tell the user a checkpoint exists and can be restored.

After accidental deletion or corruption

Inspect available recovery points with memory_snapshots.
Choose the most recent good snapshot.
Restore with memory_rollback.
Verify recovery with memory_recall, memory_list, or memory_stats.

Rules

Prefer rollback over manually re-creating many deleted memories.
If the user wants a selective logical fix rather than full restore, use memory_correct or memory_forget instead.
After rollback, state what was restored and what you verified.