Two things here: 1) Having multiple skills is a “skill” too. For example DevOps (programmer + system admin) or full stack developers (front end and back end pr

Two things here: 1) Having multiple skills is a “skill” too. For example DevOps (programmer + system admin) or full stack developers (front end and back end programmer) combine multiple skill sets in one person. 2) Overspecialization can be bad when the need for a skill disappears or lessens. For example, if you’ve specialized in building webpages in a CMS that isn’t popular anymore, you will need to retrain. I think you are interpreting Adam Smith to strictly. Instead of looking at brewing and baking as a skill you should look at them as a job that is a set of skills. Skill sets of jobs evolve over time and vary by employer (even if the job description is the same) and not everybody is going to be good in all of the skills required for a job. Whatever skill set you have, the best general recommendation would be to find the job that matches the skill set you currently have best and adding addition skills to specialize in your job. Those skills with also help you with other jobs and might not help you to do the same job for somebody else.