atxp-backup_skill

This skill helps you back up and restore your agent's memory and identity md files securely to ATXP servers, ensuring quick recovery.
  • TypeScript

5

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill atxp-dev/cli --skill atxp-backup

  • SKILL.md2.9 KB

Overview

This skill provides free cloud backup and restore for agent identity and memory Markdown files (.md only). It lets you push a snapshot of SOUL.md, MEMORY.md, memory/*.md, AGENTS.md, USER.md, and similar Markdown files to ATXP servers and pull them back to a workspace on another machine. The tool is focused, secure, and designed to help recover or bootstrap agent workspaces quickly.

How this skill works

The skill scans the provided --path directory and collects only files with a .md extension, then uploads them over HTTPS to an ATXP server tied to the authenticated agent identity. A push replaces the server snapshot entirely (no history), while a pull writes the server snapshot files into the target directory without deleting existing local files. Status shows file count, total size, and last sync time; authentication must be completed beforehand.

When to use it

  • After meaningful edits to SOUL.md or MEMORY.md before ending a session (use push)
  • When setting up a fresh machine or restoring a lost workspace (use pull)
  • Before risky changes to local workspace to verify a backup exists (use status)
  • After registering or logging in with ATXP to ensure backups are associated with your agent
  • When moving work between machines or sharing a baseline agent identity

Best practices

  • Always run npx atxp@latest login or agent register before push/pull to ensure correct agent association
  • Run push frequently after substantive content changes; push overwrites the previous snapshot
  • Use pull into an empty or separate directory first to verify contents before merging into a live workspace
  • Keep non-Markdown secrets and credentials out of the workspace; only .md files are transmitted
  • Confirm --path points to the workspace root; there is no auto-detection of workspace location

Example use cases

  • Back up an agent’s SOUL.md and MEMORY.md at the end of each day with npx atxp@latest backup push --path ~/.openclaw/workspace-<id>
  • Recover a lost laptop by running npx atxp@latest backup pull --path ~/restored-workspace to retrieve the latest snapshot
  • Check backup health with npx atxp@latest backup status to see file count, size, and last sync time
  • Migrate an agent identity and memories between environments by pushing from the source and pulling on the target machine
  • Bootstrap a CI or container instance with a known agent state by pulling the snapshot into the container’s workspace

FAQ

No. Only .md files are collected and transmitted. JSON, binaries, credentials, and other file types are never uploaded.

Will push delete my local files or create version history on the server?

Push replaces the single server snapshot and does not create history. Pull is non-destructive locally—it writes server files but does not remove local files that are missing from the server.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational