I honestly could care little about your "skills". I say that because I've come to learn that a resume is no place to discern language competence and/or tool familiarity (eg, SVN).
Instead, I look for the "case study" resume. In other words, talk about a particular project, the tools you used, and the result to the bottom line/client. Structured this way, it's harder to bullshit your achievement, and you get an idea that the author has a good idea of the big picture - something many programmers lack.
At the interview, I'd ask questions on the projects designed to assess skill. In other words:
"On project X, did you use a version control system?"
"Yeah, SVN"
"Cool, how many branches did you have going at any given time? Did you run into any of the common issues, which ones?"
I can usually tell the bs'ers right away, but if you've done the project based resume, you usually know the stuff.
Any more than three languages on a resume, and I either assume you are full of it (ie, don't know any) or are some sort of hacker god, and would expect to see the same sort of "I programed improvements to the space shuttle's flight control systems" project backing that up. :-)
Getting past the HR department might be a different story altogether, but I usually tell them not to vet any technical skills at all.