Definitely not a skill issue if you read the details in their post - https://www.feldera.com/blog/the-pain-that-is-github-actions - they're clearly very experienced with using GitHub Actions and have run into legitimate challenges due to the complexity of what they're using it for.

I did read the post. The documentation of the product does explain how to use it, so it is unfair to blame the product in my opinion.

GitHub Actions may cover this stuff in the documentation but it's still difficult to use. That means the product could be designed better (and the documentation could be easier to follow.)

It would be more helpful for you to provide the solution rather than just boast about your intelligence.

The solution was found by the author, and is covered in GitHub actions documentation.