Telnyx Rag
ReviewAudited by ClawScan on May 10, 2026.
Overview
This appears to be a legitimate Telnyx-backed memory search skill, but it will upload selected workspace files to Telnyx and should be configured carefully.
Install only if you are comfortable uploading the configured workspace files to Telnyx. Before running setup or sync, review config.json, choose the intended bucket, add exclusions for secrets or private files, and keep TELNYX_API_KEY/.env protected and trusted.
Findings (5)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Your selected local memory, knowledge, docs, and skill content may be stored and reused as RAG context through Telnyx.
The skill intentionally sends selected workspace content into a cloud-backed embedding/search workflow, which is purpose-aligned but can include private memory or agent context.
- **Indexes** your workspace files (MEMORY.md, memory/*.md, knowledge/, skills/) - **Embeds** content automatically using Telnyx AI
Review config.json patterns and exclusions before syncing, and avoid indexing files that contain secrets, private user data, or instructions you do not want reused.
Running setup can upload configured workspace files and start Telnyx embedding work.
Full setup performs cloud/storage actions, including bucket creation or verification, file sync, and embedding trigger. These are expected for the skill but are more than a passive install check.
python3 "$SCRIPT_DIR/sync.py" --create-bucket --quiet ... python3 "$SCRIPT_DIR/sync.py" --quiet ... python3 "$SCRIPT_DIR/sync.py" --embed --quiet
Run setup only after confirming the bucket name and file patterns, and use validation/check modes only with a key you are comfortable testing.
If the .env file is untrusted or modified, running setup could execute unintended shell commands.
The setup script loads .env by sourcing it as shell, so a tampered .env could execute shell syntax instead of merely providing TELNYX_API_KEY.
set -a # Enable export of all variables source "$SCRIPT_DIR/.env" set +a
Create .env yourself, keep it to a simple TELNYX_API_KEY assignment, and do not run setup with an untrusted .env file.
Anyone who obtains the key may be able to access or mutate Telnyx resources allowed by that key.
The skill uses a Telnyx bearer API key for provider calls, which is expected for this integration but grants access according to that key's Telnyx permissions.
-H "Authorization: Bearer $TELNYX_API_KEY"
Use a suitably scoped Telnyx key if available, protect .env permissions, and rotate the key if it may have been exposed.
Files could be uploaded to a different Telnyx bucket than the user expected if they follow the default setup path without checking output.
The setup script defaults to openclaw-memory and rewrites config.json; users should verify this because the quick-start text says setup uses the bucket from config.json.
BUCKET="${1:-openclaw-memory}" ... config['bucket'] = '$BUCKET'Pass an explicit bucket name or confirm config.json after setup before syncing sensitive content.