Okay great timing because I was having the exact same idea, but mine was just a skill that was building a website with the flow mapped out and the relevant code, which seems that you are doing as well, definitely going to follow this, good luck guys!
Nice. I didn't build a skill but I noticed that for a few complicated features that I built recently, I asked the model to build an interactive "explainer" for it
Such an explainer would contain for example a simulation of the feature, where it shows how data flows between components and allows the reviewer to tweak parameters and see how it affects things. The explainer can visually show edge cases or introduce faults.
Basically my problem is that agents can write a lot. They can write a lot of code and also a lot of natural language design/spec which ultimately becomes hard to review (sloppificarion of design documents)
Sometimes you can tame this by focusing on very high level, human curated specs, but since often the devil is in the details, you need a way to see these details.
I found that interactive visual exploration tools are a very good way to both iterate on your problems and to share it with your colleagues.
Haha yeah and I’ve been building one for myself as a side project. I think there are many people experimenting in this space. Going to be interesting to see how it develops.
working on my own AI harness https://github.com/syrull/pluto tldr I dont trust anything nowadays, I wanted to know what requests I am doing to where and basically implement features that I use daily without the clutter of the other harnesses, still very raw but I am using it exclusively. Not a product or anything just something for myself.
