Sounds promising, but is there any way to not use a path? Eg. when you go to the MeshRenderer, you can drop-down a (non-pathed) list of meshes to choose. That would be nice. Otherwise, I have to crawl my project folder looking for the mesh, which in fact may be a sub-mesh.

In that case, I'd just make a wizard with a public mesh property, drag the right mesh in, and do the processing after create

I'm really trying to avoid that 'drag' step all together. I'm making a script to repair 'missing mesh' and 'missing material' problems. I have a ton of them, too much dragging each time.

In that case, the only thing I can think of is recurse through the assets using functions from System.IO.Directory, then render them in a selectable list

This can't be really interactive. Actually, I have made some headway. I'm assuming a particular path and all files .dae. So when I run into a game object with a MeshRenderer but no mesh, I load the dae with the same name as the parent of this object, then look in the loaded objects for one that matches the current gameobject's name, with type of Mesh. I then assign this to the sharedMesh property on the mesh filter. This actually seems to work but I'm not thrilled, because the results seem to have some serious clipping plane problems (original, undamaged file had no problems). Also (see next..