STM Assistant
PassAudited by ClawScan on May 10, 2026.
Overview
The skill is a transparent email-assistant recipe, but it gives the agent delegated email-sending and inbox-monitoring duties, so install only with a dedicated inbox and clear approval boundaries.
This skill appears coherent and instruction-only, with no hidden code or install script. Before using it, configure a dedicated email inbox, confirm the CC and Reply-To behavior works, define which emails require approval, and control any scheduled inbox-monitoring process.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent may send routine professional emails on your behalf before you review them.
The instructions allow the agent to send routine outbound emails without pre-send approval. This is central to the skill and bounded by CC/Reply-To and high-stakes approval rules, so it is a note rather than a concern.
“Routine emails (scheduling, follow-ups, informational) — send directly, notify human after”
Use a dedicated inbox and give the agent a clear policy for recipients, topics, and what must be approved before sending.
Whoever controls the configured provider account can send messages from the assistant inbox.
The skill relies on delegated access to an email-sending account through mcporter/AgentMail or SMTP. This is expected for the stated purpose and no credential leakage or unrelated account use is shown.
“Agent inbox — via AgentMail (`mcporter call agentmail.create_inbox displayName="Your Assistant"`) or any SMTP provider” and “mcporter with agentmail configured”
Create a dedicated assistant inbox with limited privileges, keep credentials in the provider’s normal configuration, and avoid reusing a personal mailbox if not needed.
Email contents and metadata may be handled by the chosen email provider, and a hosted logo may be fetched from an external image host by recipients’ mail clients.
Outbound email content, recipient metadata, replies, and signature images depend on external provider services. That data flow is disclosed and expected for an email assistant.
“AgentMail account (or any SMTP provider)” and “Image hosting for email signature logo”
Use trusted providers, avoid tracking-style image hosts unless intended, and do not send highly sensitive content unless the provider setup is appropriate.
A scheduled assistant could continue checking the inbox and changing message labels after initial setup.
The skill recommends ongoing inbox monitoring and message label updates. This is disclosed and fits the email-assistant purpose, but it is still persistent behavior the user should control.
“Check for replies on a regular cycle (heartbeat or cron)” and “Always mark processed emails.”
Set an explicit monitoring frequency, decide who receives alerts, and remove any heartbeat or cron job when the assistant is no longer needed.