ovm skill

[HananINouman]

Summary

Details

i did a couple of write operations with claude code and tested with cursor opus model

How to test it

ticket: #000

[pinebit]

I like this, but now we have two sets of pretty much identical scripts: the forge's one (./script/ovm/*.s.sol) and these new shell scripts. It would be ideal to have just one set, either now or eventually.
Also, I think that these scripts might be useful outside of Claude's ecosystem, so power users could reuse them in CLI or higher level scripting. People who don't use Claude, may not guess these scripts exist at all. Moving them to ./script folder would be reasonable, but this would lead us to the above statement of having two sets of identical scripts... I am fine to remove forge's script, but then we will need to add the missing one - "deploy ovm factory".

[HananINouman]

I like this, but now we have two sets of pretty much identical scripts: the forge's one (./script/ovm/*.s.sol) and these new shell scripts. It would be ideal to have just one set, either now or eventually. Also, I think that these scripts might be useful outside of Claude's ecosystem, so power users could reuse them in CLI or higher level scripting. People who don't use Claude, may not guess these scripts exist at all. Moving them to ./script folder would be reasonable, but this would lead us to the above statement of having two sets of identical scripts... I am fine to remove forge's script, but then we will need to add the missing one - "deploy ovm factory".

i think the goal eventually is to move this obol-ovm skill folder to the obolnetowrks/skills repo and to be used outside of the obol-splits, this is why i added all needed scripts in obol-ovm instead of using .sol scripts,  and I didnt add deploy-factory because we only want ovm capabilities,
we dont want users to deploy factories