SKILLEMALL.ai
RU Sign in

BD imap-smtp-email

Read and send email via IMAP/SMTP using exec commands run from /local/mnt/workspace/vthoram/.openclaw/workspace/skills/imap-smtp-email. To check inbox/recent/unread emails: exec 'node scripts/imap.js check --limit 10'. To search: exec 'node scripts/imap.js search --unseen --limit 20'. To fetch one email by uid: exec 'node scripts/imap.js fetch <uid>'. To send an email: exec 'node scripts/smtp.js send --to <email> --subject <text> --body <text>'. Use this skill for ANY request mentioning email, inbox, mail, messages, or unread. Always run commands with workdir set to the skill directory above.

ClawHub Agent Skills author: Madhu Thoram v1.0.1 MIT-0 12 files · 1 script body ≈ 1 430 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

As a process D 48/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureGmailOutlookSoftware developmentData and analyticstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
85/100
safety, quality, tests
Safety 60%
95
Quality 40%
71
Run on models
none yet
Process rating
D
48/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: imap-smtp-email (ClawHub)

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 5

    ✓ No critical or high findings

    Medium and low: 5
    • low Secrets in code secret-high-entropy-token package-lock.json:22
      High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
      "integrity": "sha5…ejx+0Gxj…AIA/QTDR…aX6+5bCZslr+gWQ==",
      detector
    • low Secrets in code secret-high-entropy-token package-lock.json:35
      High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
      "integrity": "sha5…sw1+QZnlLX+/gihc…gkc//J3jVd76o/WS+taUiA==",
      detector
    • low Secrets in code secret-high-entropy-token package-lock.json:52
      High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
      "integrity": "sha5…Rog+eW3ph+GYCbj+rK+uYyR…tPn+QJlKFvWP/1PYp…nFn+A==",
      detector
    • low Secrets in code secret-high-entropy-token package-lock.json:75
      High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
      "integrity": "sha5…9co+7Zrb…CSH/zJvXw56gmHw==",
      detector
    • low Secrets in code secret-high-entropy-token package-lock.json:128
      High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
      "integrity": "sha5…rOD+dRAb…H0c+OhJA…o6A==",
      detector

    Files scanned: 12. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • warning frontmatter-yaml SKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Read and send email via IMAP/SMTP using exec commands run from /lo… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value

    Process rating: all ten parameters 48/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 8 mutating operations with no state check
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (web) that frontmatter does not declare
    • 100Steps. 29 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1430 tokens
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
    • low The response is described with custom markup (10 tags): a typed call is more reliable

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • -31 of 3 scripts are never mentioned in SKILL.md
    • +1No license
    • +2Single-language instructions
    • +3Description length 599: enough signal without eating the budget
    • +4Structure: 16 headings
    • +3Step-by-step instructions: 29 items
    • +4Has examples (11 code blocks)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.

    External checks

    ClawHub: suspicious
    This is a real email-access skill, but it asks for broad always-on mailbox authority and stores/sends with credentials in ways users should review carefully.
    LLM: suspicious (high) · VirusTotal: · 14 Jul 2026