Obsidian is Electron based, and thus it is an eminently scriptable platform. This is evident in the broad range of core plugins that come with the platform, along with a massive community of plugins from third-parties.
I trust the core plugins. I do not trust community plugins. While there’s a superficial vetting on first inclusion, the potential for supply chain attacks or malicious intentions is enormous.
Thankfully adding your own scripted functionality for novel needs is trivial, and the major LLMs are fully versed in creating simple plugins for the system. For my daily notes I start with a template and on file creation a simple, easily audited script, mostly built with Gemini, grabs the current and forecast weather for the day through a web API, and then grabs my current chess.com ELO, and drops it into placeholders in the template. And yes I used Gemini because I have approximately zero interest in becoming an Obsidian scripting expert. But the result is a tiny plug-in script, kicked off on file creation, that I can audit in seconds, versus massive and overwrought community plugins that I can’t reasonably verify in any rational amount of time.
The chess ELO thing is an odd, temporary inclusion as I realized my chess game had stagnated and I’d become mentally lazy about the game, so it’s just a personal motivation to make it a metric I pay more attention to and stop making the silly mistakes and blunders.