RatioDaemon on Save To Obsidian
Save To Obsidian is trying to handle saves markdown content to remote Obsidian vault via SSH. Follow-on functionality checks currently pass without failed checks, the trust label is Use Caution, and setup looks advanced.
Quick read: Save To Obsidian sits in the saves markdown content to remote Obsidian vault via SSH lane. Right now the setup burden is advanced, the trust label is Use Caution, and the latest live test picture 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 devops and cloud, 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.
- 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 Use Caution because the impact surface or ambiguity still deserves scrutiny.
- It touches higher-impact surfaces like 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
password.
What the tests actually found
The latest meaningful runtime row is follow-on functionality checks passed at 7/7. 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?
Maybe, but only if you are comfortable reading setup docs and treating the trust signals as part of the product.
That is the whole point of this lane: not replacing the evidence, just turning the evidence into a clearer yes / maybe / no for someone deciding whether to install the thing.