If not, did you parse the .jsonl files in the projects/ directory?
The skill itself is also the basis for my memory across sessions and projects. With that Claude can recall what I can remember. It's using a subagent so only the important bits land in context.
From there it's easy to get some benchmarks. Let it find common themes across your sessions and let it mock them to create benchmarks strong enough so not everything gets the same score. My benchmarks are now based on me designing new tools, debugging live issues going through log files, finding clues in bigger code bases etc. pp.
But no they are not open. First of all they depend on my use cases (but I also got one colleague to contribute cases) and second of all they are based on the work at my company, so I can't share them.
Have been using Codex + Claude (their $100 plans) and for some time thought Claude was too slow and wordy so using Sol for day to day; then Opus 5.5 turns out to be still the best in quality and they've caught up in speed recently as well.
I think it's always best to have multiple agents review or discuss on the problem then delegate to a faster/lower cost model for execution.