← Back to Skills Marketplace
leli1024

Lel Mail

by Leli1024 · GitHub ↗ · v1.1.4
cross-platform ⚠ suspicious
813
Downloads
0
Stars
1
Active Installs
11
Versions
Install in OpenClaw
/install lel-mail
Description
Send 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...
README (SKILL.md)

Lel Mail

Important Note If Running On the Cloud/VPS

  • Some cloud providers explicitly disable email leading to failiure of these scripts, services like tailscale will be needed to bypass these blocks

Setup

Setting up the Config File

Create ~/.config/lel-mail/config.json:

[
  {
    "provider": "gmail",
    "config": {
        "smtp": {
        "server": "smtp.gmail.com", //Default url
        "port": 587 //Default port
      },
      "imap": {
        "server": "imap.gmail.com", //Default url
        "port": 993 //Default port
      }
    },
    "auth": {
      "user": "[email protected]",
      "password": "XXXX XXXX XXXX XXXX" //Gmail Requires App Specific Password Rather Than Your Normal Password
    },
    "can_send": true,
    "can_read": true
  }
]

Setting up cron job

Set up a simple cron job which runs the following command every 5 minutes with a randomised 30-90 second delay. Confirm with user the interval to be used: ~/.openclaw/workspace/skills/lel-mail/scripts/email_sender_daemon.sh

Quick Reference

Read Email

  1. Make sure config exists, if not create it with input of user
  2. Reference USERS.md (or whatever USER reference file your system uses) to see what email(s) you need to check unless user explicitly defines the email(s)
  3. Run the following command ~/.openclaw/workspace/skills/lel-mail/scripts/check_email.sh \x3CUSER_EMAIL>

Send Email

Note, this script does not send the data directly but sends it to a scheduler which will automatically send it in approximately 5.5 minutes

  1. Make sure you have the necessary data to send the email from the user, that includes sender, recipient and body, everything else is optional
  2. Run the following command ~/.openclaw/workspace/skills/lel-mail/scripts/email_send.sh --sender \x3Csender> --recipient \x3Crecipient> --subject \x3Csubject> --body \x3Cbody> [--cc ...] [--bcc ...] Note: if using BCC/CC note that CC/BCC are comma-separated lists

3. Manage Outgoing Queue

Outgoing emails are scheduled to send with a random delay (30-90 seconds). You can list or delete these before they are sent.

List all queued emails:

python3 ~/.openclaw/workspace/skills/lel-mail/scripts/manage_queue.py --list

Delete a specific email by ID:

python3 ~/.openclaw/workspace/skills/lel-mail/scripts/manage_queue.py --delete \x3CID>

Troubleshooting

Prompt user to assist when errors occur due to missing/invalid credentials/configuration

  • If emails aren't sending at all check that a cron job for the daemon is running
Usage Guidance
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.
Capability Analysis
Type: OpenClaw Skill Name: lel-mail Version: 1.1.4 The skill is classified as suspicious due to a critical prompt injection vulnerability found in `scripts/check_email.sh`. This script directly embeds untrusted email content (subject, sender, body) into prompts sent to the `openclaw agent`. An attacker sending a crafted email could inject arbitrary instructions into the agent's subsequent actions, such as adding malicious content to the agent's memory, sending unauthorized notifications to the user, or coercing the agent to request and then exfiltrate sensitive information via the `lel-mail` skill itself. This is a severe design flaw that allows for malicious exploitation, rather than being inherently malicious code.
Capability Assessment
Purpose & 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.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install lel-mail
  3. After installation, invoke the skill by name or use /lel-mail
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.1.4
- Updated the skill description to clarify that receiving emails can trigger agent actions such as adding to memory or sending responses. - No changes to code or functionality; documentation update only.
v1.1.3
- Updated description to clarify that the email queue management is handled by a Python script. - No functional changes; documentation improved for accuracy and clarity.
v1.1.2
- Added new script manage_queue.py to list and delete pending outgoing emails before they are sent. - Updated documentation with instructions for managing the outgoing email queue. - Description now mentions queue management functionality.
v1.1.1
- Expanded skill description to include writing to memory from email content and user notification/request features. - No changes to setup or usage steps. - No breaking or behavioral changes; skill functionality remains consistent.
v1.1.0
Updated for clear description and better data handling
v1.0.5
Critical bug fixes
v1.0.4
- Improved scripts/check_email.sh with modifications (details not shown). - No changes to documentation or user-facing guidance.
v1.0.3
- Updated required dependencies: removed jq and curl, only python3 is now required. - Clarified reference to USERS.md, allowing for flexible user reference file naming. - No functional or command usage changes.
v1.0.2
- Added instructions for setting up a cron job to run the email sender daemon (`email_sender_daemon.sh`) every 5 minutes with a randomized delay. - Advised users to confirm the cron interval. - Updated troubleshooting section to include checking if the daemon cron job is running if emails are not sending.
v1.0.1
- Updated scripts/email_sender_daemon.sh (details not shown). - No user-facing documentation changes. - Version bump to 1.0.1.
v1.0.0
Initial release of lel-mail: Send, read, and manage email from the command line. - Supports Gmail configuration for SMTP (sending) and IMAP (reading). - Provides scripts to check emails and send emails with scheduling. - Requires a config file at `~/.config/lel-mail/config.json`. - Supports CC and BCC fields for outgoing emails. - Includes troubleshooting guidance for setup and errors.
Metadata
Slug lel-mail
Version 1.1.4
License
All-time Installs 1
Active Installs 1
Total Versions 11
Frequently Asked Questions

What is Lel Mail?

Send 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... It is an AI Agent Skill for Claude Code / OpenClaw, with 813 downloads so far.

How do I install Lel Mail?

Run "/install lel-mail" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Lel Mail free?

Yes, Lel Mail is completely free (open-source). You can download, install and use it at no cost.

Which platforms does Lel Mail support?

Lel Mail is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Lel Mail?

It is built and maintained by Leli1024 (@leli1024); the current version is v1.1.4.

💬 Comments