In my opinion the toolset used to create the virtualized services is a "developer" type tool. The reason I say this is that you will be working with an Integrated Development Environment (IDE) which tends to be more familiar with developers. Resources with other skill sets will be successful once they are brought up to speed on IDE's.
Clients will be most successful, based on what I have seen first hand, by having the vendor do the first round of training. The vendors are the most skilled with their individual tools. Leveraging 3rd party providers is an option as long as they have been trained and certified by the software vendor.
Most clients I have talked to would pick a small group of internal resources to be trained to "fish"... Have the vendor run thru the first couple of services while they watched ... The second set of services the resources would drive with the vendor watching ... The last step for most is to have the vendor go get coffee, but stay close by, and do the final set on their own.
This "teach to fish" approach would give the resources the chance to execute with a mentor as well as do it on their own for a few so that they felt comfortable once the vendor went home. These key resources then could train the rest of their internal community while leveraging the vendors for additional training when appropriate.
Probably the best technical skillset that I can think of is knowledge of integrations. SV tends to operate at the integration points in between the boxes. Picking up SV is easy for folks who are already familiar with integration technologies (web services, messaging brokers, queue-based systems, etc.).