If you rename both PersonSkill and RequiredSkill to Skill, QlikView will do the rest for you automatically. Unless of course you have common fields already. In the latter case you'll get synthetic keys...
I second Michael's solution. Performance would not be good if you add fields from unrelated tables to the same object on the front end, "associating" only through an expression.
.png "Luminary Alumni"){kind=icon}