Currently, the description property of a wp_resume_skill term is used to store a numeric value which is then passed as a width to the span.skill-level with role="progressbar" set.
It should be possible to use a short string as this value, such as "Beginner", "Intermediate", etc. If the description has length but is not a number, it should be given width of 100% and that text should be displayed inside.
The WP_Resume::skill_box() function should be updated so that spaces get replaced by dashes when constructing the class name "skill-level-<?php echo $desc; ?>"
Some sorting needs to be done rather than rely on the default order, and sorting should happen equally on the level of skill groups and skills. Ideally there will be a user option on how to sort, either in the admin panel or perhaps as arguments to the resume shortcode.
Possible choices are
sort by skill level, assuming numeric value (descending by default)
if labels like "expert" or "intermediate" are used, then it would also be nice to have a lookup table of numeric mappings to these terms, so that when they are sorted they are done so semantically.
sort alphabetically (this is how the skills taxonomy editor does it)
Skill boxes to the right of the Skillset label should take as much of that line as possible, rather than starting on a new line if there is enough skills to wrap within the skillset div.
Skill boxes wrapping in a skillset should have some vertical padding between rows.
Clicking a skill in the resume view should take you to /skills/{$skill->tag} which should be a page of all the positions with that skill utilized, possibly with some other metadata about that skill such as how many years it has been used in positions (total years since first use and aggregate job-years used)
a span.skill-level is drawn within the li.skill-group, but in the current style it has 0px height so it is invisible. This should be styled so that it looks good alone or with child skills.
Currently skill-level is an overloading of the description property of each wp_resume_skill taxonomy term. This means each skill, even if used different amounts or with different competence on each project, only has one value for all positions. Also, this means that no human-readable description can be stored in the description property, so there would be no place to describe how you use the skill in your work.
A possibility would be to make skill-level an option, similar to orgLink, which would reference both the position and skill IDs in its ID, making it reflect a relationship between a skill and a position which can store a value.