I've seen some organisations with an complete inability to learn these 'bicycle skills' in the interests of short-term savings because of misaligned incentives.

Gigantic enterprise software/infrastructure projects with no integration test automation because it's cheaper/faster to throw on a few temp testers every time there's a release rather than taking a month to put automation on the whole stack. Role reshuffling to make a savings for the business unit quarterly earnings sheet.

I think the other side of the coin to bicycle skills is something akin to technical debt - call it skill debt, say. Something could be done the right way straight away and the skill/process learned earlier, but because of a shortsightedness regarding cost, the cost to learn them actually increases with time until it's simply not possible without starting all over again.

This is something that can affect organisations as a whole, not just individuals, and I think it's something technical and project managers in growing organisations ought to be aware of - get your people, ALL your people, set up with the requisite bicycle skills that benefit everyone.