Simple table normalisation
Without knowing anything else about your system, that seems like total overkill.  You'd be better off with a single table that has ID, Skill, and SkillCount.  

Having two tables for such a simple schema will result in unnecessary work for both the DBA and developer.  The database engine will need to perform extra work to JOIN the two tables whenever you require reading both Skill and SkillCount at the same time.

If you had a really, really large dataset (think hundreds of millions or billions of rows) and you regularly needed to access just the Skill and rarely needed to show the SkillCount field, then perhaps you might consider using your design.