Yes, but still "how to cook" is not atomic. It involves knowing how to move stuff, how to measure, what "cooked" looks like in different environment (i.e. different lighting) or variations in ingredients, how to recover from specific failures (i.e. a good cook can fix accidentally adding too much salt, by counter-balancing with an ingredient that absorbs the extra salt). And this is only one skill.

It's a bit how deep image neural nets work, where simply detecting shape primitives is not enough, the net is also the connection and relation between those primitives.

Even saying, the AI should just have the "cooking" or "coding" skill, trivializes the problem.

> Humans spend 99% of their life on boring repeating tasks

But we are also non-stop unconciously learning about the world non-stop, from the analgous stream of inputs and seeing the immediate result/feedback. Even looking at static picture is like over-training a specific dataset.

(what is turkish)->(parse lots of potentially relevant/irrelevant context because I have no way of knowing which if any of this informs the doner kebab before I've looked at it)

>dish made of meat

(what is meat) -> (parse lots of potentially ir/relevant context because I don't know if the specific origin/chemistry/mechanics or whether maillard reactions are important before I learn about them)

>cooked on a vertical rotisserie.

(what is a rotisserie) -> etc etc etc

Seems significantly less efficient than just having the various (how to cook > meat, tools > rotisserie, how to cook > seasoning > tomato; lettuce; cabbage; onion with sumac; fresh or pickled cucumber or chili; various sauces, etc) just already built in to the weights.