Root cause of the problem: Hexo will recognize .yml / .yaml files as data files. These files will be actively parsed by Hexo and added to the template variable site.data. This process occurs before the skip_render setting takes effect. Therefore, even if skip_render is configured, Hexo will still first parse the .yml files and then attempt to skip rendering (but the parsing process has already been completed).
Solution: Use a script to forcibly copy the yml file to the public directory. Create a scripts folder in the root directory of Hexo, and within this folder, create a JavaScript file named copy-yaml.js. Write the following code into this file. Alternatively, you can download the copy-yaml.js file.