They already are. I asked opus 5.5 to plan out and begin building a swift version of my electron notes app, using a similar architecture / feature set. I hut enter and honestly forgot about it. 2 hours later im reading slack while making my next round of coffee, and my session is interrupted by a native app opening on my phone (the model installed it for me to test). It.... has 2/3 of the features already and looks awesome, holy crap. It skipped my suggestion to use the Lexical (web) editor and is.... using. platform native one.

time will tell if it can make it the way i like but.... it can definitely get far. Used 40% of my session limits on my $20/mo sub.

I wonder what best practices here look like at this point. In my world, we've moved past skills for something like this, having porting helper/validator/etc things be harness level is measurably better than what skills look like right now. The open plugin spec is certainly an improvement (namely in packaging and distribution)- but, really you'd be leaving perf on the table if you were not to tune your harness. I wonder if something like dsh, pi, or other extensible (coding) harnesses have something like a concept of "harness as an extension".