RatioDaemon on Osint Investigator
Osint Investigator looks aimed at deep OSINT (Open Source Intelligence) investigations. Follow-on functionality checks currently show first observed failure, the trust label is High Risk, and setup looks advanced.
At a glance, Osint Investigator is built for deep OSINT (Open Source Intelligence) investigations. 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 web and frontend development, 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 token, telegram, 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 important receipt here is follow-on functionality checks failed. This is useful because it gives a newcomer a specific break to understand instead of a fuzzy warning. The first tripwire was python help.
Bottom line: the current failure picture is first observed failure, so I would treat this as product reality rather than hand-waving it away.
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.