The scraping example makes the code sidecar's responsibility important. A strict JSON schema can ensure the expected fields exist while the extracted values still come from the wrong page element. Packaging the instructions preserves the process, but the model-dependent parts still need behavioral checks.
I would version a few saved DOM fixtures with the skill, including missing fields and two similar elements on one page. Running those through the same extractor and output validation would show which reliability gains come from deterministic extraction code and which depend on the model following the packaged instructions.