Depending on what Step 1 is, there is an option in the Project Settings that could skip it.
Toggling this setting will skip deploying packages in steps where the version is already on the target.
If your step you want to skip is not a package step, you have a couple of options.
You could set run conditions on the step based on a variable. You could use a system variable, one you set in the GUI manually, or you could even use API in a script step to set the variable in the project for you. Code you can adapt to do that is here.
You could use a pre-deployment script step to check something on the local worker to confirm the step is skippable(depending on why you’re skipping), then short-circuit the step if the check is true. To short-circuit a step, you can use the Skipping Conventions green box at the bottom of this documenation.
To enable pre-deployment scripts in your step, you click Configure Features within it, then enable Custom Deployment Scripts.
Please let me know if you have any questions or if this will work for you.