Files

1.6 KiB

name, description, license, metadata
name description license metadata
engram-cloud-sync Trigger: sync engram cloud, sincronizar memoria, push engram, engram cloud sync. Synchronize local Engram project to remote cloud server. Apache-2.0
author version
horacio 1.0

Activation Contract

Load this skill whenever the user explicitly asks to synchronize, push, or sync their Engram memory with the cloud.

Hard Rules

  • Never skip the sync when requested. Execute engram sync --cloud --project turnosxpress every time.
  • Always verify the cloud server is reachable and the project is enrolled before syncing.
  • Report results to the user: sessions, observations, prompts, mutations exported.
  • Fail fast on 403/forbidden errors — that means the project needs enrollment first.

Execution Steps

  1. Check cloud status: engram cloud status --cwd <repo> (default: current project directory). If Auth status: ready and Sync readiness: pending, continue.
  2. If project is not enrolled (403: forbidden: project is not allowed or similar), run engram cloud enroll turnosxpress --cwd <repo> then re-check status.
  3. Execute sync: engram sync --cloud --project turnosxpress --cwd <repo>.
  4. Report results — sessions, observations, prompts, mutations count. If sync fails, surface the exact error and suggest running engram serve for autosync mode.

Output Contract

Return:

  • Cloud server URL and enrollment status.
  • Export counts: sessions, observations, prompts, mutations.
  • Confirmation: "Cloud sync complete" or actionable error if it failed.