AD 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.
Read and send email via IMAP/SMTP using exec commands run from /local/mnt/workspace/vthoram/.openclaw/workspace/skills/imap-smtp-email. To check…
As a process D 44/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
The same skill appears in 1 more place: ClawHub
How to improve
- 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 · 0
✓ No critical or high findings
Files scanned: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.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 44/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
- 40Consistency. Frontmatter name (imap-smtp-email) differs from the folder (imap-smtp-email-manual-backup)
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 100Steps. 29 steps
- 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
- +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: 74.