SKILLEMALL.ai

CD send-email-api

USE THIS to send email, send message, email automation. Send transactional emails (welcome, password reset, notifications), marketing emails, newsletters. AWS SES backend. HTML templates supported. Track opens and clicks. No SMTP setup required.

Not recommendedcritical or high security findings
modbender/skill-library-mcp Hermes author: modbender MIT 1 file body ≈ 257 tokens Open the sourcegithub.com analyzed 2 d ago

USE THIS to send email, send message, email automation.

As a process D 49/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, failures and branches

IntegrationAWSSoftware developmentInfrastructureWriting and documentstype and topics are labelled automatically from the skill text
JSON
Technical rating
C
69/100
safety, quality, tests
Safety 60%
64
Quality 40%
76
Run on models
none yet
Process rating
D
49/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

What is at stake

The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.

Exfiltration
If you install

The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".

For the author

If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.

Dangerous commands
If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

How to improve

  1. Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
  2. For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
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 · 2

  • high Exfiltration exfil-send-secrets-to-url SKILL.md:49
    Instruction to send secrets/history to an external endpoint (security demo / example)
    Send a password reset email to jo…@….com with reset link https://myapp.com/reset/abc123
    demo
  • high Dangerous commands cmd-pipe-to-shell SKILL.md:55
    Downloads and executes remote code from an unrecognised host (pipe to shell)
    curl -fsSL https://skillboss.co/openclaw-setup.sh | bash

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

Against the Agent Skills spec

  • warning description-long-hermes description is 245 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • note frontmatter-key unknown frontmatter key "tagline"
  • note frontmatter-key unknown frontmatter key "homepage"
  • note frontmatter-key unknown frontmatter key "support"
  • note frontmatter-key unknown frontmatter key "pricing"

Process rating: all ten parameters 49/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 3 mutating operations with no state check
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 70When it triggers. States when to use, but not when not to
  • 100Steps. 12 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 257 tokens

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
  • +2Single-language instructions
  • +3Description length 245: enough signal without eating the budget
  • +4Structure: 6 headings
  • +3Step-by-step instructions: 12 items
  • +4Has examples (3 code blocks)
  • +1License stated

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