Frankly, I think the most important thing is to have a good resume. Apply for jobs where you don't have all the skills, chances are they'd be happy if you knew

Frankly, I think the most important thing is to have a good resume. Apply for jobs where you don't have all the skills, chances are they'd be happy if you knew half of the things they listed, but would be willing to learn the other half. (Don't even get me started on job descriptions asking for skills that don't get used later, this happens too frequently.) Also, apply for jobs with different frameworks where you have experience solving their type of problems. That knowledge is much more valuable on a long term basis. Ask questions like "are you actively making contributions to this framework?" If so, you probably want to know it. If not, just remind them that it will most likely take much longer to ramp up on their (non-public) codebase, but your skill is learning things and solving problems. If you're not employee #1, a lot of the framework plumbing is probably already done for you.