Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Telegram - Conversa por Áudio (PICOCLAW)
v1.0.1Processar conversas por áudio no Telegram nativo do Picoclaw, sem webhook. Use quando o usuário quiser receber mensagem de voz, transcrever áudio recebido, g...
⭐ 0· 68·0 current·0 all-time
byFabyano Titara@titara
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 functionality (transcribe with GROQ Whisper and synthesize with Edge TTS) is consistent with its description, but the registry metadata declares no required env vars or dependencies while SKILL.md and the scripts require GROQ_API_KEY, optionally PICOLAW_CHAT_ID/TELEGRAM_CHAT_ID, and Python packages (groq, edge_tts). The scripts also assume state directories under /root/.picoclaw and /tmp/picoclaw_media — these deployment assumptions are not declared in the registry and may be surprising or privilege-sensitive.
Instruction Scope
SKILL.md gives concrete runtime instructions (start a nohup watcher, call finalize_reply) and explicitly forbids webhooks. The instructions and scripts operate on local media folders, write state/metadata files, and rely on environment variables (GROQ_API_KEY, PICOLAW_CHAT_ID). They do not contain obvious exfiltration endpoints, but they do instruct running a persistent background process with file read/write access in the agent's workspace.
Install Mechanism
There is no install specification even though the code imports third-party Python libraries (groq, edge_tts). Without an install step or dependency manifest the skill will fail at runtime or silently rely on preinstalled packages. The lack of an explicit, vetted install source increases risk and deployment friction.
Credentials
The registry lists no required env vars, but SKILL.md and the scripts require GROQ_API_KEY (mandatory for transcription) and optionally PICOLAW_CHAT_ID / TELEGRAM_CHAT_ID. Edge TTS usage implies outbound network access. The skill also copies the full environment into subprocesses (env=os.environ.copy()), which can expose unrelated env variables to child processes — this should be considered when running in environments with sensitive env vars.
Persistence & Privilege
The skill does not set always:true, but the user is instructed to run a persistent background watcher (nohup). The scripts create and manage files under /root/.picoclaw/workspace/state/telegram-native-audio and /tmp/picoclaw_media and implement automatic cleanup. This provides persistent on-disk state and long-running processes but no modification of other skills' configs; still, running persistent processes and writing under /root are privilege decisions the operator should review.
What to consider before installing
This skill's code implements voice-to-voice processing and appears to do what it claims, but there are deployment mismatches and operational risks to consider before installing:
- Required secrets/deps: The SKILL.md and scripts require GROQ_API_KEY (transcription) and rely on Python packages (groq, edge_tts), but the registry metadata declares no env vars or install steps. Do not run it without supplying GROQ_API_KEY and installing those packages in a controlled environment.
- Installation: Add a clear dependency/install step (pip install groq edge_tts ...) or run in a virtualenv/container. Avoid running arbitrary code without pinning package versions.
- Privileges & paths: The scripts use hardcoded /root/.picoclaw paths and /tmp/picoclaw_media and instruct starting a persistent nohup process; consider adjusting paths to a less-privileged user and run the watcher under a managed service/sandbox (systemd unit, container) rather than as root.
- Environment leakage: finalize_reply/other scripts pass os.environ.copy() to subprocesses — ensure no sensitive environment variables are present or sanitize env before running.
- Cleanup policy: The cleanup script deletes .json files and audio older than 15 days in the skill state directories. Confirm this retention policy is acceptable and that important metadata won't be removed unintentionally.
- Network & secrets: Transcription and TTS call external services; ensure you trust the services and the provided API key scope. Monitor outbound network usage.
If you want to proceed safely: request an install manifest from the author (requirements.txt or pyproject), confirm required env vars in registry metadata (GROQ_API_KEY, optional PICOLAW_CHAT_ID), run the skill in a container or dedicated service account, and review logs during an initial test. If the author cannot supply a dependency list or explain the /root path choice, treat the package with extra caution.Like a lobster shell, security has layers — review code before you run it.
latestvk978j3309nyjr1kbeagy12229x849s76
License
MIT-0
Free to use, modify, and redistribute. No attribution required.