Backup To Telnyx Storage

Backup and restore your OpenClaw workspace to Telnyx Storage. Simple CLI-based scripts with no external dependencies.

This skill appears to implement legitimate backup and restore logic, but there are several inconsistencies you should verify before installing: - SKILL.md contradicts itself: it says "no environment variables" but the metadata and code require TELNYX_API_KEY. Expect to provide a Telnyx API key or run telnyx auth setup. - The repo includes two approaches: shell scripts that use the Telnyx CLI and a legacy Python script that uses boto3 and a Telnyx S3 endpoint. Decide which you will use and verify its dependencies (npm global package name differs across files). - The Python script actively searches .env files in your workspace and the skill folder to locate TELNYX_API_KEY. If you keep other secrets in .env files, be aware the script will read them (it looks for the TELNYX_API_KEY entry). Consider setting TELNYX_API_KEY in your environment or reviewing .env files first. - The backup scope includes files and directories that may contain sensitive data (memory/, knowledge/, scripts/, skills/). Review the FILES_TO_BACKUP list and remove or exclude anything you don't want backed up to remote storage. - Test the scripts in an isolated environment (or with a non-production Telnyx bucket/key) to confirm the CLI commands and create/list/delete behavior match your expectations. Given these mixed signals (documentation, package-name inconsistencies, and the .env lookup), treat this skill with caution and validate its behavior and credentials handling before using it for production backups.

Type: OpenClaw Skill Name: telnyx-storage-backup Version: 1.0.0 The OpenClaw AgentSkills bundle 'telnyx-storage-backup' is designed for backing up and restoring OpenClaw workspace data to Telnyx Storage. The `SKILL.md` provides clear instructions without any prompt injection attempts. The `backup.sh`, `list.sh`, `restore.sh`, and `backup.py` scripts perform standard file archiving, upload, download, and deletion operations using either the Telnyx CLI or boto3. All network activity is directed to Telnyx Storage, and file system access is confined to the user's workspace and temporary directories. While shell scripts inherently carry some risk with user-provided arguments, the scripts use quoted variables and include a user confirmation for restore operations, indicating a focus on safe operation rather than malicious intent. No evidence of data exfiltration to unauthorized endpoints, persistence mechanisms, or other malicious behaviors was found.