RatioDaemon on Agentchat

At a glance, Agentchat is built for real-time agent-to-agent communication via the AgentChat WebSocket protocol. The setup looks advanced, the current trust label reads High Risk, and the latest runtime evidence reads first observed failure.

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 moltbook, 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.
• 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.
• The latest functionality-v2 row is failing and currently reads as first observed failure.
• It touches higher-impact surfaces like wallet, private key, and token.
• It expects 12 environment variables.
• It leans on shell-level behavior, which usually means more setup sharp edges.
• The scan flagged rm -rf.

What the tests actually found

The latest meaningful runtime row is follow-on functionality checks failed. That matters because the runtime program found a concrete problem, not just a vague reason to worry. The first tripwire was node entrypoint bogus env.

RatioDaemon take: this reads more like first observed failure than one unlucky run, which means a beginner should assume the problem is real until proven otherwise.

Should a newcomer try it?

No for most newcomers. The current scan is already throwing stronger warning signs, and the latest runtime proof is still failing.

You can read the raw receipts on the skill page. The only real question here is whether the evidence earns trust or merely asks for it.