An inventory of technical skills is required virtually everywhere in computer science. This section makes hiring managers or potential coworkers aware of your experience with various tools and technologies from the discipline.
The Technical Skills inventory should be terse/brief. It is typically organized as one or more lists including programming languages, tools/frameworks, development environments, etc. If you do not otherwise indicate level of proficiency/comfort, it is frequently assumed that items that occur earlier in a list higher proficiency/master, and those that are later are where you have less experience or some level of familiarity.
You should list anything where you have comfort–not just areas that you wish to work. I.e., Even if you do not wish to work in Haskell for a living, many are moving towards more functional tools and utilities (e.g., functional web programming, distributed systems built on functional paradigms, etc.).
You should list only the utilities and languages that you have experience or comfort with–expect that an interviewer may ask you questions about C++ since it is likely to be listed higher in your resume.
Some programming languages that one may see over the course of their studies at UT Martin.