tabula-backup

Back up agent collective state to a remote Git repository.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/Heretek-AI/heretek-skills --skill tabula-backup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tabula-backup
Source: https://github.com/Heretek-AI/heretek-skills/tree/main/skills/tabula-backup
Command: npx skills add https://github.com/Heretek-AI/heretek-skills --skill tabula-backup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, tar, crontab, mktemp, sed, cp, mkdir.

What problem does it solve?

Back up the agent collective state to a remote Git repository to create recovery points and preserve collective memory.

Core Features & Use Cases

  • Hourly backups of workspace, gateway config, agent identity files, installed skills, and cron jobs.
  • Supports restoration workflows and cross-node recovery in case of failures.
  • Schedule management via crontab; central management via triad-cron-manager.

Quick Start

Run the first backup by ensuring the environment is configured (GITHUB_TOKEN, paths) and executing the backup.sh script.

Frequently Asked Questions about tabula-backup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate hourly backups of my agent workspace to a remote Git repository?

To automate hourly backups to a remote Git repository, schedule the backup script via crontab. It compresses your workspace, gateway config, agent identities, installed skills, and cron jobs into a tarball, then pushes it to host-specific Git branches.

What files and configurations are included when backing up agent collective state?

Backing up agent collective state includes the workspace, gateway config, agent identity files, installed skills, and cron jobs. It packages these elements into a tarball with metadata for pushing to a remote Git repository.

Do I need a GitHub token to back up agent state to Git branches?

Yes, a GitHub token is required to back up agent state to Git. The script reads environment variables for the token and repository paths to authenticate and push the backup tarball to the appropriate host-specific branch.

Can I restore agent workspace and gateway config across different host nodes after a failure?

Yes, you can restore agent workspace and gateway config across different host nodes. The backup process pushes to host-specific Git branches, enabling cross-node recovery and quick restoration of agent collective memory after failures.

What's the best way to manage disaster recovery schedules for agent state backups?

The best way to manage disaster recovery schedules is via crontab for hourly execution, or centrally managed through a triad-cron-manager. This ensures regular recovery points are created without manual intervention.