Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Lel Mail
v1.1.4Send and read email via a combination of python and bash scripts which makes use of the main agent for reasoning and logic. This skill enables the agent to w...
⭐ 0· 734·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
Name/description promise (send/read email) mostly matches the files, but the runtime depends on invoking the 'openclaw' agent binary for LLM-driven decisions and for writing to agent memory/sessions. The declared required binaries list only 'python3' — 'openclaw' is a required runtime dependency but is not declared. That mismatch is unexpected and disproportionate.
Instruction Scope
The scripts do more than just fetch/send mail: check_email.sh asks the LLM to classify emails and then issues further 'openclaw agent' commands that instruct the agent to scan memory banks, write to MEMORY.md, locate user sessions, and proactively reach out or request inputs. This gives the skill broad discretion to read and modify agent memory and contact users, which goes beyond a narrow mail fetch/send scope.
Install Mechanism
Instruction-only skill with shipped scripts (no remote installers). Nothing is downloaded from external URLs; code is local. This is a lower install risk, but files will be written to the user's home config paths when used.
Credentials
No declared environment variables, which is reasonable, but the skill requires a local config.json containing email account credentials (user/password or app-specific password). Storing raw passwords in ~/.config/lel-mail/config.json is necessary for SMTP/IMAP but is sensitive and not enforced by the metadata. Also, the script relies on the 'openclaw' CLI (undeclared), which is a credential/privilege vector because the skill asks that CLI to take actions on agent memory and sessions.
Persistence & Privilege
The skill does not set always:true, but SKILL.md instructs the user to add a cron job to run the email_sender_daemon regularly. Combined with the agent-invocation behavior, that cron-driven persistence plus autonomous agent calls can send emails and alter agent memory without interactive approval. The skill does not modify other skills' configs directly, but it requests writing into agent memory files.
What to consider before installing
This skill largely does what it says (send/read emails), but there are several things to check before installing or enabling it:
- Missing declared dependency: the scripts call 'openclaw agent' but the skill only declares python3. Ensure the 'openclaw' CLI is present and you understand what it can do — the skill relies on it to invoke LLM-driven actions and to write to agent memory.
- Sensitive credentials: the skill requires a plaintext ~/.config/lel-mail/config.json with account passwords/app-specific passwords. Store that file with strict permissions and consider using app-specific passwords or a dedicated throwaway account. Audit the config storage and rotate credentials if needed.
- Broad agent actions: the skill instructs the agent to scan memory banks, write to MEMORY.md, locate user sessions, and proactively contact users. If you don't want the agent to modify its memory or contact users automatically, do not enable autonomous invocation or avoid installing the cron job.
- Cron persistence: the SKILL.md asks you to add a cron entry for periodic sending. If you install that, the skill can send queued emails automatically. Only add the cron job if you trust the configuration and have reviewed the scripts.
- Recommended mitigations: run in an isolated environment (container or dedicated account), inspect/modify scripts to require explicit confirmation before sending, restrict file permissions on ~/.config/lel-mail, and ensure the 'openclaw' CLI has expected behavior and access controls. If you need clarification from the author (unknown source), ask why 'openclaw' isn't declared and whether the LLM-driven write-to-memory behavior can be limited.Like a lobster shell, security has layers — review code before you run it.
latestvk9730xxrrbrtdn7dyzs660ds3x829yn2
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
📧 Clawdis
Binspython3
