BTW, Claude Artifacts could easily handle tasks like randomizing weights for the optimizer. That sort of thing is trivial—and it opens the door to automating and customizing the spreadsheet workflows many of us already use.
Take this example: Pitmaster described a great grid-based weight optimizer (presumably in Python):
This is exactly the kind of task that could be turned into an Artifact.
I don’t currently use the optimizer myself, so I’m not sure what the final upload step would look like—but generating weights on a grid and saving them to CSV (or having something to copy and paste into the optimizer) is well within Claude’s reach.
So I asked Claude to start building it using this prompt:
“Could you modify this idea to run in an Artifact? A user might have 50 weights and want to randomize or change them, then plug those weights into a ranking system or optimizer. For now, that might require a CSV file that is uploaded into the optimizer.”
Here’s the first draft of that Artifact :
https://claude.ai/public/artifacts/25b0a615-c04c-4614-b222-fc467ecdf30e
You (or Claude) can easily modify it to do exactly what you want. And I doubt this will ever be implemented as a formal feature request—but we can have it now using downloads and a bit of copy-pasting via Artifacts.
Maybe there’s even a way to skip the download/copy/paste step without needing P123 to write backend code.
Let us handle the ideas and coding—just give us a place to plug things in.
—
If P123 supported even basic Artifact-style tools in the browser—and optionally allowed them to tie into ranking or optimizer inputs—this kind of thing could evolve into a flexible, user-powered toolkit, all without requiring backend development time.