"Currency" in all fields relates to the recency and frequency with which you dealt with a particular issue. Whether flying on auto-pilot or coding with AI, automated reduces some currency. But is that a reduction in capability?

Measuring concrete tasks makes currency the operative skill; that's why it works to cram for standardized and mid-level tests.

(Indeed, the 2010's interviewing "wisdom" about people being quick to answer simple questions veered into measuring currency, not skill.)

I think this effect is strongest in time-impacted professionals. Doctors doing dozens of endoscopies a week and developers churning out code will use what tool leverage they can, and forget as much as possible to focus on what they need to. I suspect the effect is weaker in personal or research projects.

People riding bikes won't be able to run long distances - because they won't have to, and will be able to outdo any runners. That's only a problem if the supply of bikes is someone constrained. So the risk is not skill loss, but losing control of the means of production.