Automated summary
This skill guides verifying, manually triggering, and auditing system backups and cloud sync for the piMitters and nixMitters machines and the Sofia database.
Strengths
- Explicitly forbids touching the production SQLite database directly and requires confirmation before any mutation
- Gives the exact commands to trigger each backup via systemctl --user or the underlying shell script
- Includes concrete audit steps: log inspection, listing SQLite .backup copies, and checking rclone remote status
Limitations
- Hardcoded paths and usernames (kyle, /mnt/piCloud, pi5-backup) make it non-portable to another machine
- No restore procedure and no real integrity check — only presence of backup files and log output
- Assumes user-level systemd services and an already configured rclone remote
When you need to confirm last night's backup actually ran, re-run a backup on demand, or check that the Google Drive sync is current.
When you need to restore data or repair a corrupted backup, since the skill describes no recovery or integrity-validation procedure.
Security analysis
CautionThe skill is for legitimate backup verification and explicitly forbids touching the production SQLite database and requires confirmation before mutations. However, it runs systemd backup units, an external script, and rclone network commands, so it is not entirely risk-free and merits caution rather than a safe rating.
- •Executes systemctl units and a shell script (/home/kyle/NixOS/scripts/backup-piMitters.sh) whose contents are not included in the skill, so their full effects are unknown.
- •Uses rclone to access remote cloud storage, a network operation that could sync data externally.
Examples
Check whether the piMitters backup ran last night and confirm the rclone sync to gdrive:systems-backups completed.Trigger the Sofia database backup and verify that fresh .backup copies appeared in /mnt/piCloud/pi5-backup/sqlite-backups/.Read /home/kyle/backup-piMitters.log and tell me if any of the recent backup or cloud sync steps failed.name: backup-verification description: Verify, test, and audit backup status and cloud sync for nixMitters and piMitters. disable-model-invocation: true allowed-tools: run_command
Backup Verification Operations
Guidelines for verifying, executing, and auditing system backups.
Safety Constraints
- CRITICAL: Never touch
/var/lib/shiny-data/sofia/sofia.sqlitedirectly. All operations must proceed on backup copies. - CRITICAL: Ask for explicit confirmation before database mutations.
Manual Executions
1. Trigger Full Server Backup
Manually run the daily backup and cloud sync script:
systemctl --user start backup-piMitters
Or run the script directly to see inline output:
/home/kyle/NixOS/scripts/backup-piMitters.sh
2. Trigger Sofia DB Backup
systemctl --user start backup-sofia-q2h
3. Trigger Laptop Backup
systemctl --user start backup-nixMitters
Verification & Auditing
- Check the log files:
/home/kyle/backup-piMitters.log. - Verify SQLite online
.backupcopies:ls -lh /mnt/piCloud/pi5-backup/sqlite-backups/ - Validate
rclonecloud status:rclone lsd gdrive:systems-backups
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/backup-verification-mrwakbm7/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/backup-verification-mrwakbm7' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/backup-verification-mrwakbm7/download' --output '.skill-downloads/backup-verification-mrwakbm7/SKILL.md.part' && mv '.skill-downloads/backup-verification-mrwakbm7/SKILL.md.part' '.skill-downloads/backup-verification-mrwakbm7/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): run_command
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/backup-verification-mrwakbm7/SKILL.md' && test -s '.skill-downloads/backup-verification-mrwakbm7/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/backup-verification' && cp -R '.skill-downloads/backup-verification-mrwakbm7' '.claude/skills/backup-verification'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/backup-verification-mrwakbm7'openskills read 'backup-verification-mrwakbm7'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/backup-verification-mrwakbm7/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Configure a Chat Channel with SecretRefs
DevOps
Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.
Investigate ClickHouse CI Failures
DevOps
Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.
Ansible PR Review
DevOps
Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.