holo-updater

Update the HOLO-AGENT codebase from GitHub with backup and validation.

2|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/Wike-CHI/acquisition-agent --skill holo-updater
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: holo-updater
Source: https://github.com/Wike-CHI/acquisition-agent/tree/main/skills/holo-updater
Command: npx skills add https://github.com/Wike-CHI/acquisition-agent --skill holo-updater

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, rsync, python, curl, and includes scripts (resource) components.

What problem does it solve?

Keeping the HOLO‑AGENT acquisition system up‑to‑date manually is error‑prone and time‑consuming; this skill automates the entire update process.

Core Features & Use Cases

  • Pre‑check: Verifies network connectivity, git installation, and required tools.
  • Version comparison: Detects remote commits and shows change previews.
  • Backup: Saves the current skills/ directory to a timestamped .backup folder, retaining the five most recent backups.
  • Sync: Uses rsync (or cp fallback) to synchronize the skills/ directory while excluding Git metadata and archives.
  • Validation: Confirms presence of critical files and validates YAML manifests.
  • Report: Generates a concise update summary with success/failure status.

Typical use cases include updating HOLO‑AGENT after new releases, refreshing the acquisition‑agent skill set, or ensuring the latest code is deployed across development environments.

Quick Start

Ask the agent to update HOLO‑AGENT by saying “Update HOLO‑AGENT to the latest version.”

Frequently Asked Questions about holo-updater

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

FAQPage Schema
How do I automatically sync my agent skills directory from GitHub?

To automatically sync your agent skills directory from GitHub, you can use an update script that fetches remote commits and uses rsync to synchronize the local folder. This process typically includes backing up the current directory and validating YAML manifests to ensure a successful deployment.

What is the best way to backup a local codebase before pulling updates?

The best way to backup a local codebase before pulling updates is to copy the existing directory into a timestamped backup folder. This retains previous states, allowing you to keep the five most recent backups and revert if the new synchronization fails or causes issues.

Do I need rsync and git installed to update my local agent setup?

Yes, you need git installed to fetch updates and rsync to synchronize the skills directory, although a cp fallback is available if rsync is missing. Optional python is recommended for validating YAML manifests, and network connectivity is required to reach the GitHub repository.

Can I validate YAML manifests after synchronizing files from a remote repository?

Yes, you can validate YAML manifests after synchronizing files from a remote repository by using python. The update process checks for the presence of critical files and runs YAML validation to confirm the integrity of the newly synced skills directory before finalizing the deployment.

Why does my local sync exclude Git metadata when copying files?

Local sync excludes Git metadata when copying files to prevent overwriting your local repository configuration with the remote repository's internal Git data. This ensures that only the actual skill files are updated while preserving your local Git history and branch tracking.

What are the limitations of using cp fallback instead of rsync for directory sync?

Using cp fallback instead of rsync for directory sync limits the ability to efficiently transfer only modified files, as cp copies everything blindly. Rsync provides faster, more reliable synchronization by comparing file differences, making the fallback slower for large directories.