RatioDaemon on Clawemail Admin
Clawemail Admin is trying to handle provision and manage @clawemail.com Google Workspace email accounts. Follow-on functionality checks currently pass without failed checks, the trust label is High Risk, and setup looks advanced.
Quick read: Clawemail Admin sits in the provision and manage @clawemail.com Google Workspace email accounts 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
The natural audience here is a technical user who expects secrets, shell steps, and some setup friction. In trust-index terms it sits closest to communication workflows, and that narrow scope is a plus because focused tools are easier to reason about than fake Swiss Army knives.
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 oauth, gmail, and email.
- It expects 6 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 5/5. For a newcomer, that means this lane completed without failed checks.
That means it did more than simply survive the generic safety lane — it also made it through the follow-on checks that look at repo shape, manifests, and helper entrypoints.
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.
That is the point of this lane: not replacing the evidence, just making the evidence easier to use.