I think you may have answered your own question possibly. A lot of the samples you all have posted would be nice to have as part of the default libraries. Maybe a half dozen queries using the query service for example or interacting with the meta data tagging. The vCAT examples are awesome as well and I think they should be included.
I would also like to see some of the actions updated with additional parameters. For example I have been forced to create my own actions and workflows around deploying templates so that different nic types can be supported. The workflows default to creating PCNET32 nic's with no option to specify anything else. I feel like I sometimes run into scriptable objects that only "mostly" map to the api. I see this in both the vCD and vSphere plugins. That can be fairly frustrating.
We also really need to get this product working correctly with Single Sign On. I know this is not specifically vCD related but we are leveraging vCO most heavily along side our vCD deployment and have been struggling with the authentication. vCO does not like our directory structure. SSO seems to account for it as we can add each domain but then we hit bugs in vCO when we set that as the authentication source. I have not has a chance to check the current vCO beta that is part of the vCD beta but I am hopeful this is no longer an issue.
Lastly this is a core vCO item but again is causing me quite a bit of frustration. We need to get the workflow scheduler working. Hopefully this is also fixed in the current beta but it has been impossible to schedule daily jobs without leaving a user logged into an interactive session. If that session gets killed you have to remove and reschedule the jobs. Not good.