Client Communication Engine

• Verdict: Pass
• Confidence: Medium
• Analyzed: Feb 21, 2026, 1:49 PM
• Findings: 0
• Version: 0.1.0

Overview

The skill's declared requirements and runtime instructions are coherent with a Greek-language client email/drafting tool that needs local storage and SMTP credentials, but there are a few small metadata and enforcement gaps to verify before trusting it with real credentials.

This skill appears coherent for drafting and sending Greek client emails and needs SMTP credentials and a data directory to work. Before installing: 1) Confirm the registry metadata is updated to mark SMTP_* as the primary credential so reviewers know the main secret expected. 2) Prefer providing an app-specific SMTP password with limited scope and use an account dedicated to outbound firm mail. 3) Verify (or test in a sandbox) that sending truly requires explicit human approval and that there is no background job or autonomous path that can call 'openclaw comms send' without confirmation. 4) Set OPENCLAW_DATA_DIR to a restricted directory you control and review log/storage retention policies for /data/clients. 5) If you plan to provide SLACK_WEBHOOK_URL, treat it as sensitive and restrict its scope. If any of these checks fail or you cannot inspect the live implementation that enforces manual approval, consider testing in an isolated environment first.