You've put a lot into this, that much is clear. However, this suffers from the usual problem of the era of abundant bespoke tooling: It's hard to figure out what this even does. I read the README, the examples, and the scoring function, but I still couldn't easily articulate this in a meaningful way to a third person. If you want adoption, you need to solve for this first.

Your README's first few lines, which is as far as you should expect most people will go, mentions a 2-minute explainer video. But it's actually 45 seconds. Why say otherwise? Hyperbole, maybe, but to me it raises the question of whether any of this was QC'd by a human at all before publishing. If your headline marketing material is in question, I'm inclined to make assumptions about the rest of it as well.

Edit: I should add, I'm glad I didn't check out your website before commenting, because I probably would've been too intimidated to comment. My career and expertise wouldn't measure up to yours. I do stand by my thoughts though, I think we often get so deep into our own domain and needs that we can briefly lose sight of our average audience. I’ll try this out myself on a website repo I'm updating and share how it went later on.

Part 2: Using it went pretty well, in my case there wasn't much in the way of improvements identified, but it's a fairly simple static Astro site with minimal JS used to market a business, so there's far less surface area than this is maybe intended for. It looks like it works well. Tighten up the messaging on the repo and I think you've got a good tool.