Toingg Ops Toolkit
v1.1.0Create and launch Toingg voice-calling campaigns by POSTing user-supplied JSON to the toingg/make_campaign API. Use when Codex needs to turn campaign briefs...
⭐ 0· 358·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill's name, description, and scripts consistently implement Toingg campaign, call, analytics, contact upload, and WhatsApp functionality. However, the skill metadata declares no required environment variables or primary credential while every script and the SKILL.md rely on a TOINGG_API_TOKEN bearer token. That omission is an incoherence between declared requirements and actual capability.
Instruction Scope
SKILL.md and reference docs stay within the stated domain (calling Toingg endpoints and handling JSON/Excel files). But they also (a) recommend storing payloads/analytics/contact exports in version control or shared storage (risk of committing PII/credentials), (b) include a hard-coded example cron path referencing a specific user home (/Users/abhinavkalvacherla/.openclaw/...), and (c) explicitly instruct ensuring the TOINGG_API_TOKEN is visible to the gateway environment before enabling the cron. These practices could expose the token or user data if followed without care.
Install Mechanism
This is an instruction-only skill with bundled Python scripts; no install spec is present. The SKILL.md advises installing Python deps (openpyxl, requests) via pip, which is expected for Excel parsing and HTTP calls and presents standard, low-risk installation steps.
Credentials
Runtime behavior requires a single bearer token (TOINGG_API_TOKEN) used across all scripts; that is appropriate for the service. However the skill's manifest fails to declare this required environment variable. The instructions push users to export the token in all environments (including the gateway used for cron), which could increase exposure. The scripts will also process and transmit contact lists (PII) to the remote API — this is functionally required but elevates the sensitivity of where tokens and data are stored.
Persistence & Privilege
The skill itself is not always-enabled and does not auto-enable itself. It documents an opt-in 'openclaw cron create' workflow to schedule daily analytics, which creates a persistent cron job on the platform and requires the token to be available to the gateway. This persistence is user-triggered, but because a scheduled job runs with the gateway environment, enabling it without verifying token handling could increase risk.
What to consider before installing
This toolkit appears to do what it says, but take these precautions before installing or enabling scheduled runs: (1) Treat TOINGG_API_TOKEN as sensitive — do not commit it to source control; instead use secure secret storage or the platform's recommended secret mechanism. Note the skill metadata does not declare this required env var — ask the publisher to update it. (2) Avoid storing contact lists, campaign payloads, or analytics snapshots in public or shared repositories; they contain PII. (3) If you enable the recommended cron, verify where the cron runs and how the gateway exposes environment variables (rotate the token after enabling and restrict its permissions if possible). (4) Confirm the external API domain (https://prepodapi.toingg.com) is the legitimate endpoint you expect. (5) If you need stronger assurance, run the scripts locally against test data first, inspect network calls, and only grant the token to environments you control. The main concrete red flag is the metadata mismatch (missing required env var); ask the skill author to fix that before broad deployment.Like a lobster shell, security has layers — review code before you run it.
latestvk979b3wtr3as8vpk9dv525qjfx8246yv
License
MIT-0
Free to use, modify, and redistribute. No attribution required.