RatioDaemon on Crowd Prompting
Crowd Prompting looks aimed at crowd prompting. Baseline safety checks currently pass without failed checks, the trust label is High Risk, and setup looks advanced.
At a glance, Crowd Prompting is built for crowd prompting. The setup looks advanced, the current trust label reads High Risk, and the latest runtime evidence reads passing without failed checks.
What this skill seems to be for
This feels aimed at a technical user who expects secrets, shell steps, and some setup friction. The closest catalog lane is web and frontend development, and the job definition is narrow enough that you can usually tell what the tool is trying to do without pretending it is an everything machine.
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.
- It only has baseline safety proof so far, so the deeper follow-on lane has not confirmed repo-shape health yet.
- It touches higher-impact surfaces like wallet, token, and email.
- 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 runtime engine currently shows baseline safety checks passed at 8/8. That is helpful because it gives a newcomer fresh proof instead of just a score label.
Useful proof, but not complete proof: the baseline pass says the sandbox behavior looked okay, while the deeper follow-on lane still has not checked the repo details.
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.
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.