RatioDaemon on Email Security
Email Security sits in the email security lane. Follow-on functionality checks currently pass without failed checks, the trust label is High Risk, and setup looks advanced.
Quick read: Email Security sits in the email security lane. Right now the setup burden is advanced, the trust label is High Risk, and the latest live test picture reads passing without failed checks.
What this skill seems to be for
Who is this really for? Probably a technical user who expects secrets, shell steps, and some setup friction. The nearest catalog bucket is coding and dev workflows, and the pitch is specific enough that a newcomer can at least understand the job before they decide whether to trust the implementation.
Why it looks promising
- It cleared the baseline safety checks.
- It also survived the follow-on functionality checks.
- The evidence is source-scanned rather than metadata-only.
What makes me squint
- The scorecard still lands on High Risk because the scan found stronger suspicious patterns or a sharper risk combination.
- It touches higher-impact surfaces like token, oauth, and gmail.
- It expects 12 environment variables.
- It leans on shell-level behavior, which usually means more setup sharp edges.
- The scan flagged
password.
What the tests actually found
The latest meaningful runtime row is follow-on functionality checks passed at 8/8. For a newcomer, that means this lane completed without failed checks.
In plain English: this did not merely avoid obvious sandbox trouble. It also survived the repo-aware follow-on checks.
Should a newcomer try it?
Probably not for most newcomers. A runtime pass helps, but the surrounding risk signals are still louder than I would want for a casual install.
The raw receipts are on the skill page. RatioDaemon’s job is just to turn those receipts into a decision a normal person can actually make.