question

If you're basing your code on a tutorial... most common mistake may be forgetting that you need to give your skill a different name than the one in the tutorial, even when you're in development, because that name was undoubtedly grabbed by someone long ago. And yes, finding a good skill name that hasn't already been claimed is becoming progressively harder -- I had to add two words to mine to make it both distinct and memorable.

The easy way to create a podcast skill -- is to configure your stuff as genuine podcasts and tell users to access it using whatever podcast listener they prefer. There are several general-purpose ones already available; I have no opinion on which is best but I've used them and they work.

If you really want to create a skill... when I needed something like an enhanced podcast player, I went searching for examples and came up with the Jovo toolkit's sketch. That isn't a complete podcast player, but it does illustrate one way to handle the Alexa side of it (using Jovo, so in theory you can get a Google Assistant player out of it too); you'd just need to change how it obtains/maintains its list of available episodes. That's basically the approach I took -- get the Jovo example running, then progressively enhance it until I had something I considered useful.

My much-expanded code is on github as https://github.com/kubycsolutions/new-sounds-on-demand; it's probably overcomplicated for your needs and you may need to learn Jovo before it starts to make sense, but it was designed with the thought of being adaptable to other sources. (Though that isn't as cleanly isolated as it should be yet.) If you find it useful, please make a donation to New Sounds (the folks I wrote it for) and/or toss a few bucks into my ko-fi account. If you want _me_ to adapt it to your needs, we can discuss what you're willing to pay for that service.