I spend a significant portion of my time reading resumes at an elite tech firm, and another significant portion of my time revising them for students. I will give you blunt and painful advice: The skills section hurts you.
The reason is simple. Resume readers throw out any self-rating of a skill that lacks any proof. A general resume principle is ask yourself: could a precocious 5th grader have written the same thing, and could a successful esteemed engineer, professor or CEO could have written the same thing? In your case, the 5th grader has you tied. The 5th grader wanted to take a tour of a bunch of random technologies and got some random things working in a bunch of them. They are not lying at all but they are also not useful to me in any way.
Deleting the skills section should feel uncomfortable. Good. In short, the section is a crutch, and it tricks the resume writer into getting by with a hollow skills section. Take everything you deleted and write justifications for it, or throw it out if there is none. I should know your best languages or technologies from reading your accomplishments.
But, this is important: I should be hearing your languages and technologies iterated several times in your resume anyway. One, this is what automated software looks for (I'm not an expect here but I'm willing to assume keyword matching happens). Two, this is what less technical (i.e. HR and headhunters) recruiters will be catching the most, of course they will need some indication they were part of serious projects.
Don't be afraid to use lines of code! I'm serious. It's not a great metric for a lot of things but it's a good metric for the question, "Did you actually write anything." Code reviews, build systems, significant code health efforts, the fact that it landed and had some sort of positive reception, any project management you did: this tends to be useful because it tells me you actually did things. I care a little less whether it won your company a billion dollars or helped you hire 7 employees before it was abandoned, and I've learned some students and early-career people weight too much the part of the company chance had them working in.
In short I need to know what you actually did with these skills, or else I can't really assume you had any serious involvement with them.