@User: FYI, I just made a change to the magic sky130A.tech techfile that will affect you. Previously, I had split out the cifinput sections "sky130" and "vendorimport" to deal with the labeling issue (which still needs to be figured out at the root of the problem). But I keep finding errors where I make changes to one of the styles and don't make corresponding changes to the other style. I have a "variants" method that is supposed to prevent this kind of thing. So I merged the two styles together. Now the equivalent style names are "sky130()" and "sky130(vendor)". So if you are setting "cif istyle vendorimport" in any of your scripts, that will need to be changed to "cif istyle sky130(vendor)" going forward. And there will be fewer errors creeping in.

I was not specifying any style of import. Should I be? What is the difference?

If you were not specifying any style, then you shouldn't need to make any changes at all, since the first style defined is always the default. The difference between the two was how port labels were handled on GDS read, because magic was dealing with the layer:purpose pairs on text differently than appears to be expected in the GDS, something that I need to spend some time to investigate and figure out. But if the default GDS input style was working for you, then that's fine. I guess you were using the "readspice" script to correct the input for ports, which would make the input style selection unnecessary.

Yes, exactly. readspice has been great.