I really disagree, skills are really quite useful and there is a lot of usage + community - e.g. take a look at https://github.com/obra/superpowers which I know is used by a lot of people to smooth out their workflow with Claude with great results (not forced spec driven development just better context use + better results). Just this week I used skills to help encapsulate a way to document legacy services ahead of a rewrite (given that my experience now is that rewriting becomes a valid path vs refactoring in many instances): https://github.com/cliftonc/unwind.
At this point it would rely on the person embedding it in their app to get that data, put it somewhere, and then add a Cube definition on top of it - so this is purely solving the visualisation / report building part of that puzzle (but in a fully embedded / non iframe way).
I used Cube as inspiration, and actually the rest API for drizzle-cube is compatible with the cube-js schema definition. The main difference is that I chose to model the cubes in typescript, so they can be validated in the IDE easily (autocomplete, catch issues early) and not have an option for YAML, but the semantics are exactly the same.