If you can skip it, it’s probably not designed right. Well designed onboarding should answer the questions you might have right when you have them, not before you even know that there is a question to ask. It’s not rocket science, but it takes some thought. Design empty states that make it obvious how to use a screen and what it’s for, always have a clear “main” action that will have a productive outcome for most users most of the time, and make sure to have a clear and consistent way to get well designed help that is relevant to what you currently see on screen (can be tricky to do on small screens, though).

That said, traditional onboardings have their place, for example to introduce new features. Even if you skip them or click through and only skim it, you might still pick up enough of a heading or illustration to make it easier to figure out why things are different.